Bug#1042007: marked as pending in octave-sockets
Control: tag -1 pending Hello, Bug #1042007 in octave-sockets reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/pkg-octave-team/octave-sockets/-/commit/01a5e45e1aca2f058b72f4976373bbc6a17ff8c5 d/control: Build-depend on texlive Closes: #1042007 (this message was generated automatically) -- Greetings https://bugs.debian.org/1042007
Processed: Bug#1042007 marked as pending in octave-sockets
Processing control commands: > tag -1 pending Bug #1042007 [src:octave-sockets] octave-sockets FTBFS: dh_installdocs: error: Cannot find (any matches for) "doc/sockets.pdf" Added tag(s) pending. -- 1042007: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042007 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1042186: marked as done (gemmi: FTBFS: dh_install: error: missing files, aborting)
Your message dated Thu, 27 Jul 2023 05:51:36 + with message-id and subject line Bug#1042186: fixed in gemmi 0.6.2+ds-4 has caused the Debian Bug report #1042186, regarding gemmi: FTBFS: dh_install: error: missing files, aborting to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1042186: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042186 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gemmi Version: 0.6.2+ds-3 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230726 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[2]: Entering directory '/<>/obj-x86_64-linux-gnu' > make[2]: Nothing to be done for 'preinstall'. > make[2]: Leaving directory '/<>/obj-x86_64-linux-gnu' > Install the project... > /usr/bin/cmake -P cmake_install.cmake > -- Install configuration: "None" > -- Installing: /<>/debian/tmp/usr/include/gemmi > -- Installing: /<>/debian/tmp/usr/include/gemmi/binner.hpp > -- Installing: /<>/debian/tmp/usr/include/gemmi/atof.hpp > -- Installing: /<>/debian/tmp/usr/include/gemmi/sfcalc.hpp > -- Installing: /<>/debian/tmp/usr/include/gemmi/dirwalk.hpp > -- Installing: /<>/debian/tmp/usr/include/gemmi/eig3.hpp > -- Installing: /<>/debian/tmp/usr/include/gemmi/cif2mtz.hpp > -- Installing: /<>/debian/tmp/usr/include/gemmi/reciproc.hpp > -- Installing: /<>/debian/tmp/usr/include/gemmi/scaling.hpp > -- Installing: /<>/debian/tmp/usr/include/gemmi/read_map.hpp > -- Installing: /<>/debian/tmp/usr/include/gemmi/formfact.hpp > -- Installing: /<>/debian/tmp/usr/include/gemmi/input.hpp > -- Installing: /<>/debian/tmp/usr/include/gemmi/fprime.hpp > -- Installing: /<>/debian/tmp/usr/include/gemmi/twin.hpp > -- Installing: /<>/debian/tmp/usr/include/gemmi/iterator.hpp > -- Installing: /<>/debian/tmp/usr/include/gemmi/util.hpp > -- Installing: /<>/debian/tmp/usr/include/gemmi/gz.hpp > -- Installing: /<>/debian/tmp/usr/include/gemmi/bond_idx.hpp > -- Installing: /<>/debian/tmp/usr/include/gemmi/chemcomp_xyz.hpp > -- Installing: /<>/debian/tmp/usr/include/gemmi/elem.hpp > -- Installing: /<>/debian/tmp/usr/include/gemmi/assembly.hpp > -- Installing: /<>/debian/tmp/usr/include/gemmi/c4322.hpp > -- Installing: /<>/debian/tmp/usr/include/gemmi/bessel.hpp > -- Installing: /<>/debian/tmp/usr/include/gemmi/refln.hpp > -- Installing: /<>/debian/tmp/usr/include/gemmi/smcif.hpp > -- Installing: /<>/debian/tmp/usr/include/gemmi/calculate.hpp > -- Installing: /<>/debian/tmp/usr/include/gemmi/to_pdb.hpp > -- Installing: /<>/debian/tmp/usr/include/gemmi/crd.hpp > -- Installing: /<>/debian/tmp/usr/include/gemmi/cellred.hpp > -- Installing: /<>/debian/tmp/usr/include/gemmi/chemcomp.hpp > -- Installing: /<>/debian/tmp/usr/include/gemmi/enumstr.hpp > -- Installing: /<>/debian/tmp/usr/include/gemmi/floodfill.hpp > -- Installing: /<>/debian/tmp/usr/include/gemmi/riding_h.hpp > -- Installing: /<>/debian/tmp/usr/include/gemmi/sprintf.hpp > -- Installing: /<>/debian/tmp/usr/include/gemmi/mmcif_impl.hpp > -- Installing: /<>/debian/tmp/usr/include/gemmi/mmread_gz.hpp > -- Installing: /<>/debian/tmp/usr/include/gemmi/read_cif.hpp > -- Installing: /<>/debian/tmp/usr/include/gemmi/align.hpp > -- Installing: /<>/debian/tmp/usr/include/gemmi/span.hpp > -- Installing: /<>/debian/tmp/usr/include/gemmi/pdb.hpp > -- Installing: /<>/debian/tmp/usr/include/gemmi/remarks.hpp > -- Installing: /<>/debian/tmp/usr/include/gemmi/xds_ascii.hpp > -- Installing: /<>/debian/tmp/usr/include/gemmi/seqid.hpp > -- Installing: /<>/debian/tmp/usr/include/gemmi/qcp.hpp > -- Installing: /<>/debian/tmp/usr/include/gemmi/version.hpp > -- Installing: /<>/debian/tmp/usr/include/gemmi/addends.hpp > -- Installing: /<>/debian/tmp/usr/include/gemmi/linkhunt.hpp > -- Installing: /<>/debian/tmp/usr/include/gemmi/cifdoc.hpp > -- Installing: /<>/debian/tmp/usr/include/gemmi/resinfo.hpp > -- Installing: /<>/debian/tmp/usr/include/gemmi/neutron92.hpp > -- Installing: /<>/debian/tmp/usr/include/gemmi/asudata.hpp > -- Instal
Bug#1042284: marked as done (binutils-mingw-w64: FTBFS: make[1]: *** [debian/rules:71: unpack] Error 1)
Your message dated Thu, 27 Jul 2023 05:49:38 + with message-id and subject line Bug#1042284: fixed in binutils-mingw-w64 11 has caused the Debian Bug report #1042284, regarding binutils-mingw-w64: FTBFS: make[1]: *** [debian/rules:71: unpack] Error 1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1042284: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042284 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: binutils-mingw-w64 Version: 10.4 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230726 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > tar xf /usr/src/binutils/binutils-2.40.90.tar.* > rm -rf /<>/upstream > mv binutils-* /<>/upstream > patch -d /<>/upstream -R -p1 < > /usr/src/binutils/patches/001_ld_makefile_patch.patch > patching file ld/Makefile.am > patching file ld/Makefile.in > Hunk #1 succeeded at 575 (offset 2 lines). > QUILT_SERIES=debian/patches/series QUILT_PATCHES=debian/patches quilt push -a > Applying patch debian/patches/testsuite-timeout.patch > patching file upstream/gas/testsuite/lib/gas-defs.exp > > Applying patch debian/patches/specify-timestamp.patch > patching file upstream/bfd/peXXigen.c > Hunk #2 succeeded at 840 (offset -10 lines). > patching file upstream/ld/pe-dll.c > Hunk #2 succeeded at 1232 (offset 2 lines). > patching file upstream/ld/emultempl/pe.em > Hunk #1 succeeded at 345 (offset 7 lines). > patching file upstream/ld/emultempl/pep.em > Hunk #1 succeeded at 390 (offset 9 lines). > > Applying patch debian/patches/dont-run-objcopy.patch > patching file upstream/binutils/testsuite/binutils-all/objcopy.exp > Hunk #1 succeeded at 702 (offset -1 lines). > > Applying patch debian/patches/disable-flags.patch > patching file upstream/ld/emultempl/pe.em > Hunk #1 succeeded at 286 (offset 7 lines). > Hunk #2 succeeded at 387 (offset 7 lines). > patching file upstream/ld/emultempl/pep.em > Hunk #1 succeeded at 399 (offset 9 lines). > > Applying patch debian/patches/reproducible-import-libraries.patch > patching file upstream/ld/pe-dll.c > Hunk #1 succeeded at 2971 (offset 47 lines). > > Applying patch debian/patches/pr30079.patch > patching file upstream/ld/ldlang.c > Hunk #1 FAILED at 649. > 1 out of 1 hunk FAILED -- rejects in file upstream/ld/ldlang.c > Patch debian/patches/pr30079.patch can be reverse-applied > make[1]: *** [debian/rules:71: unpack] Error 1 The full build log is available from: http://qa-logs.debian.net/2023/07/26/binutils-mingw-w64_10.4_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230726;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230726=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: binutils-mingw-w64 Source-Version: 11 Done: Stephen Kitt We believe that the bug you reported is fixed in the latest version of binutils-mingw-w64, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1042...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Stephen Kitt (supplier of updated binutils-mingw-w64 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 27 Jul 2023 07:18:48 +0200 Source: binutils-mingw-w64 Architecture: source Version: 11 Distribution: unstable Urgency: medium Maintainer: Stephen Kitt Ch
Bug#1041162: marked as pending in autopkgtest
Control: tag -1 pending Hello, Bug #1041162 in autopkgtest reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/ci-team/autopkgtest/-/commit/328168f33e028426c4a8f47c88631a9efc24fb81 adt_testbed: restructure creation of pin file For testbeds with apt versions below 2.0, use dumpavail (thanks to juliank for the awk script), for testbeds with newer apt, use src:$package format. $(apt-cache showsrc $pkg) shows all packages available in the source, including Extra-Source-Only entries. This can lead to unintended failures. Closes: #1041162 (this message was generated automatically) -- Greetings https://bugs.debian.org/1041162
Processed: Bug#1041162 marked as pending in autopkgtest
Processing control commands: > tag -1 pending Bug #1041162 [autopkgtest] autopkgtest should ignore ESO entries for pinning Ignoring request to alter tags of bug #1041162 to the same tags previously set -- 1041162: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041162 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1042154: marked as done (sptag: FTBFS: dh_install: error: missing files, aborting)
Your message dated Thu, 27 Jul 2023 05:16:16 + with message-id and subject line Bug#1042154: fixed in sptag 0.0~git20230612.2ffaec6+ds-4 has caused the Debian Bug report #1042154, regarding sptag: FTBFS: dh_install: error: missing files, aborting to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1042154: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042154 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: sptag Version: 0.0~git20230612.2ffaec6+ds-3 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230726 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[2]: Entering directory '/<>/obj-x86_64-linux-gnu' > make[2]: Nothing to be done for 'preinstall'. > make[2]: Leaving directory '/<>/obj-x86_64-linux-gnu' > Install the project... > /usr/bin/cmake -P cmake_install.cmake > -- Install configuration: "None" > -- Installing: /<>/debian/tmp/usr/lib/libSPTAGLib.so > -- Installing: /<>/debian/tmp/usr/lib/libSPTAGLibStatic.a > -- Installing: /<>/debian/tmp/usr/bin/sptag-server > -- Installing: /<>/debian/tmp/usr/bin/sptag-client > -- Installing: /<>/debian/tmp/usr/bin/sptag-aggregator > -- Installing: /<>/debian/tmp/usr/bin/sptag-indexbuilder > -- Installing: /<>/debian/tmp/usr/bin/sptag-indexsearcher > -- Installing: /<>/debian/tmp/usr/bin/sptag-quantizer > -- Installing: /<>/debian/tmp/usr/lib/libsptag-ssdservingLib.a > -- Installing: /<>/debian/tmp/usr/bin/sptag-ssdserving > -- Installing: > /<>/debian/tmp/usr/local/lib/python3.11/dist-packages/_SPTAG.so > -- Installing: > /<>/debian/tmp/usr/local/lib/python3.11/dist-packages/_SPTAGClient.so > -- Installing: > /<>/debian/tmp/usr/local/lib/python3.11/dist-packages/SPTAG.py > -- Installing: > /<>/debian/tmp/usr/local/lib/python3.11/dist-packages/SPTAGClient.py > make[1]: Leaving directory '/<>/obj-x86_64-linux-gnu' >dh_install -O--buildsystem=cmake > dh_install: warning: Cannot find (any matches for) "usr/lib/python3" (tried > in ., debian/tmp) > > dh_install: warning: python3-sptag missing files: usr/lib/python3 > dh_install: error: missing files, aborting > make: *** [debian/rules:34: binary] Error 25 The full build log is available from: http://qa-logs.debian.net/2023/07/26/sptag_0.0~git20230612.2ffaec6+ds-3_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230726;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230726=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: sptag Source-Version: 0.0~git20230612.2ffaec6+ds-4 Done: Paul Wise We believe that the bug you reported is fixed in the latest version of sptag, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1042...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Paul Wise (supplier of updated sptag package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 27 Jul 2023 12:16:47 +0800 Source: sptag Architecture: source Version: 0.0~git20230612.2ffaec6+ds-4 Distribution: unstable Urgency: medium Maintainer: Paul Wise Changed-By: Paul Wise Closes: 1042154 Changes: sptag (0.0~git20230612.2ffaec6+ds-4) unstable; urgency=medium . * Fix build failure due to install layout change (Closes: #1042154)
Bug#1042098: marked as done (ocaml-gettext FTBFS with ocaml-dune 3.9.1)
Your message dated Thu, 27 Jul 2023 05:11:02 + with message-id and subject line Bug#1042098: fixed in ocaml-gettext 0.4.2-2 has caused the Debian Bug report #1042098, regarding ocaml-gettext FTBFS with ocaml-dune 3.9.1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1042098: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042098 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ocaml-gettext Version: 0.4.2-1 Severity: serious Tags: ftbfs trixie sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ocaml-gettext.html ... debian/rules override_dh_auto_install make[1]: Entering directory '/build/1st/ocaml-gettext-0.4.2' mkdir -p /build/1st/ocaml-gettext-0.4.2/debian/tmp//usr/lib/ocaml /usr/bin/make install DESTDIR=/build/1st/ocaml-gettext-0.4.2/debian/tmp \ prefix=/build/1st/ocaml-gettext-0.4.2/debian/tmp/usr sysconfdir=/build/1st/ocaml-gettext-0.4.2/debian/tmp/etc \ OCAMLFIND_LDCONF=ignore \ DOCDIR='/build/1st/ocaml-gettext-0.4.2/debian/tmp/usr/share/doc/libgettext-ocaml-dev' make[2]: Entering directory '/build/1st/ocaml-gettext-0.4.2' dune build @install dune install Error: The mandir installation directory is unknown. Hint: It can be specified with --prefix or by setting --mandir make[2]: *** [Makefile:46: install] Error 1 --- End Message --- --- Begin Message --- Source: ocaml-gettext Source-Version: 0.4.2-2 Done: Stéphane Glondu We believe that the bug you reported is fixed in the latest version of ocaml-gettext, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1042...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Stéphane Glondu (supplier of updated ocaml-gettext package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 27 Jul 2023 06:31:05 +0200 Source: ocaml-gettext Architecture: source Version: 0.4.2-2 Distribution: unstable Urgency: medium Maintainer: Debian OCaml Maintainers Changed-By: Stéphane Glondu Closes: 1042098 Changes: ocaml-gettext (0.4.2-2) unstable; urgency=medium . * Team upload * Use ocam_dune DH buildsystem (Closes: #1042098) * Bump Standards-Version to 4.6.2 Checksums-Sha1: 958a60e886c9559adf1d0715014155cc45a51ce0 2083 ocaml-gettext_0.4.2-2.dsc 70e7e9f4e4653974e31698085ea0a764bec0a7a4 4588 ocaml-gettext_0.4.2-2.debian.tar.xz Checksums-Sha256: 9a14f7e5646e1ea4f4d7fd41f0d2a667a4b30143ddf7c6ff8c1c4ff281bd833e 2083 ocaml-gettext_0.4.2-2.dsc a77e62637db29857938b7c4053ca23b94679d24fb378ee047f2e99acd435d107 4588 ocaml-gettext_0.4.2-2.debian.tar.xz Files: 4c1a1a17c3fcb8fe415b3e1893acc863 2083 ocaml optional ocaml-gettext_0.4.2-2.dsc 1fc6304c89f087cb6119298557aeae1e 4588 ocaml optional ocaml-gettext_0.4.2-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQFGBAEBCgAwFiEEbeJOl+yohsxW5iUOIbju8bGJMIEFAmTB8+gSHGdsb25kdUBk ZWJpYW4ub3JnAAoJECG47vGxiTCBzdsH/2ehpStfvficIQxGMgvJRE6Ktfwj4Aqs fantv0i6JA+q7k3XiZZAXstqPkC/bVjSP2OuQAOFXMpNA2fPZLQAPOVh1AlCs1HG 6xOU1Kc4prpOyDWz4pVBzpH7N4wq/cL9lXbmoBe2Y7v+oAI3W4ViZ5ZmeOH7XBDS gvemV2rIS8eh2qtwiUM+j3fC9oQ3Pv23Snkct7WkJGNNibuVrzpmL+eIf9KxAO4m 1aZzENEnt3nZEytPnPqdByf0UYx2gU0RH1B0DOmATveSY/ZM86Mmc1ea+VdJOdH2 ZW0DW6GaT34mV+eynZ49kQqBBSCt308xMKsyP2a0M9puKOgR9TXJ9Mg= =ixDU -END PGP SIGNATURE End Message ---
Bug#1042100: marked as done (lablgtk3 FTBFS with ocaml-dune 3.9.1)
Your message dated Thu, 27 Jul 2023 05:08:22 + with message-id and subject line Bug#1042100: fixed in lablgtk3 3.1.3-2 has caused the Debian Bug report #1042100, regarding lablgtk3 FTBFS with ocaml-dune 3.9.1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1042100: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042100 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: lablgtk3 Version: 3.1.3-1 Severity: serious Tags: ftbfs trixie sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/lablgtk3.html ... debian/rules override_dh_auto_install make[1]: Entering directory '/build/1st/lablgtk3-3.1.3' DESTDIR=/build/1st/lablgtk3-3.1.3/debian/tmp dune install lablgtk3 lablgtk3-gtkspell3 lablgtk3-sourceview3 Error: The mandir installation directory is unknown. Hint: It can be specified with --prefix or by setting --mandir make[1]: *** [debian/rules:21: override_dh_auto_install] Error 1 --- End Message --- --- Begin Message --- Source: lablgtk3 Source-Version: 3.1.3-2 Done: Stéphane Glondu We believe that the bug you reported is fixed in the latest version of lablgtk3, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1042...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Stéphane Glondu (supplier of updated lablgtk3 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 27 Jul 2023 05:40:39 +0200 Source: lablgtk3 Architecture: source Version: 3.1.3-2 Distribution: unstable Urgency: medium Maintainer: Debian OCaml Maintainers Changed-By: Stéphane Glondu Closes: 1042100 Changes: lablgtk3 (3.1.3-2) unstable; urgency=medium . * Team upload * Use ocaml_dune DH buildsystem (Closes: #1042100) * Bump Standards-Version to 4.6.2 Checksums-Sha1: 0dd4b5f161ecf7c49b7187a7de54206014224541 2524 lablgtk3_3.1.3-2.dsc d330e11c7e0aa466533824a4cc71e59f55a47b58 5612 lablgtk3_3.1.3-2.debian.tar.xz Checksums-Sha256: 8c56932be755ca41bc3d253c28c3fcdd237010c56013f2078e94368cb2d483bd 2524 lablgtk3_3.1.3-2.dsc 359603a7e46184e0653b07d99153a28a5b1e1dd8bed7d58156c23e76a80b3ddf 5612 lablgtk3_3.1.3-2.debian.tar.xz Files: 97fcff4845b52ca0f3cd601d1052a44b 2524 ocaml optional lablgtk3_3.1.3-2.dsc 0a8eb03868fe1ead81686ee5ae8bf0f5 5612 ocaml optional lablgtk3_3.1.3-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQFGBAEBCgAwFiEEbeJOl+yohsxW5iUOIbju8bGJMIEFAmTB714SHGdsb25kdUBk ZWJpYW4ub3JnAAoJECG47vGxiTCBpFsH/3jrZ0P0lygMqK2N7ccxEMEEq8rTLlhX gN5d0gjL6VX8/BpCJ506WpmCl7ehS5Vj61K1t0eMpx9UtfskqtoSsanX6VNTULIH Q5sqN/EH3ugzI28vib+6f4rPzs0XtlVeNeViVZS8KBMZpI/lZGMhVat98Rf24hpV OS7cqfgkoJReAqKenSgBu6oNZTr02HEGvHM9LUwLGNwJtK1RWb6uJD6hbm7hJmN0 GgxDRCNlfwdkf7z732m8uoRqU3gVaodwusBO66gmL3N3G7mRg4IBxZkwSmeOYtpC gnXC6+80F36ROWSJ9SRCaL0nNzjcNZgKqpcq+/UuEUU6Jr9yRSIsOaE= =nQqk -END PGP SIGNATURE End Message ---
Bug#1042278: marked as done (python-snuggs: FTBFS: tests fail)
Your message dated Thu, 27 Jul 2023 04:26:22 +
with message-id
and subject line Bug#1042278: fixed in python-snuggs 1.4.7-4
has caused the Debian Bug report #1042278,
regarding python-snuggs: FTBFS: tests fail
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1042278: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042278
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-snuggs
Version: 1.4.7-3
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230726 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules binary
> dh binary --with python3 --buildsystem pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:240: python3.11 setup.py config
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:240: /usr/bin/python3 setup.py build
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.11_snuggs/build/snuggs
> copying snuggs/__init__.py ->
> /<>/.pybuild/cpython3_3.11_snuggs/build/snuggs
> running egg_info
> creating snuggs.egg-info
> writing snuggs.egg-info/PKG-INFO
> writing dependency_links to snuggs.egg-info/dependency_links.txt
> writing requirements to snuggs.egg-info/requires.txt
> writing top-level names to snuggs.egg-info/top_level.txt
> writing manifest file 'snuggs.egg-info/SOURCES.txt'
> reading manifest file 'snuggs.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> warning: no files found matching 'VERSION.txt'
> adding license file 'LICENSE'
> adding license file 'AUTHORS.txt'
> writing manifest file 'snuggs.egg-info/SOURCES.txt'
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:240: cd /<>/.pybuild/cpython3_3.11_snuggs/build;
> python3.11 -m pytest /<>/test_snuggs.py
> = test session starts
> ==
> platform linux -- Python 3.11.4, pytest-7.4.0, pluggy-1.2.0
> rootdir: /<>
> plugins: hypothesis-6.82.0
> collected 37 items
>
> ../../../test_snuggs.py ..X...F.F.F..
> [100%]
>
> === FAILURES
> ===
> __ test_missing_closing_paren
> __
>
> self = ')', instring = '(+ 1 2', loc = 6, doActions = True, callPreParse =
> False
>
> def _parseNoCache(
> self, instring, loc, doActions=True, callPreParse=True
> ) -> Tuple[int, ParseResults]:
> TRY, MATCH, FAIL = 0, 1, 2
> debugging = self.debug # and doActions)
> len_instring = len(instring)
>
> if debugging or self.failAction:
> # print("Match {} at loc {}({}, {})".format(self, loc,
> lineno(loc, instring), col(loc, instring)))
> try:
> if callPreParse and self.callPreparse:
> pre_loc = self.preParse(instring, loc)
> else:
> pre_loc = loc
> tokens_start = pre_loc
> if self.debugActions.debug_try:
> self.debugActions.debug_try(instring, tokens_start, self,
> False)
> if self.mayIndexError or pre_loc >= len_instring:
> try:
> loc, tokens = self.parseImpl(instring, pre_loc,
> doActions)
> except IndexError:
> raise ParseException(instring, len_instring,
> self.errmsg, self)
> else:
> loc, tokens = self.parseImpl(instring, pre_loc, doActions)
> except Exception as err:
> # print("Exception raised:", err)
> if self.debugActions.debug_fail:
> self.debugActions.debug_fail(
> instring, tokens_start, self, err, False
> )
> if self.failAction:
> self.failAction(instring, tokens_start, self, err)
> raise
> else:
> if callPreParse and self.callPreparse:
>
Bug#1037709: marked as done (kitinerary: ftbfs with GCC-13)
Your message dated Thu, 27 Jul 2023 04:21:57 + with message-id and subject line Bug#1037709: fixed in kitinerary 22.12.3-2 has caused the Debian Bug report #1037709, regarding kitinerary: ftbfs with GCC-13 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1037709: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037709 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:kitinerary Version: 22.12.3-1 Severity: normal Tags: sid trixie User: debian-...@lists.debian.org Usertags: ftbfs-gcc-13 [This bug is targeted to the upcoming trixie release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-13/g++-13, but succeeds to build with gcc-12/g++-12. The severity of this report will be raised before the trixie release. The full build log can be found at: http://qa-logs.debian.net/2023/05/22/logs/kitinerary_22.12.3-1_unstable_gccexp.log The last lines of the build log are at the end of this report. To build with GCC 13, either set CC=gcc-13 CXX=g++-13 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-13/porting_to.html [...] 19 | class BitVectorView | ^ /<>/src/lib/asn1/bitvectorview.h: In instantiation of ‘T KItinerary::BitVectorView::valueAtMSB(size_type, size_type) const [with T = unsigned char; size_type = long unsigned int]’: /<>/src/lib/asn1/bitvectorview.cpp:41:43: required from here /<>/src/lib/asn1/bitvectorview.h:46:25: error: ‘at’ was not declared in this scope; did you mean ‘Qt’? 46 | result |= at(index + i); | ~~^~~ | Qt [ 6%] Building CXX object src/lib/CMakeFiles/KPimItinerary.dir/datatypes/action.cpp.o cd /<>/obj-x86_64-linux-gnu/src/lib && /usr/bin/c++ -DKCalCore=KCalendarCore -DKF_DEPRECATED_WARNINGS_SINCE=0x6 -DKF_DISABLE_DEPRECATED_BEFORE_AND_AT=0x56300 -DKPimItinerary_EXPORTS -DQT_CORE_LIB -DQT_DEPRECATED_WARNINGS_SINCE=0x6 -DQT_DISABLE_DEPRECATED_BEFORE=0x50f02 -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_NO_CAST_FROM_ASCII -DQT_NO_CAST_FROM_BYTEARRAY -DQT_NO_CAST_TO_ASCII -DQT_NO_DEBUG -DQT_NO_FOREACH -DQT_NO_KEYWORDS -DQT_NO_NARROWING_CONVERSIONS_IN_CONNECT -DQT_NO_URL_CAST_FROM_STRING -DQT_QML_LIB -DQT_STRICT_ITERATORS -DQT_USE_QSTRINGBUILDER -DTRANSLATION_DOMAIN=\"kitinerary\" -D_GNU_SOURCE -D_LARGEFILE64_SOURCE -I/<>/obj-x86_64-linux-gnu/src/lib -I/<>/src/lib -I/<>/obj-x86_64-linux-gnu/src/lib/KPimItinerary_autogen/include -I/<>/obj-x86_64-linux-gnu -I/usr/include/libxml2 -isystem /usr/include/x86_64-linux-gnu/qt5 -isystem /usr/include/x86_64-linux-gnu/qt5/QtCore -isystem /usr/lib/x86_64-linux-gnu/qt5/mkspecs /linux-g++ -isystem /usr/include/KF5/KMime -isystem /usr/include/KF5 -isystem /usr/include/x86_64-linux-gnu/qt5/QtQml -isystem /usr/include/x86_64-linux-gnu/qt5/QtNetwork -isystem /usr/include/KF5/KArchive -isystem /usr/include/KF5/KI18n -isystem /usr/include/KF5/KI18nLocaleData -isystem /usr/include/KF5/KCalendarCore -isystem /usr/include/x86_64-linux-gnu/qt5/QtGui -isystem /usr/include/KF5/KCodecs -isystem /usr/include/KF5/KContacts -isystem /usr/include/KPim -isystem /usr/include/poppler -isystem /usr/include/x86_64-linux-gnu/qt5/QtQml/5.15.8 -isystem /usr/include/x86_64-linux-gnu/qt5/QtQml/5.15.8/QtQml -isystem /usr/include/x86_64-linux-gnu/qt5/QtNetwork/5.15.8 -isystem /usr/include/x86_64-linux-gnu/qt5/QtNetwork/5.15.8/QtNetwork -isystem /usr/include/x86_64-linux-gnu/qt5/QtCore/5.15.8 -isystem /usr/include/x86_64-linux-gnu/qt5/QtCore/5.15.8/QtCore -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE= 2 -fno-operator-names -fno-exceptions -Wall -Wextra -Wcast-align -Wchar-subscripts -Wformat-security -Wno-long-long -Wpointer-arith -Wundef -Wnon-virtual-dtor -Woverloaded-virtual -Werror=return-type -Werror=init-self -Wvla -Wdate-time -Wsuggest-override -Wlogical-op -pedantic -Wzero-as-null-pointer-constant -Wmissing-include-dirs
Bug#244289: xball: Package includes non-free source code.
I unarchived this bug as the package still contains the source file act_area.c with the same non-free license. I marked it as found in xball/3.0-12 because it was the earliest version I was able to dig on debsnaps. As such, I couldn't pinpoint the exact version between that and 3.0-5 in which the file was reintroduced. -- ⢀⣴⠾⠻⢶⣦⠀ David da Silva Polverari ⣾⠁⢠⠒⠀⣿⡁ ⢿⡄⠘⠷⠚⠋⠀ Debian: The universal operating system ⠈⠳⣄
Bug#1042346: marked as done (rust-versionize-derive: FTBFS: dh_auto_test: error: /usr/share/cargo/bin/cargo test --all returned exit code 101)
Your message dated Thu, 27 Jul 2023 03:56:43 +
with message-id
and subject line Bug#1042346: fixed in rust-versionize-derive 0.1.5-1
has caused the Debian Bug report #1042346,
regarding rust-versionize-derive: FTBFS: dh_auto_test: error:
/usr/share/cargo/bin/cargo test --all returned exit code 101
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1042346: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042346
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-versionize-derive
Version: 0.1.4-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230726 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_test -- test --all
> debian cargo wrapper: options, profiles, parallel: ['parallel=8'] [] ['-j8']
> debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu,
> x86_64-linux-gnu
> debian cargo wrapper: running subprocess (['env', 'RUST_BACKTRACE=1',
> '/usr/bin/cargo', '-Zavoid-dev-deps', 'test', '--verbose', '--verbose',
> '-j8', '--target', 'x86_64-unknown-linux-gnu', '--all'],) {}
>Compiling proc-macro2 v1.0.65
>Compiling quote v1.0.30
>Compiling unicode-ident v1.0.0
> Running `CARGO=/usr/bin/cargo CARGO_CRATE_NAME=build_script_build
> CARGO_MANIFEST_DIR=/<>/debian/cargo_registry/quote-1.0.30
> CARGO_PKG_AUTHORS='David Tolnay '
> CARGO_PKG_DESCRIPTION='Quasi-quoting macro quote'\!'(...)'
> CARGO_PKG_HOMEPAGE='' CARGO_PKG_LICENSE='MIT OR Apache-2.0'
> CARGO_PKG_LICENSE_FILE='' CARGO_PKG_NAME=quote
> CARGO_PKG_REPOSITORY='https://github.com/dtolnay/quote'
> CARGO_PKG_RUST_VERSION=1.31 CARGO_PKG_VERSION=1.0.30
> CARGO_PKG_VERSION_MAJOR=1 CARGO_PKG_VERSION_MINOR=0
> CARGO_PKG_VERSION_PATCH=30 CARGO_PKG_VERSION_PRE=''
> LD_LIBRARY_PATH='/<>/target/debug/deps:/usr/lib' rustc
> --crate-name build_script_build --edition=2018
> /<>/debian/cargo_registry/quote-1.0.30/build.rs
> --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat
> --crate-type bin --emit=dep-info,link -C embed-bitcode=no -C debuginfo=2
> --cfg 'feature="default"' --cfg 'feature="proc-macro"' -C
> metadata=7a34db8af5b2571c -C extra-filename=-7a34db8af5b2571c --out-dir
> /<>/target/debug/build/quote-7a34db8af5b2571c -L
> dependency=/<>/target/debug/deps --cap-lints warn`
> Running `CARGO=/usr/bin/cargo CARGO_CRATE_NAME=unicode_ident
> CARGO_MANIFEST_DIR=/<>/debian/cargo_registry/unicode-ident-1.0.0
> CARGO_PKG_AUTHORS='David Tolnay '
> CARGO_PKG_DESCRIPTION='Determine whether characters have the XID_Start or
> XID_Continue properties according to Unicode Standard Annex #31'
> CARGO_PKG_HOMEPAGE='' CARGO_PKG_LICENSE='MIT OR Apache-2.0'
> CARGO_PKG_LICENSE_FILE='' CARGO_PKG_NAME=unicode-ident
> CARGO_PKG_REPOSITORY='https://github.com/dtolnay/unicode-ident'
> CARGO_PKG_RUST_VERSION=1.31 CARGO_PKG_VERSION=1.0.0 CARGO_PKG_VERSION_MAJOR=1
> CARGO_PKG_VERSION_MINOR=0 CARGO_PKG_VERSION_PATCH=0 CARGO_PKG_VERSION_PRE=''
> LD_LIBRARY_PATH='/<>/target/debug/deps:/usr/lib' rustc
> --crate-name unicode_ident --edition=2018
> /<>/debian/cargo_registry/unicode-ident-1.0.0/src/lib.rs
> --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat
> --crate-type lib --emit=dep-info,metadata,link -C embed-bitcode=no -C
> debuginfo=2 -C metadata=e2db5faa88c7ef07 -C extra-filename=-e2db5faa88c7ef07
> --out-dir /<>/target/debug/deps -L
> dependency=/<>/target/debug/deps --cap-lints warn`
> Running `CARGO=/usr/bin/cargo CARGO_CRATE_NAME=build_script_build
> CARGO_MANIFEST_DIR=/<>/debian/cargo_registry/proc-macro2-1.0.65
> CARGO_PKG_AUTHORS='David Tolnay :Alex Crichton
> ' CARGO_PKG_DESCRIPTION='A substitute implementation
> of the compiler'\''s `proc_macro` API to decouple token-based libraries from
> the procedural macro use case.' CARGO_PKG_HOMEPAGE='' CARGO_PKG_LICENSE='MIT
> OR Apache-2.0' CARGO_PKG_LICENSE_FILE='' CARGO_PKG_NAME=proc-macro2
> CARGO_PKG_REPOSITORY='https://github.com/dtolnay/proc-macro2'
> CARGO_PKG_RUST_VERSION=1.31 CARGO_PKG_VERSION=1.0.65
> CARGO_PKG_VERSION_MAJOR=1 CARGO_PKG_VERSION_MINOR=0
> CARGO_PKG_VERSION_PATCH=65 CARGO_PKG_VERSION_PRE=''
> L
Bug#1042261: marked as done (rust-tealdeer: FTBFS: make: *** [debian/rules:3: binary] Error 25)
Your message dated Thu, 27 Jul 2023 03:56:31 + with message-id and subject line Bug#1042261: fixed in rust-tealdeer 1.6.1-1 has caused the Debian Bug report #1042261, regarding rust-tealdeer: FTBFS: make: *** [debian/rules:3: binary] Error 25 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1042261: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042261 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: rust-tealdeer Version: 1.5.0-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230726 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > help2man \ > --name tldr \ > --no-info \ > debian/tealdeer/usr/bin/tldr > debian/tldr.1 > dh_installman -O--buildsystem=cargo > make[1]: Leaving directory '/<>' >dh_installinit -O--buildsystem=cargo >dh_installsystemduser -O--buildsystem=cargo >dh_perl -O--buildsystem=cargo >dh_link -O--buildsystem=cargo >dh_strip_nondeterminism -O--buildsystem=cargo >dh_compress -O--buildsystem=cargo >dh_fixperms -O--buildsystem=cargo >dh_missing -O--buildsystem=cargo >dh_dwz -O--buildsystem=cargo > dwz: debian/tealdeer/usr/bin/tldr: Couldn't find DIE at [b586b] referenced by > DW_AT_abstract_origin from DIE at [c599d] > dh_dwz: error: dwz -- debian/tealdeer/usr/bin/tldr returned exit code 1 > dh_dwz: error: Aborting due to earlier error > make: *** [debian/rules:3: binary] Error 25 The full build log is available from: http://qa-logs.debian.net/2023/07/26/rust-tealdeer_1.5.0-2_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230726;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230726=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: rust-tealdeer Source-Version: 1.6.1-1 Done: Peter Michael Green We believe that the bug you reported is fixed in the latest version of rust-tealdeer, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1042...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Peter Michael Green (supplier of updated rust-tealdeer package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 27 Jul 2023 03:22:35 + Source: rust-tealdeer Architecture: source Version: 1.6.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Rust Maintainers Changed-By: Peter Michael Green Closes: 1042261 Changes: rust-tealdeer (1.6.1-1) unstable; urgency=medium . * Team upload. * Package tealdeer 1.6.1 from crates.io using debcargo 2.6.0 * Apply workaround for dh_dwz crash (Closes: #1042261) . [ Blair Noctis ] * Package tealdeer 1.6.1 from crates.io using debcargo 2.6.0 * Drop clap 3 rc relaxing patch and allow_prerelease_deps option * Patch to add back shell completions removed in crates.io release * Use upstream zsh completion Checksums-Sha1: aaa5d10f498c05544d54f683d32cdec155691c4a 2702 rust-tealdeer_1.6.1-1.dsc b2e8bd8a5d0f89e3b39ebf5d2a02a3c204754bd0 42615 rust-tealdeer_1.6.1.orig.tar.gz a1f547191cde358526bd3dc14f7af4173c30a7c7 4740 rust-tealdeer_1.6.1-1.debian.tar.xz a1d1c71d7c0cb28f4d9da15f53068c0fe4e66adc 19226 rust-tealdeer_1.6.1-1_source.buildinfo Checksums-Sha256: 69797f5dc115d3fd8d5eead3b68327b0fa71068f2af4e6ea08b5a48d75c753a6 2702 rust-tealdeer_1.6.1-1.dsc 0a7adacdcd053ee8c5bd3288c
Bug#1042292: marked as done (pyosmium: FTBFS: FAILED test/test_writer.py::test_member_object - RuntimeError: return_value_p...)
Your message dated Thu, 27 Jul 2023 03:55:21 +
with message-id
and subject line Bug#1042292: fixed in pyosmium 3.6.0-2
has caused the Debian Bug report #1042292,
regarding pyosmium: FTBFS: FAILED test/test_writer.py::test_member_object -
RuntimeError: return_value_p...
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1042292: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042292
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pyosmium
Version: 3.6.0-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230726 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[2]: Entering directory '/<>/doc'
> sphinx-build -b man -d _build/doctrees . _build/man
> Running Sphinx v5.3.0
> making output directory... done
> WARNING: html_static_path entry '_static' does not exist
> loading pickled environment... done
> building [mo]: targets for 0 po files that are out of date
> building [man]: all manpages
> updating environment: 0 added, 0 changed, 0 removed
> looking for now-outdated files... none found
> writing... pyosmium-get-changes.1 { } pyosmium-up-to-date.1 { } done
> build succeeded, 1 warning.
>
> The manual pages are in _build/man.
>
> Build finished. The manual pages are in _build/man.
> make[2]: Leaving directory '/<>/doc'
> make[1]: Leaving directory '/<>'
>dh_auto_build -O--buildsystem=pybuild -Npyosmium -Npyosmium-doc
> I: pybuild base:240: /usr/bin/python3 setup.py build
> running build
> running build_py
> running build_ext
> Re-run cmake no build system arguments
> CMake Deprecation Warning at CMakeLists.txt:1 (cmake_minimum_required):
> Compatibility with CMake < 3.5 will be removed from a future version of
> CMake.
>
> Update the VERSION argument value or use a ... suffix to tell
> CMake that the project does not need compatibility with older versions.
>
>
> -- lz4 library found, compiling with it
> -- Building in C++14 mode
> CMake Warning (dev) at /usr/lib/cmake/pybind11/FindPythonLibsNew.cmake:98
> (find_package):
> Policy CMP0148 is not set: The FindPythonInterp and FindPythonLibs modules
> are removed. Run "cmake --help-policy CMP0148" for policy details. Use
> the cmake_policy command to set the policy and suppress this warning.
>
> Call Stack (most recent call first):
> /usr/lib/cmake/pybind11/pybind11Tools.cmake:50 (find_package)
> /usr/lib/cmake/pybind11/pybind11Common.cmake:188 (include)
> /usr/lib/cmake/pybind11/pybind11Config.cmake:250 (include)
> CMakeLists.txt:44 (find_package)
> This warning is for project developers. Use -Wno-dev to suppress it.
>
> -- Found pybind11: /usr/include (found version "2.11.1")
> -- Configuring done (0.1s)
> -- Generating done (0.0s)
> -- Build files have been written to:
> /<>/build/temp.linux-x86_64-cpython-311
> Change Dir: '/<>/build/temp.linux-x86_64-cpython-311'
>
> Run Build Command(s): /usr/bin/cmake -E env VERBOSE=1 /usr/bin/gmake -f
> Makefile -j2
> gmake[1]: Entering directory
> '/<>/build/temp.linux-x86_64-cpython-311'
> /usr/bin/cmake -S/<>
> -B/<>/build/temp.linux-x86_64-cpython-311 --check-build-system
> CMakeFiles/Makefile.cmake 0
> /usr/bin/cmake -E cmake_progress_start
> /<>/build/temp.linux-x86_64-cpython-311/CMakeFiles
> /<>/build/temp.linux-x86_64-cpython-311//CMakeFiles/progress.marks
> /usr/bin/gmake -f CMakeFiles/Makefile2 all
> gmake[2]: Entering directory
> '/<>/build/temp.linux-x86_64-cpython-311'
> /usr/bin/gmake -f CMakeFiles/geom.dir/build.make CMakeFiles/geom.dir/depend
> /usr/bin/gmake -f CMakeFiles/index.dir/build.make CMakeFiles/index.dir/depend
> gmake[3]: Entering directory
> '/<>/build/temp.linux-x86_64-cpython-311'
> cd /<>/build/temp.linux-x86_64-cpython-311 && /usr/bin/cmake -E
> cmake_depends "Unix Makefiles" /<> /<>
> /<>/build/temp.linux-x86_64-cpython-311
> /<>/build/temp.linux-x86_64-cpython-311
> /<>/build/temp.linux-x86_64-cpython-311/CMakeFiles/geom.dir/DependInfo.cmake
> "--color="
> gmake[3]: Entering directory
> '/<>/build/temp.linux-x86_64-cpython-311'
> cd /<>/build/temp.
Bug#1042103: marked as done (ocaml-cairo2 FTBFS with ocaml-dune 3.9.1)
Your message dated Thu, 27 Jul 2023 03:53:07 + with message-id and subject line Bug#1042103: fixed in ocaml-cairo2 0.6.4+dfsg-2 has caused the Debian Bug report #1042103, regarding ocaml-cairo2 FTBFS with ocaml-dune 3.9.1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1042103: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042103 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ocaml-cairo2 Version: 0.6.4+dfsg-1 Severity: serious Tags: ftbfs trixie sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ocaml-cairo2.html ... dh_auto_install make -j16 install DESTDIR=/build/1st/ocaml-cairo2-0.6.4\+dfsg/debian/tmp AM_UPDATE_INFO_DIR=no "INSTALL=install --strip-program=true" make[1]: Entering directory '/build/1st/ocaml-cairo2-0.6.4+dfsg' dune install Error: The mandir installation directory is unknown. Hint: It can be specified with --prefix or by setting --mandir make[1]: *** [Makefile:12: install] Error 1 --- End Message --- --- Begin Message --- Source: ocaml-cairo2 Source-Version: 0.6.4+dfsg-2 Done: Stéphane Glondu We believe that the bug you reported is fixed in the latest version of ocaml-cairo2, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1042...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Stéphane Glondu (supplier of updated ocaml-cairo2 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 27 Jul 2023 05:22:06 +0200 Source: ocaml-cairo2 Architecture: source Version: 0.6.4+dfsg-2 Distribution: unstable Urgency: medium Maintainer: Debian OCaml Maintainers Changed-By: Stéphane Glondu Closes: 1042103 Changes: ocaml-cairo2 (0.6.4+dfsg-2) unstable; urgency=medium . * Team upload * Use ocaml_dune DH buildsystem (Closes: #1042103) Checksums-Sha1: 06f7aa1039733a22dc1872347b1fe61adc1dee4f 2062 ocaml-cairo2_0.6.4+dfsg-2.dsc d69c1784f10a7274741b242819c6e454d4d163c5 3740 ocaml-cairo2_0.6.4+dfsg-2.debian.tar.xz Checksums-Sha256: 3f3b99313dffa784715754fa50c2a25c55240e7a4fdcf386f3bf650c2ae2e373 2062 ocaml-cairo2_0.6.4+dfsg-2.dsc 1bd399b2e163d93ab2d7f0b69b94cf0ce9c2c3dd623bd086f939b69d7b0cd92b 3740 ocaml-cairo2_0.6.4+dfsg-2.debian.tar.xz Files: 286b5baf6c8f0f54e7196ada596ea5c7 2062 ocaml optional ocaml-cairo2_0.6.4+dfsg-2.dsc 49d5808756ea268194263e2fe570144d 3740 ocaml optional ocaml-cairo2_0.6.4+dfsg-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQFGBAEBCgAwFiEEbeJOl+yohsxW5iUOIbju8bGJMIEFAmTB49USHGdsb25kdUBk ZWJpYW4ub3JnAAoJECG47vGxiTCB0CgH/1LeXTgnh6LkjxTNucXm5NPERYB6TPtR gz+agPbyDUa0VLpaERRqOt3nsIamC7vP9wEFxCJdIAJKLmfSdJmT9WbbRJx7wo/M iQsCGhE5uoRP2xJqDj8p0x8bHyQGQFYq/hCeQjQd8/um4WUmS/J0QWdR/tq45wg0 b0O5GKxVcdhxM7sBw42660w8papJ6hlsrTWYLECjfaVPYVA5N6mk/G4/Vw6v2K6j 2x//NAKtsLPJdKb4jD55znVPPkhqU77ky4MDIQ2bVm2eHdd8zXQoq++jVxSdup+d Y8XALUV9aeydEiffsjrM7FCaa9UMNGCMajsK96urEABIW2qZmXgb9EQ= =gU8Y -END PGP SIGNATURE End Message ---
Bug#1042101: marked as done (ocaml-rope FTBFS with ocaml-dune 3.9.1)
Your message dated Thu, 27 Jul 2023 03:53:13 + with message-id and subject line Bug#1042101: fixed in ocaml-rope 0.6.2-4 has caused the Debian Bug report #1042101, regarding ocaml-rope FTBFS with ocaml-dune 3.9.1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1042101: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042101 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ocaml-rope Version: 0.6.2-3 Severity: serious Tags: ftbfs trixie sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ocaml-rope.html ... Error: The mandir installation directory is unknown. Hint: It can be specified with --prefix or by setting --mandir make[1]: *** [debian/rules:17: override_dh_auto_install] Error 1 --- End Message --- --- Begin Message --- Source: ocaml-rope Source-Version: 0.6.2-4 Done: Stéphane Glondu We believe that the bug you reported is fixed in the latest version of ocaml-rope, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1042...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Stéphane Glondu (supplier of updated ocaml-rope package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 27 Jul 2023 05:29:25 +0200 Source: ocaml-rope Architecture: source Version: 0.6.2-4 Distribution: unstable Urgency: medium Maintainer: Debian OCaml Maintainers Changed-By: Stéphane Glondu Closes: 1042101 Changes: ocaml-rope (0.6.2-4) unstable; urgency=medium . * Team upload * Use ocaml_dune DH buildsystem (Closes: #1042101) * Bump Standards-Version to 4.6.2 Checksums-Sha1: 17f98ed63cdc7effcdc6766695dbd266b4ec3af0 1954 ocaml-rope_0.6.2-4.dsc 9710618afc95d42797add4353acbad19bb1d7258 3424 ocaml-rope_0.6.2-4.debian.tar.xz Checksums-Sha256: fd4770ff95218b7bea65684382f805465ea6644ae74f610fbc511ad665366094 1954 ocaml-rope_0.6.2-4.dsc d2e9e31d7c1b6cc5ef6dc6896877fd47c0f85a52557042b1f7f5c2c266603404 3424 ocaml-rope_0.6.2-4.debian.tar.xz Files: a4304eda1fd7388237828ae6f54e1b0c 1954 ocaml optional ocaml-rope_0.6.2-4.dsc f5881d7738add7916d0166178eaaa66e 3424 ocaml optional ocaml-rope_0.6.2-4.debian.tar.xz -BEGIN PGP SIGNATURE- iQFGBAEBCgAwFiEEbeJOl+yohsxW5iUOIbju8bGJMIEFAmTB5eQSHGdsb25kdUBk ZWJpYW4ub3JnAAoJECG47vGxiTCBlhwH/ROxNs9I9FDZ01/nYISSYML4BHBjVT5/ XmCSiikEaRLAGzLRIqRFYECOtqCc6Rij4wfjIIinpYWwMf2/RQMrCp81mfz/Mu59 hcValiPirnXKqRPqbD+8vjLx+rm+CoIGHEPpB3MIJkmBkUOYESW3xCGzb8LaWv7m ItDifA1QMZnzqVpoFxB3LDs60MJG4tj6YO9esl4oI86CH53lCHycROlUaoof0ddd E5pv6ZIeB0ZJ0u9+Lg2vI59XwS7NVf+kJajZsDwEYGHlabN315m9phgDfFNIf9KJ rMilesmiBzjds9A0nFELUB9qyMpc1zqZ99EusqhXHRjVLN5V/Sk2DL0= =BbuC -END PGP SIGNATURE End Message ---
Processed: forcibly merging 1037833 1042229
Processing commands for cont...@bugs.debian.org: > forcemerge 1037833 1042229 Bug #1037833 [src:qzxing] qzxing: ftbfs with GCC-13 Bug #1042229 [src:qzxing] qzxing: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below Merged 1037833 1042229 > thanks Stopping processing here. Please contact me if you need assistance. -- 1037833: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037833 1042229: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042229 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1042263: marked as done (postgis: FTBFS: make[2]: *** [regress/runtest.mk:24: check-regress] Error 2)
Your message dated Thu, 27 Jul 2023 05:19:10 +0200 with message-id and subject line Re: Bug#1042263: postgis: FTBFS: make[2]: *** [regress/runtest.mk:24: check-regress] Error 2 has caused the Debian Bug report #1042263, regarding postgis: FTBFS: make[2]: *** [regress/runtest.mk:24: check-regress] Error 2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1042263: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042263 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: postgis Version: 3.3.3+dfsg-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230726 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[3]: Entering directory '/<>/topology/test' > cpp -P -traditional-cpp predicates.sql.in | sed -e > 's:@COLUMN@:feature:g;s:@SCHEMA@:topology.:g' > topo_predicates.sql > cpp -P -traditional-cpp load_topology.sql.in | sed -e 's:@SRID@:-1:g' > > load_topology.sql > cpp -P -traditional-cpp load_topology.sql.in | sed -e 's:@SRID@:4326:g' > > load_topology-4326.sql > make[3]: Leaving directory '/<>/topology/test' > RUNTESTFLAGS: -v --tiger --sfcgal --topology --raster > RUNTESTFLAGS_INTERNAL: --before-upgrade-script > ./raster/test/regress/hooks/hook-before-upgrade-raster.sql > --before-upgrade-script > ./topology/test/regress/hooks/hook-before-upgrade-topology.sql > --before-upgrade-script ./regress/hooks/hook-before-upgrade.sql > --after-upgrade-script ./regress/hooks/hook-after-upgrade.sql > --after-create-script ./regress/hooks/hook-after-create.sql > --before-uninstall-script ./regress/hooks/hook-before-uninstall.sql > --after-upgrade-script > ./topology/test/regress/hooks/hook-after-upgrade-topology.sql > --after-upgrade-script > ./raster/test/regress/hooks/hook-after-upgrade-raster.sql > POSTGIS_TOP_BUILD_DIR=/<> /usr/bin/perl ./regress/run_test.pl -v > --tiger --sfcgal --topology --raster --before-upgrade-script > ./raster/test/regress/hooks/hook-before-upgrade-raster.sql > --before-upgrade-script > ./topology/test/regress/hooks/hook-before-upgrade-topology.sql > --before-upgrade-script ./regress/hooks/hook-before-upgrade.sql > --after-upgrade-script ./regress/hooks/hook-after-upgrade.sql > --after-create-script ./regress/hooks/hook-after-create.sql > --before-uninstall-script ./regress/hooks/hook-before-uninstall.sql > --after-upgrade-script > ./topology/test/regress/hooks/hook-after-upgrade-topology.sql > --after-upgrade-script > ./raster/test/regress/hooks/hook-after-upgrade-raster.sql > ./regress/core/affine ./regress/core/bestsrid ./regress/core/binary > ./regress/core/boundary ./regress/core/chaikin ./regress/core/filterm > ./regress/core/cluster ./regress/core/ctors ./regress/core/curvetoline > ./regress/core/dump ./regress/core/dumppoints ./regress/core/dumpsegments > ./regress/core/empty ./regress/core/estimatedextent ./regress/core/forcecurve > ./regress/core/flatgeobuf ./regress/core/geography > ./regress/core/geometric_median ./regress/core/geos_noop > ./regress/core/hausdorff ./regress/core/in_flatgeobuf > ./regress/core/in_geohash ./regress/core/in_gml ./regress/core/in_kml > ./regress/core/in_marc21 ./regress/core/out_marc21 > ./regress/core/in_encodedpolyline ./regress/core/iscollection > ./regress/core/legacy ./regress/core/letters ./regress/core/long_xact > ./regress/core/lwgeom_regress ./regress/core/measures > ./regress/core/minimum_bounding_circle ./regress/core/normalize > ./regress/core/operators ./regress/core/orientation > ./regress/core/out_flatgeobuf ./regress/core/out_geometry > ./regress/core/out_geography ./regress/core/out_gml ./regress/core/polygonize > ./regress/core/polyhedralsurface ./regress/core/postgis_type_name > ./regress/core/quantize_coordinates ./regress/core/regress > ./regress/core/regress_bdpoly ./regress/core/regress_buffer_params > ./regress/core/regress_gist_index_nd ./regress/core/regress_index > ./regress/core/regress_index_nulls ./regress/core/regress_management > ./regress/core/regress_selectivity ./regress/core/regress_lrs > ./regress/core/regress_ogc ./regress/core/regress_ogc_cover > ./regress/core/regress_ogc_prep ./regress/core/regress_proj_basic > ./regress/core/regress_proj_adhoc ./regress/core/regress_proj_cache
Bug#1042203: marked as done (saga: FTBFS: dh_install: error: missing files, aborting)
Your message dated Thu, 27 Jul 2023 05:17:56 +0200 with message-id <5be6d84b-ffd3-3482-7631-9e69824f4...@xs4all.nl> and subject line Re: Bug#1042203: saga: FTBFS: dh_install: error: missing files, aborting has caused the Debian Bug report #1042203, regarding saga: FTBFS: dh_install: error: missing files, aborting to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1042203: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042203 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: saga Version: 9.1.0+dfsg-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230726 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[3]: Entering directory '/<>/obj-x86_64-linux-gnu' > make[3]: Nothing to be done for 'preinstall'. > make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu' > Install the project... > /usr/bin/cmake -P cmake_install.cmake > -- Install configuration: "None" > -- Installing: /<>/debian/tmp/usr/share/saga/toolchains > -- Installing: > /<>/debian/tmp/usr/share/saga/toolchains/gc_filter_simple.xml > -- Installing: > /<>/debian/tmp/usr/share/saga/toolchains/grid_statistics_for_directions.xml > -- Installing: > /<>/debian/tmp/usr/share/saga/toolchains/imagery_lczc.xml > -- Installing: > /<>/debian/tmp/usr/share/saga/toolchains/grid_tools_bulk_no-data_change.xml > -- Installing: > /<>/debian/tmp/usr/share/saga/toolchains/climate_tools.xml > -- Installing: > /<>/debian/tmp/usr/share/saga/toolchains/gc_filter_laplacian.xml > -- Installing: > /<>/debian/tmp/usr/share/saga/toolchains/shapes_select_delete.xml > -- Installing: > /<>/debian/tmp/usr/share/saga/toolchains/imagery.xml > -- Installing: > /<>/debian/tmp/usr/share/saga/toolchains/ta_ls_factor.xml > -- Installing: > /<>/debian/tmp/usr/share/saga/toolchains/imagery_classify_majority.xml > -- Installing: > /<>/debian/tmp/usr/share/saga/toolchains/tta_TravelTime.xml > -- Installing: > /<>/debian/tmp/usr/share/saga/toolchains/terrain_analysis.xml > -- Installing: > /<>/debian/tmp/usr/share/saga/toolchains/gc_tools.xml > -- Installing: > /<>/debian/tmp/usr/share/saga/toolchains/gc_filter_rank.xml > -- Installing: > /<>/debian/tmp/usr/share/saga/toolchains/cluster_terrain.xml > -- Installing: > /<>/debian/tmp/usr/share/saga/toolchains/terrain_segmentation.xml > -- Installing: > /<>/debian/tmp/usr/share/saga/toolchains/grid_and_polygon_to_table.xml > -- Installing: > /<>/debian/tmp/usr/share/saga/toolchains/polygons_remove_from_boundary.xml > -- Installing: > /<>/debian/tmp/usr/share/saga/toolchains/sieve_and_clump.xml > -- Installing: > /<>/debian/tmp/usr/share/saga/toolchains/grid_notch_filter.xml > -- Installing: > /<>/debian/tmp/usr/share/saga/toolchains/polygons_max_interior_circles.xml > -- Installing: > /<>/debian/tmp/usr/share/saga/toolchains/group_files.xml > -- Installing: > /<>/debian/tmp/usr/share/saga/toolchains/ta_summits.xml > -- Installing: /<>/debian/tmp/usr/share/saga/toolchains/twi.xml > -- Installing: > /<>/debian/tmp/usr/share/saga/toolchains/gridding.xml > -- Installing: > /<>/debian/tmp/usr/share/saga/toolchains/temperature_downscaling_bulk.xml > -- Installing: > /<>/debian/tmp/usr/share/saga/toolchains/points_to_contour.xml > -- Installing: > /<>/debian/tmp/usr/share/saga/toolchains/upslope_height.xml > -- Installing: > /<>/debian/tmp/usr/share/saga/toolchains/import_text_tables.xml > -- Installing: > /<>/debian/tmp/usr/share/saga/toolchains/tta_LandCover.xml > -- Installing: /<>/debian/tmp/usr/share/saga/toolchains/obia.xml > -- Installing: > /<>/debian/tmp/usr/share/saga/toolchains/tta_tools.xml > -- Installing: > /<>/debian/tmp/usr/share/saga/toolchains/grid_filter.xml > -- Installing: > /<>/debian/tmp/usr/share/saga/toolchains/grid_list_simple_filter.xml > -- Installing: > /<>/debian/tmp/usr/share/saga/toolchains/gc_longitudinal_range.xml > -- Installing: > /<>/debian/tmp/usr/share/saga/toolchains/ta_flow_accumulation.xml > -- Installing: > /<>/debian/t
Bug#1042151: marked as done (rust-zoxide: FTBFS: build-dependency not installable: librust-dirs-4+default-dev)
Your message dated Thu, 27 Jul 2023 03:55:31 +0100 with message-id and subject line re: rust-zoxide: FTBFS: build-dependency not installable: librust-dirs-4+default-dev has caused the Debian Bug report #1042151, regarding rust-zoxide: FTBFS: build-dependency not installable: librust-dirs-4+default-dev to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1042151: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042151 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: rust-zoxide Version: 0.4.3-5 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230726 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: debhelper (>= 12), dh-cargo (>= 25), cargo, rustc, > libstd-rust-dev, librust-anyhow-1+default-dev (>= 1.0.28-~~), > librust-bincode-1+default-dev (>= 1.3.1-~~), librust-clap-2+default-dev (>= > 2.33.0-~~), librust-dirs-4+default-dev | librust-dirs-3+default-dev, > librust-dunce-1+default-dev, librust-float-ord-0.3+default-dev, > librust-serde-1+default-dev (>= 1.0.106-~~), librust-serde-1+derive-dev (>= > 1.0.106-~~), librust-structopt-0.3+default-dev (>= 0.3.12-~~), > librust-uuid-1+default-dev, librust-uuid-1+v4-dev, help2man, build-essential, > fakeroot > Filtered Build-Depends: debhelper (>= 12), dh-cargo (>= 25), cargo, rustc, > libstd-rust-dev, librust-anyhow-1+default-dev (>= 1.0.28-~~), > librust-bincode-1+default-dev (>= 1.3.1-~~), librust-clap-2+default-dev (>= > 2.33.0-~~), librust-dirs-4+default-dev, librust-dunce-1+default-dev, > librust-float-ord-0.3+default-dev, librust-serde-1+default-dev (>= > 1.0.106-~~), librust-serde-1+derive-dev (>= 1.0.106-~~), > librust-structopt-0.3+default-dev (>= 0.3.12-~~), librust-uuid-1+default-dev, > librust-uuid-1+v4-dev, help2man, build-essential, fakeroot > dpkg-deb: building package 'sbuild-build-depends-main-dummy' in > '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'. > Ign:1 copy:/<>/apt_archive ./ InRelease > Get:2 copy:/<>/apt_archive ./ Release [963 B] > Ign:3 copy:/<>/apt_archive ./ Release.gpg > Get:4 copy:/<>/apt_archive ./ Sources [529 B] > Get:5 copy:/<>/apt_archive ./ Packages [610 B] > Fetched 2102 B in 0s (178 kB/s) > Reading package lists... > Reading package lists... > > Install main build dependencies (apt-based resolver) > > > Installing build dependencies > Reading package lists... > Building dependency tree... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > sbuild-build-depends-main-dummy : Depends: librust-dirs-4+default-dev but it > is not installable > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://qa-logs.debian.net/2023/07/26/rust-zoxide_0.4.3-5_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230726;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230726=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Version: 0.4.3-6 Fixed in 0.4.3-6--- End Message ---
Bug#1042228: marked as done (rust-sequoia-net: FTBFS: build-dependency not installable: librust-base64-0.13+default-dev)
Your message dated Thu, 27 Jul 2023 02:46:31 + with message-id and subject line Bug#1042228: fixed in rust-sequoia-net 0.26.0-4 has caused the Debian Bug report #1042228, regarding rust-sequoia-net: FTBFS: build-dependency not installable: librust-base64-0.13+default-dev to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1042228: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042228 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: rust-sequoia-net Version: 0.26.0-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230726 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: debhelper (>= 12), dh-cargo (>= 25), cargo, rustc, > libstd-rust-dev, librust-anyhow-1+default-dev (>= 1.0.18-~~), > librust-base64-0.13+default-dev | librust-base64-0.12+default-dev, > librust-futures-util-0.3+default-dev (>= 0.3.5-~~), > librust-http-0.2+default-dev, librust-hyper-0.14+default-dev (>= 0.14.10-~~), > librust-hyper-0.14+http1-dev (>= 0.14.10-~~), librust-hyper-0.14+http2-dev > (>= 0.14.10-~~), librust-hyper-tls-0.5+default-dev, > librust-libc-0.2+default-dev (>= 0.2.66-~~), > librust-native-tls-0.2+default-dev, librust-percent-encoding-2+default-dev > (>= 2.1-~~), librust-sequoia-openpgp-1-dev (>= 1.13-~~), > librust-tempfile-3+default-dev (>= 3.1-~~), librust-thiserror-1+default-dev > (>= 1.0.2-~~), librust-tokio-1+default-dev (>= 1.13.1-~~), > librust-tokio-1+macros-dev (>= 1.13.1-~~), > librust-trust-dns-client-0.22+default-dev, > librust-trust-dns-resolver-0.22+default-dev, > librust-trust-dns-resolver-0.22+dnssec-ring-dev, librust-url-2+default-dev > (>= 2.1-~~), librust-zbase32-0.1+default-dev (>= 0.1.2-~~), build-essential, > fakeroot > Filtered Build-Depends: debhelper (>= 12), dh-cargo (>= 25), cargo, rustc, > libstd-rust-dev, librust-anyhow-1+default-dev (>= 1.0.18-~~), > librust-base64-0.13+default-dev, librust-futures-util-0.3+default-dev (>= > 0.3.5-~~), librust-http-0.2+default-dev, librust-hyper-0.14+default-dev (>= > 0.14.10-~~), librust-hyper-0.14+http1-dev (>= 0.14.10-~~), > librust-hyper-0.14+http2-dev (>= 0.14.10-~~), > librust-hyper-tls-0.5+default-dev, librust-libc-0.2+default-dev (>= > 0.2.66-~~), librust-native-tls-0.2+default-dev, > librust-percent-encoding-2+default-dev (>= 2.1-~~), > librust-sequoia-openpgp-1-dev (>= 1.13-~~), librust-tempfile-3+default-dev > (>= 3.1-~~), librust-thiserror-1+default-dev (>= 1.0.2-~~), > librust-tokio-1+default-dev (>= 1.13.1-~~), librust-tokio-1+macros-dev (>= > 1.13.1-~~), librust-trust-dns-client-0.22+default-dev, > librust-trust-dns-resolver-0.22+default-dev, > librust-trust-dns-resolver-0.22+dnssec-ring-dev, librust-url-2+default-dev > (>= 2.1-~~), librust-zbase32-0.1+default-dev (>= 0.1.2-~~), build-essential, > fakeroot > dpkg-deb: building package 'sbuild-build-depends-main-dummy' in > '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'. > Ign:1 copy:/<>/apt_archive ./ InRelease > Get:2 copy:/<>/apt_archive ./ Release [963 B] > Ign:3 copy:/<>/apt_archive ./ Release.gpg > Get:4 copy:/<>/apt_archive ./ Sources [660 B] > Get:5 copy:/<>/apt_archive ./ Packages [726 B] > Fetched 2349 B in 0s (154 kB/s) > Reading package lists... > Reading package lists... > > Install main build dependencies (apt-based resolver) > > > Installing build dependencies > Reading package lists... > Building dependency tree... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: >
Bug#1029331: marked as done (librust-snapbox-dev has unmet dependencies)
Your message dated Thu, 27 Jul 2023 02:46:43 + with message-id and subject line Bug#1029331: fixed in rust-snapbox 0.4.8-1 has caused the Debian Bug report #1029331, regarding librust-snapbox-dev has unmet dependencies to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1029331: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029331 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: librust-snapbox-dev Version: 0.3.3-1 Severity: serious The following packages have unmet dependencies: librust-snapbox-dev : Depends: librust-concolor-0.0.8+auto-dev but it is not installable Depends: librust-concolor-0.0.8+default-dev but it is not installable Depends: librust-concolor-0.0.8+std-dev but it is not installable Depends: librust-document-features-0.2+default-dev (>= 0.2.3-~~) but it is not installable Depends: librust-libtest-mimic-0.4+default-dev but it is not installable --- End Message --- --- Begin Message --- Source: rust-snapbox Source-Version: 0.4.8-1 Done: Peter Michael Green We believe that the bug you reported is fixed in the latest version of rust-snapbox, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1029...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Peter Michael Green (supplier of updated rust-snapbox package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 27 Jul 2023 01:43:40 + Source: rust-snapbox Architecture: source Version: 0.4.8-1 Distribution: unstable Urgency: medium Maintainer: Debian Rust Maintainers Changed-By: Peter Michael Green Closes: 1029331 Changes: rust-snapbox (0.4.8-1) unstable; urgency=medium . * Package snapbox 0.4.8 from crates.io using debcargo 2.6.0 . [ Blair Noctis ] * Team upload. * Package snapbox 0.4.8 from crates.io using debcargo 2.6.0 (Closes: #1029331) * Patch out Windows deps * Mark flaky tests for features document-features, structured-data * Remove "examples" feature and optional dependency on escargot. Checksums-Sha1: f1244566391e0130c3d56562339f671cf8a01532 2612 rust-snapbox_0.4.8-1.dsc 8cc5b09322c0303bae3cb2b84d2562e8317c54a8 34929 rust-snapbox_0.4.8.orig.tar.gz 29161a8a76d3ed87890851cf7634526da6823142 3948 rust-snapbox_0.4.8-1.debian.tar.xz d5af3e04320e57f4d0b4de7b119e544f780ac332 8026 rust-snapbox_0.4.8-1_source.buildinfo Checksums-Sha256: 2f4ac4f2252609418bdebdec2a924a65469ac2d73d812cdfb6c06e7f9e64688c 2612 rust-snapbox_0.4.8-1.dsc 4389a6395e9925166f19d67b64874e526ec28a4b8455f3321b686c912299c3ea 34929 rust-snapbox_0.4.8.orig.tar.gz 033e447a6d9d606b19d26ad7ffb64fe2609853152015facc8b75f44f323f5962 3948 rust-snapbox_0.4.8-1.debian.tar.xz a744a61dfb093cf138c8c27e47e96f8af156ffe998d073f3371ceae95f566cb5 8026 rust-snapbox_0.4.8-1_source.buildinfo Files: 1fce829880e6c62e9675704f9fcc40fd 2612 rust optional rust-snapbox_0.4.8-1.dsc 419806502d26a122316d5623cbc9a3e3 34929 rust optional rust-snapbox_0.4.8.orig.tar.gz 29f65319b8ad1d923b5804b059893250 3948 rust optional rust-snapbox_0.4.8-1.debian.tar.xz a00e4aab9a1aa75f6127dcd5e6981142 8026 rust optional rust-snapbox_0.4.8-1_source.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCAAyFiEEU0DQATYMplbjSX63DEjqKnqP/XsFAmTBzSsUHHBsdWd3YXNo QGRlYmlhbi5vcmcACgkQDEjqKnqP/Xu8oQ//U7C4SVGINogYpKksnIVRwly8gs7w uBHBpUWnjUqFh8fKxRjG1KK+GsUJfCAza05XUM9jOl3DUPPIFIx3Vi9lkJ1fbTSi PmZBfCVt4zir9wuCGCFSSnM2kJaLL2UQoQtY7ZFWzz7woV/OyKeL5Ii/13UKzss5 ecZ1uVBNfQa1R1av6unOErhcr8p+rQoIJbPx+5nyNLovcq/FNEFpvjjeZK/vyUnL xtS/E9qvANCHVCjBiWavFtNFmtqup7mi76G8+z6TGF2Nh66dHk+ciICv1UTlDHAx OWaGI5uvAujszcrJhq2VSriU7jVjwPJUtY5crQ9agAKnAgWaEwHVeX7NEQ5LOQqF Ae54IcgndNq1WoRG0FtoYwEkMFoO/R8H33WhD5oOPu089jurIP+l+Sd9eqat55R6 J/rY/NpUrYiULOJ/LMp1+YDk/QPPJxyW3xMFdCTB0tyTzm/uDuuAT5d+tYzaUPks k/rSfOBKiC8gfl4yR0T2S5hO5D89pXXt2MVz8U5Wcf2AYQON36+TCAMDxrrmbvFZ g0wj9OW3YzE2xmO+9iICCZiT+eNHAh41v4wiXCi1vWWH6Rk77rX3Tan+XphZQF8c kxI3MqBX/gdHkbHrBeGs5mtmhNy7CiaiA8FPfoIQyHd47xxY51vBgfdoWhMMKeU6 01FVRI+ozG4XsYI= =QyGf -END PGP SIGNATURE End Message ---
Bug#1037839: marked as done (repowerd: ftbfs with GCC-13)
Your message dated Thu, 27 Jul 2023 02:45:22 + with message-id and subject line Bug#1037839: fixed in repowerd 2023.07-1 has caused the Debian Bug report #1037839, regarding repowerd: ftbfs with GCC-13 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1037839: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037839 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:repowerd Version: 2022.01-3 Severity: normal Tags: sid trixie User: debian-...@lists.debian.org Usertags: ftbfs-gcc-13 [This bug is targeted to the upcoming trixie release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-13/g++-13, but succeeds to build with gcc-12/g++-12. The severity of this report will be raised before the trixie release. The full build log can be found at: http://qa-logs.debian.net/2023/05/22/logs/repowerd_2022.01-3_unstable_gccexp.log The last lines of the build log are at the end of this report. To build with GCC 13, either set CC=gcc-13 CXX=g++-13 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-13/porting_to.html [...] cd /<>/obj-x86_64-linux-gnu/googletest && /usr/bin/cmake -P CMakeFiles/gtest.dir/cmake_clean_target.cmake cd /<>/obj-x86_64-linux-gnu/googletest && /usr/bin/cmake -E cmake_link_script CMakeFiles/gtest.dir/link.txt --verbose=1 /usr/bin/ar qc /<>/obj-x86_64-linux-gnu/gmock/lib/libgtest.a "CMakeFiles/gtest.dir/src/gtest-all.cc.o" /usr/bin/ranlib /<>/obj-x86_64-linux-gnu/gmock/lib/libgtest.a make[6]: Leaving directory '/<>/obj-x86_64-linux-gnu/gmock' [ 25%] Built target gtest make -f CMakeFiles/gmock.dir/build.make CMakeFiles/gmock.dir/depend make -f /<>/obj-x86_64-linux-gnu/googletest/CMakeFiles/gtest_main.dir/build.make /<>/obj-x86_64-linux-gnu/googletest/CMakeFiles/gtest_main.dir/depend make[6]: Entering directory '/<>/obj-x86_64-linux-gnu/gmock' cd /<>/obj-x86_64-linux-gnu/gmock && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /usr/src/googletest/googlemock /usr/src/googletest/googlemock /<>/obj-x86_64-linux-gnu/gmock /<>/obj-x86_64-linux-gnu/gmock /<>/obj-x86_64-linux-gnu/gmock/CMakeFiles/gmock.dir/DependInfo.cmake --color= make[6]: Entering directory '/<>/obj-x86_64-linux-gnu/gmock' cd /<>/obj-x86_64-linux-gnu/gmock && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /usr/src/googletest/googlemock /usr/src/googletest/googletest /<>/obj-x86_64-linux-gnu/gmock /<>/obj-x86_64-linux-gnu/googletest /<>/obj-x86_64-linux-gnu/googletest/CMakeFiles/gtest_main.dir/DependInfo.cmake --color= make[6]: Leaving directory '/<>/obj-x86_64-linux-gnu/gmock' make[6]: Leaving directory '/<>/obj-x86_64-linux-gnu/gmock' make -f CMakeFiles/gmock.dir/build.make CMakeFiles/gmock.dir/build make -f /<>/obj-x86_64-linux-gnu/googletest/CMakeFiles/gtest_main.dir/build.make /<>/obj-x86_64-linux-gnu/googletest/CMakeFiles/gtest_main.dir/build make[6]: Entering directory '/<>/obj-x86_64-linux-gnu/gmock' make[6]: Entering directory '/<>/obj-x86_64-linux-gnu/gmock' [ 37%] Building CXX object CMakeFiles/gmock.dir/src/gmock-all.cc.o /usr/bin/c++ -I/usr/src/googletest/googlemock/include -I/usr/src/googletest/googlemock -isystem /usr/src/googletest/googletest/include -isystem /usr/src/googletest/googletest -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -g -pthread -std=c++14 -Werror -Wall -Wnon-virtual-dtor -Wextra -pedantic -g -Wno-old-style-cast -Wno-missing-field-initializers -Wno-ctor-dtor-privacy -Wno-switch-default -Wall -Wshadow -Wno-error=dangling-else -DGTEST_HAS_PTHREAD=1 -fexceptions -Wextra -Wno-unused-parameter -Wno-missing-field-initializers -DGTEST_HAS_PTHREAD=1 -MD -MT CMakeFiles/gmock.dir/src/gmock-all.cc.o -MF CMakeFiles/gmock.dir/src/gmock-all.cc.o.d -o CMakeFiles/gmock.dir/src/gmock-all.cc.o -c /usr/src/googletest/googlemock/src/gmock-all.cc [ 50%] Building CXX object /<>/obj-x86_64-linux-gnu/googletest/CMakeFiles/gtest_main.dir/src/gtest_main.cc.o cd
Bug#1041372: marked as done (xtensor autopkg tests fail on i386 and s390x)
Your message dated Thu, 27 Jul 2023 00:20:39 +
with message-id
and subject line Bug#1041372: fixed in xtensor 0.24.3-2
has caused the Debian Bug report #1041372,
regarding xtensor autopkg tests fail on i386 and s390x
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1041372: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041372
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:xtensor
Version: 0.24.3-1
Severity: serious
Tags: sid trixie
xtensor autopkg tests fail on i386 and s390x, see
https://ci.debian.net/data/autopkgtest/testing/i386/x/xtensor/35913428/log.gz
829s Built without XSIMD
829s Built without XSIMD
829s
===
829s
/tmp/autopkgtest-lxc.vtoe34gr/downtmp/autopkgtest_tmp/test_xbuilder.cpp:145:
829s TEST CASE: xbuilder.arange_min_max_step
829s
829s
/tmp/autopkgtest-lxc.vtoe34gr/downtmp/autopkgtest_tmp/test_xbuilder.cpp:165:
FATAL ERROR: REQUIRE_EQ( 3.f * 0.3f,l3[{3}] ) is NOT correct!
829s values: REQUIRE_EQ( 0.9, 0.9 )
829s
829s
===
829s
/tmp/autopkgtest-lxc.vtoe34gr/downtmp/autopkgtest_tmp/test_xcomplex.cpp:298:
829s TEST CASE: xcomplex.longdouble
829s
829s
/tmp/autopkgtest-lxc.vtoe34gr/downtmp/autopkgtest_tmp/test_xcomplex.cpp:305:
ERROR: CHECK_EQ( a(4, 4),cmplx(123.321, -123.321) ) is NOT correct!
829s values: CHECK_EQ( (123.321,-123.321), (123.321,-123.321) )
829s
829s
/tmp/autopkgtest-lxc.vtoe34gr/downtmp/autopkgtest_tmp/test_xcomplex.cpp:309:
ERROR: CHECK_EQ( a(0, 0),cmplx(-123.321, -123.321) ) is NOT correct!
829s values: CHECK_EQ( (-123.321,-123.321), (-123.321,-123.321) )
829s
829s
/tmp/autopkgtest-lxc.vtoe34gr/downtmp/autopkgtest_tmp/test_xcomplex.cpp:310:
ERROR: CHECK_EQ( a(4, 4),cmplx(-123.321, -123.321) ) is NOT correct!
829s values: CHECK_EQ( (-123.321,-123.321), (-123.321,-123.321) )
829s
829s
===
829s [doctest] test cases: 1185 | 1183 passed | 2 failed | 0 skipped
https://ci.debian.net/data/autopkgtest/testing/s390x/x/xtensor/35911766/log.gz
193s
===
193s
/tmp/autopkgtest-lxc._9ej_xfd/downtmp/autopkgtest_tmp/test_xbuilder.cpp:145:
193s TEST CASE: xbuilder.arange_min_max_step
193s
193s
/tmp/autopkgtest-lxc._9ej_xfd/downtmp/autopkgtest_tmp/test_xbuilder.cpp:165:
FATAL ERROR: REQUIRE_EQ( 3.f * 0.3f,l3[{3}] ) is NOT correct!
193s values: REQUIRE_EQ( 0.9, 0.9 )
193s
193s
===
193s [doctest] test cases: 1185 | 1184 passed | 1 failed | 0 skipped
193s [doctest] assertions: 19465 | 19464 passed | 1 failed |
193s [doctest] Status: FAILURE!
--- End Message ---
--- Begin Message ---
Source: xtensor
Source-Version: 0.24.3-2
Done: Drew Parsons
We believe that the bug you reported is fixed in the latest version of
xtensor, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1041...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Drew Parsons (supplier of updated xtensor package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Thu, 27 Jul 2023 00:10:32 +0200
Source: xtensor
Architecture: source
Version: 0.24.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers
Changed-By: Drew Parsons
Closes: 1041372
Changes:
xtensor (0.24.3-2) unstable; urgency=medium
.
* debian patch gcc13_test_precision.patch fixes test failures
triggered by precision changes in gcc-13. Closes: #1041372.
Checksums-Sha1:
75f34d0affb49e8ce148796aa3bc24f7bf59f787 2510 xtensor_0.24.3-2.dsc
ffaf76dd386293b889c04c75705533aa4a12ad10 9576 xtensor_0.24.3-2.debian.tar.xz
Checksums-Sha256:
a1a82c03859865d308c7face048c092a25de1699b34a597a6b9ff0da9c94e1d4 2510
xtensor_0.24.3-2.dsc
3a78bec9d4a5129ff345617a956162b2ee7f9af023c25dac76b4aab8a7082187 9576
xtensor_0.24.3-2.debian.tar.xz
Files:
27aeec46e1172263aa17b0d37dbfa552 2510 libs optional
Bug#1042156: marked as done (rust-droid-juicer: FTBFS: build-dependency not installable: librust-goblin-0.2+default-dev)
Your message dated Wed, 26 Jul 2023 23:51:02 + with message-id and subject line Bug#1042156: fixed in rust-droid-juicer 0.2.0-3 has caused the Debian Bug report #1042156, regarding rust-droid-juicer: FTBFS: build-dependency not installable: librust-goblin-0.2+default-dev to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1042156: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042156 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: rust-droid-juicer Version: 0.2.0-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230726 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: debhelper (>= 12), dh-cargo (>= 25), cargo, rustc, > libstd-rust-dev, librust-clap-4+default-dev, librust-clap-4+derive-dev, > librust-goblin-0.2+default-dev, librust-serde-1+default-dev, > librust-serde-1+derive-dev, librust-serde-json-1+default-dev, > librust-sys-mount-2+default-dev, librust-toml-0.5+default-dev, > librust-uname-0.1+default-dev, build-essential, fakeroot > Filtered Build-Depends: debhelper (>= 12), dh-cargo (>= 25), cargo, rustc, > libstd-rust-dev, librust-clap-4+default-dev, librust-clap-4+derive-dev, > librust-goblin-0.2+default-dev, librust-serde-1+default-dev, > librust-serde-1+derive-dev, librust-serde-json-1+default-dev, > librust-sys-mount-2+default-dev, librust-toml-0.5+default-dev, > librust-uname-0.1+default-dev, build-essential, fakeroot > dpkg-deb: building package 'sbuild-build-depends-main-dummy' in > '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'. > Ign:1 copy:/<>/apt_archive ./ InRelease > Get:2 copy:/<>/apt_archive ./ Release [957 B] > Ign:3 copy:/<>/apt_archive ./ Release.gpg > Get:4 copy:/<>/apt_archive ./ Sources [462 B] > Get:5 copy:/<>/apt_archive ./ Packages [546 B] > Fetched 1965 B in 0s (133 kB/s) > Reading package lists... > Reading package lists... > > Install main build dependencies (apt-based resolver) > > > Installing build dependencies > Reading package lists... > Building dependency tree... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > sbuild-build-depends-main-dummy : Depends: librust-goblin-0.2+default-dev > but it is not installable > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://qa-logs.debian.net/2023/07/26/rust-droid-juicer_0.2.0-2_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230726;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230726=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: rust-droid-juicer Source-Version: 0.2.0-3 Done: Peter Michael Green We believe that the bug you reported is fixed in the latest version of rust-droid-juicer, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1042...@bugs.debian.org, and the maintainer will reopen the bug rep
Bug#1042156: rust-droid-juicer- call for testing of goblin update.
I've just patched rust-droid-juicer to use the new version of goblin. It built fine, but given the lack of any meaningful tests in the package I don't feel comfortable uploading it to unstable until someone more familiar with the software has tested it. I have uploaded the patched version to experimental to make it easier for people to test.
Processed: Re: Bug#1042289: magit: FTBFS: Debugger entered--Lisp error: (file-missing "Cannot open load file" "No such file or directory" "compat")
Processing commands for cont...@bugs.debian.org: > tags 1042289 patch Bug #1042289 [src:magit] magit: FTBFS: Debugger entered--Lisp error: (file-missing "Cannot open load file" "No such file or directory" "compat") Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 1042289: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042289 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1042289: magit: FTBFS: Debugger entered--Lisp error: (file-missing "Cannot open load file" "No such file or directory" "compat")
tags 1042289 patch
thanks
Lucas Nussbaum writes:
> Source: magit
> Version: 3.3.0-2
> Severity: serious
> Justification: FTBFS
> Tags: trixie sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20230726 ftbfs-trixie
>
> Hi,
>
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
>
>
> Relevant part (hopefully):
>> make[2]: Entering directory '/<>'
>> Loading /<>/t/magit-tests.el (source)...
>> Debugger entered--Lisp error: (file-missing "Cannot open load file" "No such
>> file or directory" "compat")
>> require(compat)
>>
>> load-with-code-conversion("/usr/share/emacs/site-lisp/elpa-src/with-editor-3"
>> "/usr/share/emacs/site-lisp/elpa-src/with-editor-3" nil t)
>> require(with-editor)
>> load-with-code-conversion("/<>/lisp/magit-process..."
>> "/<>/lisp/magit-process..." nil t)
>> require(magit-process)
>> load-with-code-conversion("/<>/lisp/magit-transie..."
>> "/<>/lisp/magit-transie..." nil t)
>> require(magit-transient)
>> load-with-code-conversion("/<>/lisp/magit-margin"
>> "/<>/lisp/magit-margin" nil t)
>> require(magit-margin)
>> load-with-code-conversion("/<>/lisp/magit-core.el"
>> "/<>/lisp/magit-core.el" nil t)
>> require(magit-core)
>> load-with-code-conversion("/<>/lisp/magit.el"
>> "/<>/lisp/magit.el" nil t)
>> require(magit)
>> load-with-code-conversion("/<>/t/magit-tests.el"
>> "/<>/t/magit-tests.el" nil nil)
>> load-file("t/magit-tests.el")
>> (progn (load-file "t/magit-tests.el") (ert-run-tests-batch-and-exit))
>> command-line-1(("-L" "./lisp" "-L"
>> "/usr/share/emacs/site-lisp/elpa-src/dash-2.19.1" "-L" "./../libgit" "-L"
>> "/usr/share/emacs/site-lisp/elpa-src/transient-0.3" "-L"
>> "/usr/share/emacs/site-lisp/elpa-src/with-editor-3" "--eval" "(progn
>> (load-file \"t/magit-tests.el\")(ert-r..."))
>> command-line()
>> normal-top-level()
>>
>> make[2]: *** [Makefile:111: test] Error 255
>
>
> The full build log is available from:
> http://qa-logs.debian.net/2023/07/26/magit_3.3.0-2_unstable.log
>
> All bugs filed during this archive rebuild are listed at:
> https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230726;users=lu...@debian.org
> or:
> https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230726=lu...@debian.org=1=1=1=1#results
>
> A list of current common problems and possible solutions is available at
> http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
>
> If you reassign this bug to another package, please mark it as 'affects'-ing
> this package. See https://www.debian.org/Bugs/server-control#affects
>
> If you fail to reproduce this, please provide a build log and diff it with
> mine
> so that we can identify if something relevant changed in the meantime.
>
This is due to newer with-editor starts to depend on compat while magit
hasn't done it in 3.3.0 yet. I have prepared a merge request[1] that
cherrypicks the necessary upstream commit that fixes the compat
detection, as well as a few lintian fixes. PTAL. Thanks!
[1] https://salsa.debian.org/emacsen-team/magit/-/merge_requests/2
--
Manphiz
Bug#1042173: marked as done (openlp: FTBFS: AttributeError: module 'PIL.ImageQt' has no attribute 'ImageQt')
Your message dated Wed, 26 Jul 2023 23:20:00 + with message-id and subject line Bug#1042173: fixed in openlp 3.0.2-3 has caused the Debian Bug report #1042173, regarding openlp: FTBFS: AttributeError: module 'PIL.ImageQt' has no attribute 'ImageQt' to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1042173: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042173 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: openlp Version: 3.0.2-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230726 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > QT_QPA_PLATFORM=offscreen dh_auto_test > I: pybuild base:240: cd /<>/.pybuild/cpython3_3.11_openlp/build; > python3.11 -m pytest -k 'not test_load_settings_position_invalid and not > test_get_directory_for_language_dir_from_source and not > test_get_ip_address_default' > = test session starts > == > platform linux -- Python 3.11.4, pytest-7.4.0, pluggy-1.2.0 > PyQt5 5.15.9 -- Qt runtime 5.15.10 -- Qt compiled 5.15.10 > rootdir: /<> > configfile: setup.cfg > plugins: qt-4.2.0+repack > collected 2288 items / 3 deselected / 1 skipped / 2285 selected > > tests/openlp_core/test_app.py ...[ > 0%] > tests/openlp_core/test_server.py . [ > 0%] > tests/openlp_core/test_state.py ... [ > 1%] > tests/openlp_core/test_threading.py .[ > 1%] > tests/openlp_core/test_version.py ...[ > 2%] > tests/openlp_core/api/test_deploy.py ... [ > 2%] > tests/openlp_core/api/test_main.py . [ > 2%] > tests/openlp_core/api/test_tab.py EEEFE [ > 3%] > tests/openlp_core/api/test_websockets.py .. [ > 4%] > tests/openlp_core/api/endpoint/test_controller.py [ > 4%] > tests/openlp_core/api/http_server/test_http.py ..[ > 4%] > tests/openlp_core/api/http_server/test_init.py ... [ > 4%] > tests/openlp_core/api/v2/test_controller.py [ > 6%] > [ > 6%] > tests/openlp_core/api/v2/test_core.py .. [ > 6%] > tests/openlp_core/api/v2/test_plugins.py . [ > 7%] > tests/openlp_core/api/v2/test_service.py [ > 7%] > tests/openlp_core/common/test_actions.py .. [ > 8%] > tests/openlp_core/common/test_applocation.py [ > 8%] > tests/openlp_core/common/test_db.py .. [ > 8%] > tests/openlp_core/common/test_handlers.py . [ > 8%] > tests/openlp_core/common/test_httputils.py ..[ > 9%] > tests/openlp_core/common/test_i18n.py [ > 10%] > tests/openlp_core/common/test_init.py .. [ > 11%] > .. [ > 12%] > tests/openlp_core/common/test_json.py .. [ > 13%] > tests/openlp_core/common/test_mixins.py [ > 13%] > tests/openlp_core/common/test_network_interfaces.py .. [ > 13%] > tests/openlp_core/common/test_path.py . [ > 14%] > tests/openlp_core/common/test_platform.py . [ > 14%] > tests/openlp_core/common/test_registry.py .. [ > 14%] > tests/openlp_core/common/test_settings.py ...[ > 15%] > tests/openlp_core/common/test_utils.py ... [ > 16%] > tests/openlp_core/display/test_render.py .. [ > 16%] > tests/openlp_core/display/test_screens.py ...
Bug#1041135: marked as done (libusermetrics FTBFS with googletest 1.13.0)
Your message dated Wed, 26 Jul 2023 23:19:48 + with message-id and subject line Bug#1041135: fixed in libusermetrics 1.3.0-2 has caused the Debian Bug report #1041135, regarding libusermetrics FTBFS with googletest 1.13.0 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1041135: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041135 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libusermetrics Version: 1.3.0-1 Severity: serious Tags: ftbfs trixie sid Forwarded: https://gitlab.com/ubports/development/core/libusermetrics/-/merge_requests/11 https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libusermetrics.html ... In file included from /usr/src/googletest/googletest/include/gtest/gtest-message.h:57, from /usr/src/googletest/googletest/include/gtest/gtest-assertion-result.h:46, from /usr/src/googletest/googletest/include/gtest/gtest.h:64, from /build/1st/libusermetrics-1.3.0/tests/testutils/main.cpp:21: /usr/src/googletest/googletest/include/gtest/internal/gtest-port.h:270:2: error: #error C++ versions less than C++14 are not supported. 270 | #error C++ versions less than C++14 are not supported. | ^ ... --- End Message --- --- Begin Message --- Source: libusermetrics Source-Version: 1.3.0-2 Done: Marius Gripsgard We believe that the bug you reported is fixed in the latest version of libusermetrics, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1041...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Marius Gripsgard (supplier of updated libusermetrics package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 27 Jul 2023 01:01:00 +0200 Source: libusermetrics Architecture: source Version: 1.3.0-2 Distribution: unstable Urgency: medium Maintainer: Debian UBports Team Changed-By: Marius Gripsgard Closes: 1041135 Changes: libusermetrics (1.3.0-2) unstable; urgency=medium . * debian/patches: Add patch to fix FTBFS with googletest 1.13.0 (closes: #1041135) * debian/control: Add myself as uploader Checksums-Sha1: 1d693e2a052a2c38fbaa386695973b6d89f217dc 2327 libusermetrics_1.3.0-2.dsc 424327af2b0c87cba7ef6f7ccaff7c5b2596fed5 131382 libusermetrics_1.3.0.orig.tar.gz 17212dacd9e966ecdbf1477903493f44ad11a3f0 5844 libusermetrics_1.3.0-2.debian.tar.xz e960cfc8565f5a40d7216c972731a540d8513f40 13954 libusermetrics_1.3.0-2_source.buildinfo Checksums-Sha256: 878273b1628bd757f64661e331b0dbb3029ffa6a371a71e3e6d34a6cdd3b2da5 2327 libusermetrics_1.3.0-2.dsc 9028c382c86d54e38768dcb7a0286b8d2f2a478449ff647aa264699ffa8ad0d5 131382 libusermetrics_1.3.0.orig.tar.gz 45678a85ecfb6f1f0896fd25535e040b693959545a4d3b5ac2f7944972c03862 5844 libusermetrics_1.3.0-2.debian.tar.xz cf33265c45dc82e2b8e795963396e46ecddcb495895dbe820cab236136a01e56 13954 libusermetrics_1.3.0-2_source.buildinfo Files: f861ba991646a4f11905d0427650b260 2327 libs optional libusermetrics_1.3.0-2.dsc 63f22964004291f880f8eff477f8ca14 131382 libs optional libusermetrics_1.3.0.orig.tar.gz 5afae2c7f11714ef79b0a0a05df2eb84 5844 libs optional libusermetrics_1.3.0-2.debian.tar.xz 1fa00d7166846034a04bacf2c5586870 13954 libs optional libusermetrics_1.3.0-2_source.buildinfo -BEGIN PGP SIGNATURE- iIsEARYIADMWIQT0KegCiCm6mh1JH2jwqyDIdgBMKgUCZMGl8hUcbWFyaW9ncmlw QGRlYmlhbi5vcmcACgkQ8KsgyHYATCqvowEAy/dVFZYDJ/mWr1UXs5sIWmgVTe8D jHfM+5oyPCLjQv8A/0jAcKPBSjOu1a4zBUM7K8M4g54XZER1NqLIMAfhtvgL =Puzt -END PGP SIGNATURE End Message ---
Bug#1042108: marked as done (librust-shellexpand-dev is not installable)
Your message dated Wed, 26 Jul 2023 23:20:28 + with message-id and subject line Bug#1042108: fixed in rust-shellexpand 3.1.0-3 has caused the Debian Bug report #1042108, regarding librust-shellexpand-dev is not installable to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1042108: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042108 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: librust-shellexpand-dev Version: 3.1.0-2 Severity: serious The following packages have unmet dependencies: librust-shellexpand-dev : Depends: librust-dirs-4+default-dev --- End Message --- --- Begin Message --- Source: rust-shellexpand Source-Version: 3.1.0-3 Done: Matthias Geiger We believe that the bug you reported is fixed in the latest version of rust-shellexpand, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1042...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthias Geiger (supplier of updated rust-shellexpand package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 26 Jul 2023 22:56:41 + Source: rust-shellexpand Architecture: source Version: 3.1.0-3 Distribution: unstable Urgency: medium Maintainer: Debian Rust Maintainers Changed-By: Matthias Geiger Closes: 1042108 Changes: rust-shellexpand (3.1.0-3) unstable; urgency=medium . * Team upload. * Package shellexpand 3.1.0 from crates.io using debcargo 2.6.0 * Updated patch for newer dirs (Closes: #1042108). Checksums-Sha1: 4e72304cde7e81d37ee58bc2e287f01831bf461b 2213 rust-shellexpand_3.1.0-3.dsc 092664f0e522e9cf4da48fdedc21e0187a1e0df2 3388 rust-shellexpand_3.1.0-3.debian.tar.xz cc35728f9c82b6823f99b6c15d12ce866cebe46a 7666 rust-shellexpand_3.1.0-3_source.buildinfo Checksums-Sha256: f4fe7573fc21c31c4d0f0f1f2ef20256e31ee56f47435ee8bcf95f4335ae3954 2213 rust-shellexpand_3.1.0-3.dsc f91356984252992bfc2827e3b4e0447a5c1e7fbcdd89f1ecb58c1777efacb14d 3388 rust-shellexpand_3.1.0-3.debian.tar.xz 55ba11a296bee937cc146beeb8c9a04600a29ff2003e25f099be2aa4f7ef3a30 7666 rust-shellexpand_3.1.0-3_source.buildinfo Files: 44af9828c048c16b0efcfd363a1a00d8 2213 rust optional rust-shellexpand_3.1.0-3.dsc 2f2f80cb3c0ca430e9e536a51b40239a 3388 rust optional rust-shellexpand_3.1.0-3.debian.tar.xz 8e241580431661ca2fcf78689b654d68 7666 rust optional rust-shellexpand_3.1.0-3_source.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCAAyFiEEU0DQATYMplbjSX63DEjqKnqP/XsFAmTBpPIUHHBsdWd3YXNo QGRlYmlhbi5vcmcACgkQDEjqKnqP/Xv3UQ/+LfIxrtrauLbwC2eEXwKbKh9Nwg0w 59oWlEyusJRogWpEY5z6RdeCrq2xha93+zAU4jqULwYWGYSuQHtansaewjyWvkSm a/4FsluK/aLN+z3Ny5lNuOIAQSy5+xtL5sBURsqYWcty9O1qjLn2Lz3+BjkHW8zs h+hiA31xKCogJjnKX+IndmX2jRNzEf1yEyUb4MLQAGnIWnFB3cBhdPET/wPtAguJ 8d46uS7SXNgyW6rJb5W1XQqh27CWXU75FIxLMpyqPxqdVsjNff6KjE9jrerLZdNj UrdbTjREM2rJLzRaLWEhGhcsostqJdEMaGfHYnwPrM4eDq2PFlKNyhsDboQQth94 1qVGTxWIT2oiD8o4okb4D6YmIQya7v1RxSj4pLSF8OPwmy84YxTTYBw8pDxQ0Q6a Ut4MieC/423oz5kkTFIl1MtEem3ItHb+buwHlI0WH5O4bOAldNCuxUNYlVqljHdx vzA++bZO9HdlhHH3Xcos6CD93V8SWlwQpqo4wqaoI4eC+mvqXl4yjpSARtyu74/q kgsoeXZQDXA/N+hI4dxDUzmTQItNYTlODNwhqtErMzHTDRUsKZlUj23iymr2Z9LL Iiglqn720eKYuwWjpaeiTW6Wu0y1ZR+42L2J8mFwMtlsT6n9YuyVYxjOW6tr3aSx dXAobJyUxb2sLvQ= =tsYG -END PGP SIGNATURE End Message ---
Processed: closing 1041083
Processing commands for cont...@bugs.debian.org: > close 1041083 0.3.2-1 Bug #1041083 [src:libqtdbustest] libqtdbustest FTBFS with googletest 1.13.0 The source 'libqtdbustest' and version '0.3.2-1' do not appear to match any binary packages Marked as fixed in versions libqtdbustest/0.3.2-1. Bug #1041083 [src:libqtdbustest] libqtdbustest FTBFS with googletest 1.13.0 Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1041083: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041083 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1037763: marked as done (lomiri-app-launch: ftbfs with GCC-13)
Your message dated Wed, 26 Jul 2023 23:03:51 + with message-id and subject line Bug#1037763: fixed in lomiri-app-launch 0.1.7-1 has caused the Debian Bug report #1037763, regarding lomiri-app-launch: ftbfs with GCC-13 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1037763: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037763 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:lomiri-app-launch Version: 0.1.6-1 Severity: normal Tags: sid trixie User: debian-...@lists.debian.org Usertags: ftbfs-gcc-13 [This bug is targeted to the upcoming trixie release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-13/g++-13, but succeeds to build with gcc-12/g++-12. The severity of this report will be raised before the trixie release. The full build log can be found at: http://qa-logs.debian.net/2023/05/22/logs/lomiri-app-launch_0.1.6-1_unstable_gccexp.log The last lines of the build log are at the end of this report. To build with GCC 13, either set CC=gcc-13 CXX=g++-13 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-13/porting_to.html [...] cd /<>/obj-x86_64-linux-gnu/tests/googletest && /usr/bin/cmake -P CMakeFiles/gtest.dir/cmake_clean_target.cmake cd /<>/obj-x86_64-linux-gnu/tests/googletest && /usr/bin/cmake -E cmake_link_script CMakeFiles/gtest.dir/link.txt --verbose=1 /usr/bin/ar qc /<>/obj-x86_64-linux-gnu/tests/gmock/lib/libgtest.a "CMakeFiles/gtest.dir/src/gtest-all.cc.o" /usr/bin/ranlib /<>/obj-x86_64-linux-gnu/tests/gmock/lib/libgtest.a make[6]: Leaving directory '/<>/obj-x86_64-linux-gnu/tests/gmock' [ 25%] Built target gtest make -f CMakeFiles/gmock.dir/build.make CMakeFiles/gmock.dir/depend make -f /<>/obj-x86_64-linux-gnu/tests/googletest/CMakeFiles/gtest_main.dir/build.make /<>/obj-x86_64-linux-gnu/tests/googletest/CMakeFiles/gtest_main.dir/depend make[6]: Entering directory '/<>/obj-x86_64-linux-gnu/tests/gmock' cd /<>/obj-x86_64-linux-gnu/tests/gmock && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /usr/src/googletest/googlemock /usr/src/googletest/googlemock /<>/obj-x86_64-linux-gnu/tests/gmock /<>/obj-x86_64-linux-gnu/tests/gmock /<>/obj-x86_64-linux-gnu/tests/gmock/CMakeFiles/gmock.dir/DependInfo.cmake --color= make[6]: Entering directory '/<>/obj-x86_64-linux-gnu/tests/gmock' cd /<>/obj-x86_64-linux-gnu/tests/gmock && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /usr/src/googletest/googlemock /usr/src/googletest/googletest /<>/obj-x86_64-linux-gnu/tests/gmock /<>/obj-x86_64-linux-gnu/tests/googletest /<>/obj-x86_64-linux-gnu/tests/googletest/CMakeFiles/gtest_main.dir/DependInfo.cmake --color= make[6]: Leaving directory '/<>/obj-x86_64-linux-gnu/tests/gmock' make -f CMakeFiles/gmock.dir/build.make CMakeFiles/gmock.dir/build make[6]: Entering directory '/<>/obj-x86_64-linux-gnu/tests/gmock' make[6]: Leaving directory '/<>/obj-x86_64-linux-gnu/tests/gmock' make -f /<>/obj-x86_64-linux-gnu/tests/googletest/CMakeFiles/gtest_main.dir/build.make /<>/obj-x86_64-linux-gnu/tests/googletest/CMakeFiles/gtest_main.dir/build make[6]: Entering directory '/<>/obj-x86_64-linux-gnu/tests/gmock' [ 37%] Building CXX object CMakeFiles/gmock.dir/src/gmock-all.cc.o /usr/bin/c++ -I/usr/src/googletest/googlemock/include -I/usr/src/googletest/googlemock -isystem /usr/src/googletest/googletest/include -isystem /usr/src/googletest/googletest -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++17 -std=c++17 -g -Wno-old-style-cast -Wno-missing-field-initializers -Wno-ctor-dtor-privacy -Wno-switch-default -Wall -Wshadow -Wno-error=dangling-else -DGTEST_HAS_PTHREAD=1 -fexceptions -Wextra -Wno-unused-parameter -Wno-missing-field-initializers -DGTEST_HAS_PTHREAD=1 -MD -MT CMakeFiles/gmock.dir/src/gmock-all.cc.o -MF CMakeFiles/gmock.dir/src/gmock-all.cc.o.d -o CMakeFiles/gmock.dir/src/gmock-all.cc.o -c /usr/src/googletest/googlemock/src/gmock-all.cc [ 50%]
Processed: Bug#1042173 marked as pending in openlp
Processing control commands: > tag -1 pending Bug #1042173 [src:openlp] openlp: FTBFS: AttributeError: module 'PIL.ImageQt' has no attribute 'ImageQt' Added tag(s) pending. -- 1042173: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042173 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1042173: marked as pending in openlp
Control: tag -1 pending Hello, Bug #1042173 in openlp reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/openlp/-/commit/5de4ce839d9b218539b68efd61c72d30cca6d734 Patch: Remove dependency on PIL (Closes: #1042173) (this message was generated automatically) -- Greetings https://bugs.debian.org/1042173
Bug#1042157: [3dprinter-general] Bug#1042157: uranium: FTBFS: dh_install: error: missing files, aborting
-- Installing: /<>/debian/tmp/usr/local/lib/python3.11/dist-packages/UM -- Installing: /<>/debian/tmp/usr/local/lib/python3.11/dist-packages/UM/ColorImage.py dh_install: warning: Cannot find (any matches for) "usr/lib/python3/dist-packages/UM" (tried in ., debian/tmp) dh_install: warning: python3-uranium missing files: usr/lib/python3/dist-packages/UM dh_install: error: missing files, aborting make: *** [debian/rules:7: binary] Error 25 Those are very strange results. No files should end up in /usr/local! And I haven't been able to reproduce this locally yet. Investigation ongoing...
Bug#1042299: marked as done (libfirefox-marionette-perl: FTBFS: tests fail)
Your message dated Wed, 26 Jul 2023 22:25:05 +
with message-id
and subject line Bug#1042299: fixed in libfirefox-marionette-perl 1.41-1
has caused the Debian Bug report #1042299,
regarding libfirefox-marionette-perl: FTBFS: tests fail
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1042299: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042299
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libfirefox-marionette-perl
Version: 1.35-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230726 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[2]: Entering directory '/<>'
> PERL_DL_NONLAZY=1 "/usr/bin/perl" "-MExtUtils::Command::MM" "-MTest::Harness"
> "-e" "undef *Test::Harness::Switches; test_harness(1, 'blib/lib',
> 'blib/arch')" t/*.t
> # Testing Firefox::Marionette 1.35
> t/00.load.t
> 1..1
> ok 1 - use Firefox::Marionette;
> ok
> # Version is Mozilla Firefox 115.0.2esr
> # XAUTHORITY is /tmp/xvfb-run.UybmK6/Xauthority
> # DISPLAY is :99
> # D-Bus is working
> # Debian Version is trixie/sid
> # Xvfb deb version is 2:21.1.7-3
> # grep -r Mem /proc/meminfo
> # MemTotal: 32522708 kB
> # MemFree:27782096 kB
> # MemAvailable: 31741224 kB
> # ulimit -a | grep -i mem
> # memory(kbytes) unlimited
> # locked memory(kbytes) 4065338
> # vmemory(kbytes) unlimited
> # This firefox installation has 0 existing profiles
> '/usr/bin/perl --version' did not produce output that could be parsed.
> Assuming modern Marionette is available at t/01-marionette.t line 605.
> '/usr/bin/perl --version' did not produce output that could be parsed.
> Assuming modern Marionette is available at t/01-marionette.t line 605.
> '/usr/bin/perl --version' did not produce output that could be parsed.
> Assuming modern Marionette is available at t/01-marionette.t line 605.
> '/usr/bin/perl --version' did not produce output that could be parsed.
> Assuming modern Marionette is available at t/01-marionette.t line 605.
> # Initial tests
> # Testing has been running for 2 seconds at t/01-marionette.t line 714
> ** firefox --version
> ** firefox -marionette -safe-mode -headless -profile
> /tmp/firefox_marionette_local_J2HxYCzFDvj/profile --no-remote --new-instance
> *** You are running in headless mode.
> << 50:{"applicationType":"gecko","marionetteProtocol":3}
> >> 73:[0,1,"WebDriver:NewSession",{"capabilities":{"requiredCapabilities":{}}}]
> <<
> 721:[1,1,null,{"sessionId":"da1bdff4-017f-47b8-b199-bcbe91185eb9","capabilities":{"browserName":"firefox","browserVersion":"115.0.2","platformName":"linux","acceptInsecureCerts":false,"pageLoadStrategy":"normal","setWindowRect":true,"timeouts":{"implicit":0,"pageLoad":30,"script":3},"strictFileInteractability":false,"unhandledPromptBehavior":"dismiss
> and
> notify","moz:accessibilityChecks":false,"moz:buildID":"20230710180319","moz:headless":true,"moz:platformVersion":"5.10.0-23-cloud-amd64","moz:processID":84703,"moz:profile":"/tmp/firefox_marionette_local_J2HxYCzFDvj/profile","moz:shutdownTimeout":6,"moz:useNonSpecCompliantPointerOrigin":false,"moz:webdriverClick":true,"moz:windowless":false,"proxy":{}}}]
> >> 33:[0,2,"WebDriver:GetCapabilities"]
> <<
> 680:[1,2,null,{"value":{"capabilities":{"browserName":"firefox","browserVersion":"115.0.2","platformName":"linux","acceptInsecureCerts":false,"pageLoadStrategy":"normal","setWindowRect":true,"timeouts":{"implicit":0,"pageLoad":30,"script":3},"strictFileInteractability":false,"unhandledPromptBehavior":"dismiss
> and
> notify","moz:accessibilityChecks":false,"moz:buildID":&
Bug#1000083: marked as done (crystal: depends on obsolete pcre3 library)
Your message dated Wed, 26 Jul 2023 22:23:01 + with message-id and subject line Bug#125: fixed in crystal 1.9.2+dfsg-1 has caused the Debian Bug report #125, regarding crystal: depends on obsolete pcre3 library to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 125: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=125 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: crystal Severity: important User: matthew-pcre...@debian.org Usertags: obsolete-pcre3 Dear maintainer, Your package still depends on the old, obsolete PCRE3[0] libraries (i.e. libpcre3-dev). This has been end of life for a while now, and upstream do not intend to fix any further bugs in it. Accordingly, I would like to remove the pcre3 libraries from Debian, preferably in time for the release of Bookworm. The newer PCRE2 library was first released in 2015, and has been in Debian since stretch. Upstream's documentation for PCRE2 is available here: https://pcre.org/current/doc/html/ Many large projects that use PCRE have made the switch now (e.g. git, php); it does involve some work, but we are now at the stage where PCRE3 should not be used, particularly if it might ever be exposed to untrusted input. This mass bug filing was discussed on debian-devel@ in https://lists.debian.org/debian-devel/2021/11/msg00176.html Regards, Matthew [0] Historical reasons mean that old PCRE is packaged as pcre3 in Debian --- End Message --- --- Begin Message --- Source: crystal Source-Version: 1.9.2+dfsg-1 Done: David Suárez We believe that the bug you reported is fixed in the latest version of crystal, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1000...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. David Suárez (supplier of updated crystal package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 26 Jul 2023 21:12:38 +0200 Source: crystal Architecture: source Version: 1.9.2+dfsg-1 Distribution: unstable Urgency: medium Maintainer: David Suárez Changed-By: David Suárez Closes: 125 1026873 Changes: crystal (1.9.2+dfsg-1) unstable; urgency=medium . * New upstream version (Closes: #1026873). * d/patches: - Remove patch 'fix-sbuild-pkgbuilddir-filtering-in-unix-spec'. - Refresh patch 'remove-check-in-random-failing-test'. * Switch to pcre2 (Closes: #125). * Install fish completion file. * debian/control: - Bump debhelper compat version. - Update standards version; No changes needed. Checksums-Sha1: 43c2f795624443e965f89d3fd87dd11a41dee66e 2160 crystal_1.9.2+dfsg-1.dsc 2a9ae1f9fd97011b87919c5d75db4d33dda3160d 2097284 crystal_1.9.2+dfsg.orig.tar.xz 7e31e6f1139c23f827048d0eee2318499d523c14 6204 crystal_1.9.2+dfsg-1.debian.tar.xz 7c6894a11b3e023e5158f77f067c7ba70448df88 8225 crystal_1.9.2+dfsg-1_source.buildinfo Checksums-Sha256: 5afbbb56ac55c4e10654ab926b6c07e89bd314d25900f9c4f6c08080ae678829 2160 crystal_1.9.2+dfsg-1.dsc dea2365f7466ac370fae64349d3776cc7cbe4ad5443d8a22346a5df3421aa7a5 2097284 crystal_1.9.2+dfsg.orig.tar.xz 4f2f7beee1fcd9d9339bb198e4cc934c0f8ab0f64af1b33194cb8f8fb0d75640 6204 crystal_1.9.2+dfsg-1.debian.tar.xz 7babb7c7f2994e943cee91385b7e753639dea23420300803d1d4da6ef5005cbc 8225 crystal_1.9.2+dfsg-1_source.buildinfo Files: 389e4a48864a77b2465194d07990256b 2160 devel optional crystal_1.9.2+dfsg-1.dsc 70b0080e0599dd0221a29170f52af0d5 2097284 devel optional crystal_1.9.2+dfsg.orig.tar.xz d3072c572b770992f2430474c3aabc27 6204 devel optional crystal_1.9.2+dfsg-1.debian.tar.xz 9521b638f5ef25e1f20047e5065bd691 8225 devel optional crystal_1.9.2+dfsg-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEExFAZYDOyRoLv5EydfLboPYYFQjoFAmTBkxwACgkQfLboPYYF QjoA3g/+IxKxRFyCXkWeqHHJq6gL0sUvgnd6HudV6WjPeELFrdi4f9wcxC+1c7Ut lQq79hqIMUtHcNIjtOGswyl8ekSM2BpHmNTSpmDBvcYTBs9802yiO6QMH9by9aQG hjii2C30JPiR1ut5ruknVufLC2TYARE0VDtnRfcHKFhJxItfhNtaTk7yddGAeyA5 Q2iJVnITO06V50yNBvX1y+Ol/ec1BKkLt6MyBqC6ikY0rBtQe+8KjEsQQf1GXFwe FM8X279AU2aBmSek1s9hVe0lFwlLJT6/398h5oei5b1aMvnP4rHWa/fVrmL1PRnK
Bug#1000025: marked as done (crystal: depends on obsolete pcre3 library)
Your message dated Wed, 26 Jul 2023 22:23:01 + with message-id and subject line Bug#125: fixed in crystal 1.9.2+dfsg-1 has caused the Debian Bug report #125, regarding crystal: depends on obsolete pcre3 library to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 125: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=125 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: crystal Severity: important User: matthew-pcre...@debian.org Usertags: obsolete-pcre3 Dear maintainer, Your package still depends on the old, obsolete PCRE3[0] libraries (i.e. libpcre3-dev). This has been end of life for a while now, and upstream do not intend to fix any further bugs in it. Accordingly, I would like to remove the pcre3 libraries from Debian, preferably in time for the release of Bookworm. The newer PCRE2 library was first released in 2015, and has been in Debian since stretch. Upstream's documentation for PCRE2 is available here: https://pcre.org/current/doc/html/ Many large projects that use PCRE have made the switch now (e.g. git, php); it does involve some work, but we are now at the stage where PCRE3 should not be used, particularly if it might ever be exposed to untrusted input. This mass bug filing was discussed on debian-devel@ in https://lists.debian.org/debian-devel/2021/11/msg00176.html Regards, Matthew [0] Historical reasons mean that old PCRE is packaged as pcre3 in Debian --- End Message --- --- Begin Message --- Source: crystal Source-Version: 1.9.2+dfsg-1 Done: David Suárez We believe that the bug you reported is fixed in the latest version of crystal, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1000...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. David Suárez (supplier of updated crystal package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 26 Jul 2023 21:12:38 +0200 Source: crystal Architecture: source Version: 1.9.2+dfsg-1 Distribution: unstable Urgency: medium Maintainer: David Suárez Changed-By: David Suárez Closes: 125 1026873 Changes: crystal (1.9.2+dfsg-1) unstable; urgency=medium . * New upstream version (Closes: #1026873). * d/patches: - Remove patch 'fix-sbuild-pkgbuilddir-filtering-in-unix-spec'. - Refresh patch 'remove-check-in-random-failing-test'. * Switch to pcre2 (Closes: #125). * Install fish completion file. * debian/control: - Bump debhelper compat version. - Update standards version; No changes needed. Checksums-Sha1: 43c2f795624443e965f89d3fd87dd11a41dee66e 2160 crystal_1.9.2+dfsg-1.dsc 2a9ae1f9fd97011b87919c5d75db4d33dda3160d 2097284 crystal_1.9.2+dfsg.orig.tar.xz 7e31e6f1139c23f827048d0eee2318499d523c14 6204 crystal_1.9.2+dfsg-1.debian.tar.xz 7c6894a11b3e023e5158f77f067c7ba70448df88 8225 crystal_1.9.2+dfsg-1_source.buildinfo Checksums-Sha256: 5afbbb56ac55c4e10654ab926b6c07e89bd314d25900f9c4f6c08080ae678829 2160 crystal_1.9.2+dfsg-1.dsc dea2365f7466ac370fae64349d3776cc7cbe4ad5443d8a22346a5df3421aa7a5 2097284 crystal_1.9.2+dfsg.orig.tar.xz 4f2f7beee1fcd9d9339bb198e4cc934c0f8ab0f64af1b33194cb8f8fb0d75640 6204 crystal_1.9.2+dfsg-1.debian.tar.xz 7babb7c7f2994e943cee91385b7e753639dea23420300803d1d4da6ef5005cbc 8225 crystal_1.9.2+dfsg-1_source.buildinfo Files: 389e4a48864a77b2465194d07990256b 2160 devel optional crystal_1.9.2+dfsg-1.dsc 70b0080e0599dd0221a29170f52af0d5 2097284 devel optional crystal_1.9.2+dfsg.orig.tar.xz d3072c572b770992f2430474c3aabc27 6204 devel optional crystal_1.9.2+dfsg-1.debian.tar.xz 9521b638f5ef25e1f20047e5065bd691 8225 devel optional crystal_1.9.2+dfsg-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEExFAZYDOyRoLv5EydfLboPYYFQjoFAmTBkxwACgkQfLboPYYF QjoA3g/+IxKxRFyCXkWeqHHJq6gL0sUvgnd6HudV6WjPeELFrdi4f9wcxC+1c7Ut lQq79hqIMUtHcNIjtOGswyl8ekSM2BpHmNTSpmDBvcYTBs9802yiO6QMH9by9aQG hjii2C30JPiR1ut5ruknVufLC2TYARE0VDtnRfcHKFhJxItfhNtaTk7yddGAeyA5 Q2iJVnITO06V50yNBvX1y+Ol/ec1BKkLt6MyBqC6ikY0rBtQe+8KjEsQQf1GXFwe FM8X279AU2aBmSek1s9hVe0lFwlLJT6/398h5oei5b1aMvnP4rHWa/fVrmL1PRnK
Bug#1040521: tpm2-tss: FTBFS (test failures)
For the autpkgtest fialures see also #1042041.
Bug#1042041: tpm2-pkcs11: FTBFS: undefined symbol: Tss2_MU_TPMS_ALGORITHM_DESCRIPTION_Marshal
Control: reopen -1 Control: reassign -1 python3-tpm2-pytss X-Debbugs-Cc: paul...@debian.org Forget about my previous email. On Tue, 25 Jul 2023 23:06:27 +0200 Lucas Nussbaum wrote: Source: tpm2-pkcs11 Version: 1.9.0-0.2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > gcc version 13.1.0 (Debian 13.1.0-9) > ... rest of stderr output deleted ... > configure:14853: checking for module tpm2_pytss in python > configure:14857: error: not found echo "import tpm2_pytss" | python3 Traceback (most recent call last): File "", line 1, in File "/usr/lib/python3/dist-packages/tpm2_pytss/__init__.py", line 2, in from .ESAPI import ESAPI File "/usr/lib/python3/dist-packages/tpm2_pytss/ESAPI.py", line 2, in from .types import * File "/usr/lib/python3/dist-packages/tpm2_pytss/types.py", line 12, in from ._libtpm2_pytss import ffi, lib ImportError: /usr/lib/python3/dist-packages/tpm2_pytss/_libtpm2_pytss.abi3.so: undefined symbol: Tss2_MU_TPMS_ALGORITHM_DESCRIPTION_Marshal The python3-tpm2-pytss package needs a binNMU because tpm2-tss was uploaded without migration.
Processed: Re: tpm2-pkcs11: FTBFS: undefined symbol: Tss2_MU_TPMS_ALGORITHM_DESCRIPTION_Marshal
Processing control commands:
> reopen -1
Bug #1042041 {Done: Bastian Germann } [src:tpm2-pkcs11]
tpm2-pkcs11: FTBFS: gcc: error: unrecognized command-line option '-V'
Bug reopened
Ignoring request to alter fixed versions of bug #1042041 to the same values
previously set
> reassign -1 python3-tpm2-pytss
Bug #1042041 [src:tpm2-pkcs11] tpm2-pkcs11: FTBFS: gcc: error: unrecognized
command-line option '-V'
Bug reassigned from package 'src:tpm2-pkcs11' to 'python3-tpm2-pytss'.
No longer marked as found in versions tpm2-pkcs11/1.9.0-0.2.
Ignoring request to alter fixed versions of bug #1042041 to the same values
previously set
--
1042041: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042041
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1042219: marked as done (minilla: FTBFS: find: ‘/<>/debian/minilla/usr/share/man/man1’: No such file or directory)
Your message dated Wed, 26 Jul 2023 21:54:44 + with message-id and subject line Bug#1042219: fixed in minilla 3.1.21-2 has caused the Debian Bug report #1042219, regarding minilla: FTBFS: find: ‘/<>/debian/minilla/usr/share/man/man1’: No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1042219: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042219 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: minilla Version: 3.1.21-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230726 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_auto_install > /usr/bin/perl Build install --destdir /<>/debian/minilla > --create_packlist 0 > Installing /<>/debian/minilla/usr/share/perl5/Minilla.pm > Installing > /<>/debian/minilla/usr/share/perl5/Module/BumpVersion.pm > Installing > /<>/debian/minilla/usr/share/perl5/Minilla/Gitignore.pm > Installing > /<>/debian/minilla/usr/share/perl5/Minilla/Unsupported.pm > Installing /<>/debian/minilla/usr/share/perl5/Minilla/Project.pm > Installing /<>/debian/minilla/usr/share/perl5/Minilla/WorkDir.pm > Installing /<>/debian/minilla/usr/share/perl5/Minilla/Git.pm > Installing /<>/debian/minilla/usr/share/perl5/Minilla/Util.pm > Installing > /<>/debian/minilla/usr/share/perl5/Minilla/FileGatherer.pm > Installing /<>/debian/minilla/usr/share/perl5/Minilla/Migrate.pm > Installing /<>/debian/minilla/usr/share/perl5/Minilla/Logger.pm > Installing > /<>/debian/minilla/usr/share/perl5/Minilla/ReleaseTest.pm > Installing > /<>/debian/minilla/usr/share/perl5/Minilla/Tutorial.pod > Installing /<>/debian/minilla/usr/share/perl5/Minilla/Errors.pm > Installing /<>/debian/minilla/usr/share/perl5/Minilla/CLI.pm > Installing /<>/debian/minilla/usr/share/perl5/Minilla/Metadata.pm > Installing > /<>/debian/minilla/usr/share/perl5/Minilla/Profile/Default.pm > Installing > /<>/debian/minilla/usr/share/perl5/Minilla/Profile/Base.pm > Installing > /<>/debian/minilla/usr/share/perl5/Minilla/Profile/ModuleBuild.pm > Installing > /<>/debian/minilla/usr/share/perl5/Minilla/Profile/ExtUtilsMakeMaker.pm > Installing > /<>/debian/minilla/usr/share/perl5/Minilla/Profile/XS.pm > Installing > /<>/debian/minilla/usr/share/perl5/Minilla/Profile/ModuleBuildTiny.pm > Installing /<>/debian/minilla/usr/share/perl5/Minilla/CLI/Dist.pm > Installing /<>/debian/minilla/usr/share/perl5/Minilla/CLI/Test.pm > Installing /<>/debian/minilla/usr/share/perl5/Minilla/CLI/Help.pm > Installing > /<>/debian/minilla/usr/share/perl5/Minilla/CLI/Install.pm > Installing > /<>/debian/minilla/usr/share/perl5/Minilla/CLI/Build.pm > Installing > /<>/debian/minilla/usr/share/perl5/Minilla/CLI/Migrate.pm > Installing /<>/debian/minilla/usr/share/perl5/Minilla/CLI/Run.pm > Installing > /<>/debian/minilla/usr/share/perl5/Minilla/CLI/Release.pm > Installing /<>/debian/minilla/usr/share/perl5/Minilla/CLI/New.pm > Installing > /<>/debian/minilla/usr/share/perl5/Minilla/CLI/Clean.pm > Installing > /<>/debian/minilla/usr/share/perl5/Minilla/License/Unknown.pm > Installing > /<>/debian/minilla/usr/share/perl5/Minilla/License/Perl_5.pm > Installing > /<>/debian/minilla/usr/share/perl5/Minilla/ModuleMaker/ModuleBuild.pm > Installing > /<>/debian/minilla/usr/share/perl5/Minilla/ModuleMaker/ExtUtilsMakeMaker.pm > Installing > /<>/debian/minilla/usr/share/perl5/Minilla/ModuleMaker/ModuleBuildTiny.pm > Installing > /<>/debian/minilla/usr/share/perl5/Minilla/Release/CheckChanges.pm > Installing > /<>/debian/minilla/usr/share/perl5/Minilla/Release/MakeDist.pm > Installing > /<>/debian/minilla/usr/share/perl5/Minilla/Release/CheckOrigin.pm > Installing > /<>/debian/minilla/usr/share/perl5/Minilla/Release/CheckReleaseBranch.pm > Installing > /<>/debian/minilla/usr/share/perl5/Minilla/Release/Commit.pm > Installing > /<>/debian/minilla/usr/share/perl5/Minilla/Release/RewriteChanges.pm > Installing > /<>
Bug#1037664: marked as done (freecad: ftbfs with GCC-13)
Your message dated Wed, 26 Jul 2023 21:52:39 + with message-id and subject line Bug#1037664: fixed in freecad 0.20.2+dfsg1-9 has caused the Debian Bug report #1037664, regarding freecad: ftbfs with GCC-13 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1037664: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037664 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:freecad Version: 0.20.2+dfsg1-4 Severity: normal Tags: sid trixie User: debian-...@lists.debian.org Usertags: ftbfs-gcc-13 [This bug is targeted to the upcoming trixie release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-13/g++-13, but succeeds to build with gcc-12/g++-12. The severity of this report will be raised before the trixie release. The full build log can be found at: http://qa-logs.debian.net/2023/05/22/logs/freecad_0.20.2+dfsg1-4_unstable_gccexp.log The last lines of the build log are at the end of this report. To build with GCC 13, either set CC=gcc-13 CXX=g++-13 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-13/porting_to.html [...] from /usr/include/c++/13/memory:66, from /usr/include/boost/smart_ptr/detail/sp_counted_impl.hpp:35, from /usr/include/boost/smart_ptr/detail/shared_count.hpp:27, from /usr/include/boost/smart_ptr/shared_ptr.hpp:17, from /usr/include/boost/shared_ptr.hpp:17, from /<>/src/3rdParty/salomesmesh/inc/SMDS_ElemIterator.hxx:33, from /<>/src/3rdParty/salomesmesh/inc/SMDS_MeshElement.hxx:34: /usr/include/c++/13/bits/stl_iterator_base_types.h:127:34: note: declared here 127 | struct _GLIBCXX17_DEPRECATED iterator | ^~~~ [ 43%] Building CXX object src/3rdParty/salomesmesh/CMakeFiles/SMDS.dir/src/SMDS/chrono.cpp.o cd /<>/debian/build-py3/src/3rdParty/salomesmesh && /usr/bin/c++ -DCSFDB -DH5_BUILT_AS_DYNAMIC_LIB -DHAVE_CONFIG_H -DHAVE_FREEIMAGE -DHAVE_FREETYPE -DHAVE_LIMITS_H -DHAVE_OPENGL_EXT -DHAVE_RAPIDJSON -DHAVE_TBB -DHAVE_TK -DHAVE_XLIB -DLIN -DMPICH_SKIP_MPICXX -DMPI_NO_CPPBIND -DOCC_CONVERT_SIGNALS -DOMPI_SKIP_MPICXX -DSMDS_EXPORTS -D_MPICC_H -D_OCC64 -Dkiss_fft_scalar=double -I/<>/debian/build-py3 -I/<>/debian/build-py3/src -I/<>/src -I/<>/src/3rdParty/salomesmesh/src/SMDS -I/<>/src/3rdParty/salomesmesh/src/Driver -I/<>/src/3rdParty/salomesmesh/src/DriverUNV -I/<>/src/3rdParty/salomesmesh/src/DriverDAT -I/<>/src/3rdParty/salomesmesh/src/DriverSTL -I/<>/src/3rdParty/salomesmesh/src/StdMeshers -I/<>/src/3rdParty/salomesmesh/inc -I/<>/debian/build-py3/src/3rdParty/salomesmesh -I/usr/include/opencascade -isystem /usr/include/hdf5/serial -isystem /usr/include/vtk-9.1 -isystem /usr/include/jsoncpp -isystem /usr/lib/x86_64-linux-gnu/openmpi/include -isystem /usr/lib/x86_64-linux-gnu/openmpi/include/openmpi -isystem /usr/include/freetype2 -Wall -Wextra -Wno-write-strings -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -fpermissive -I/usr/include/python3.11 -flto -Wno-sign-compare -Wno-reorder -Wno-switch -Wno-unused-variable -Wno-unused-but-set-variable -Wno-comment -Wno-unused-parameter -Wno-empty-body -Wno-pedantic -Wno-unused-result -Wno-cast-function-type -Wno-maybe-uninitialized -Wno-missing-field-initializers -O2 -g -DNDEBUG -fPIC -I/usr/include/hdf5/openmpi -I/usr/lib/x86_64-linux-gnu/openmpi/include -I/usr/lib/x86_64-linux-gnu/openmpi/include/openmpi -std=gnu++17 -MD -MT src/3rdParty/salomesmesh/CMakeFiles/SMDS.dir/src/SMDS/chrono.cpp.o -MF CMakeFiles/SMDS.dir/src/SMDS/chrono.cpp.o.d -o CMakeFiles/SMDS.dir/src/SMDS/chro no.cpp.o -c /<>/src/3rdParty/salomesmesh/src/SMDS/chrono.cpp [ 43%] Building CXX object src/3rdParty/salomesmesh/CMakeFiles/SMDS.dir/src/SMDS/duplicate.cpp.o cd /<>/debian/build-py3/src/3rdParty/salomesmesh && /usr/bin/c++ -DCSFDB -DH5_BUILT_AS_DYNAMIC_LIB
Bug#1042269: marked as done (binutils-riscv64-unknown-elf: FTBFS: dh_auto_configure: error: invalid or non-existing path to the source directory: binutils-2.40.90.20230720)
Your message dated Wed, 26 Jul 2023 21:49:39 + with message-id and subject line Bug#1042269: fixed in binutils-riscv64-unknown-elf 5 has caused the Debian Bug report #1042269, regarding binutils-riscv64-unknown-elf: FTBFS: dh_auto_configure: error: invalid or non-existing path to the source directory: binutils-2.40.90.20230720 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1042269: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042269 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: binutils-riscv64-unknown-elf Version: 4 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230726 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules binary > dh binary -Dbinutils-2.40.90.20230720 -Bbuild >dh_update_autotools_config -O-Dbinutils-2.40.90.20230720 -O-Bbuild >dh_autoreconf -O-Dbinutils-2.40.90.20230720 -O-Bbuild >debian/rules override_dh_auto_configure > make[1]: Entering directory '/<>' > tar xf /usr/src/binutils/binutils-*.tar.* > mkdir -p debian/stamp > cp /usr/share/doc/binutils-source/copyright debian/copyright > touch debian/stamp/tar > dh_auto_configure -Dbinutils-2.40.90.20230720 -Bbuild -- > --target=riscv64-unknown-elf --prefix=/usr/lib --bindir=/usr/bin > --libdir=/usr/lib/riscv64-unknown-elf > --infodir=/usr/share/doc/binutils-riscv64-unknown-elf/info > --htmldir=/usr/share/doc/binutils-riscv64-unknown-elf/html > --pdfdir=/usr/share/doc/binutils-riscv64-unknown-elf/pdf > --mandir=/usr/share/man --disable-nls --disable-werror --enable-plugins > --enable-interwork --with-system-zlib > "--with-pkgversion=2.40.90.20230720-1+4" --enable-deterministic-archives > ASFLAGS="" CFLAGS="-g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security" > CPPFLAGS="-Wdate-time -D_FORTIFY_SOURCE=2" CXXFLAGS="-g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security" DFLAGS="-frelease" FCFLAGS="-g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong" FFLAGS="-g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong" GCJFLAGS="-g > -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong" > LDFLAGS="-Wl,-z,relro -Wl,-z,now" OBJCFLAGS="-g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security" OBJCXXFLAGS="-g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security" > dh_auto_configure: error: invalid or non-existing path to the source > directory: binutils-2.40.90.20230720 > make[1]: *** [debian/rules:55: override_dh_auto_configure] Error 25 The full build log is available from: http://qa-logs.debian.net/2023/07/26/binutils-riscv64-unknown-elf_4_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230726;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230726=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: binutils-riscv64-unknown-elf Source-Version: 5 Done: Keith Packard We believe that the bug you reported is fixed in the latest version of binutils-riscv64-unknown-elf, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1042...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Keith Packard (supplier of updated binutils-riscv64-unknown-elf package) (This message was generated automatically at their request; if you believe that there is
Processed: Re: #1041372 xtensor autopkg tests fail on i386 and s390x
Processing commands for cont...@bugs.debian.org: > forwarded 1041372 https://github.com/xtensor-stack/xtensor/issues/2718 Bug #1041372 [src:xtensor] xtensor autopkg tests fail on i386 and s390x Set Bug forwarded-to-address to 'https://github.com/xtensor-stack/xtensor/issues/2718'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1041372: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041372 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1041372: #1041372 xtensor autopkg tests fail on i386 and s390x
forwarded 1041372 https://github.com/xtensor-stack/xtensor/issues/2718 thanks Evidently triggered by excess precision changes in gcc-13, see https://gcc.gnu.org/gcc-13/porting_to.html
Bug#1042089: src:golang-defaults: fails to migrate to testing for too long: triggers autopkgtest failure on armhf
On Thu, Jul 27, 2023 at 2:51 AM David Kalnischkies wrote: > > On Wed, Jul 26, 2023 at 04:48:55PM +0200, Paul Gevers wrote: > > [2]. Hence, I am filing this bug. The version in unstable triggers an > > autopkgtest failure in vim-youcompleteme on armhf. > > This used to be the case for armel, too, until today, which had gccgo-13 > 13.1.0-9 migrate to testing – the day before it failed with 13.1.0-6. > armhf seems to have followed up just now with a passing grade: > https://ci.debian.net/packages/v/vim-youcompleteme/testing/armhf/ Yes, I'm waiting for gcc-13 to migrate. See my previous trigger with gcc-13 from unstable. https://ci.debian.net/user/zhsj/jobs?package=ycmd -- Shengjing Zhu
Bug#1042029: marked as done (graph-tool: FTBFS: collect2: fatal error: ld terminated with signal 9 [Killed])
Your message dated Wed, 26 Jul 2023 23:12:53 +0200 with message-id <31785653-789e-04d2-44bb-c9cebd676...@rezozer.net> and subject line graph-tool: FTBFS: fatal error: ld terminated with signal 9 [Killed] [cannot reproduce] has caused the Debian Bug report #1042029, regarding graph-tool: FTBFS: collect2: fatal error: ld terminated with signal 9 [Killed] to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1042029: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042029 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: graph-tool Version: 2.45+ds-10 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230724 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /bin/bash ./libtool --tag=CXX --mode=link g++ -std=gnu++17 -fopenmp -O3 > -fvisibility=default -fvisibility-inlines-hidden -Wno-deprecated -Wall > -Wextra -ftemplate-backtrace-limit=0 -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -module -avoid-version -export-dynamic -no-undefined > -Wl,-E -Wl,--as-needed -Wl,-z,relro -Wl,-z,now -o libgraph_tool_util.la > -rpath /usr/lib/python3.11/dist-packages/graph_tool/util > src/graph/util/graph_search.lo src/graph/util/graph_util_bind.lo > -L/usr/lib/x86_64-linux-gnu -lpython3.11 -L/usr/lib/x86_64-linux-gnu > -lboost_iostreams -lboost_python311 -lboost_regex -lboost_context > -lboost_coroutine -lexpat-lgmp -lgmp > libtool: link: g++ -fPIC -DPIC -shared -nostdlib > /usr/lib/gcc/x86_64-linux-gnu/13/../../../x86_64-linux-gnu/crti.o > /usr/lib/gcc/x86_64-linux-gnu/13/crtbeginS.o > src/graph/util/.libs/graph_search.o src/graph/util/.libs/graph_util_bind.o > -L/usr/lib/x86_64-linux-gnu -lpython3.11 -lboost_iostreams -lboost_python311 > -lboost_regex -lboost_context -lboost_coroutine -lexpat -lgmp > -L/usr/lib/gcc/x86_64-linux-gnu/13 > -L/usr/lib/gcc/x86_64-linux-gnu/13/../../../x86_64-linux-gnu > -L/usr/lib/gcc/x86_64-linux-gnu/13/../../../../lib -L/lib/x86_64-linux-gnu > -L/lib/../lib -L/usr/lib/../lib -L/usr/lib/gcc/x86_64-linux-gnu/13/../../.. > -lstdc++ -lm -lc -lgcc_s /usr/lib/gcc/x86_64-linux-gnu/13/crtendS.o > /usr/lib/gcc/x86_64-linux-gnu/13/../../../x86_64-linux-gnu/crtn.o -fopenmp > -O3 -g -O2 -fstack-protector-strong -Wl,-E -Wl,--as-needed -Wl,-z -Wl,relro > -Wl,-z -Wl,now -fopenmp -Wl,-soname -Wl,libgraph_tool_util.so -o > .libs/libgraph_tool_util.so > libtool: link: ( cd ".libs" && rm -f "libgraph_tool_util.la" && ln -s > "../libgraph_tool_util.la" "libgraph_tool_util.la" ) > collect2: fatal error: ld terminated with signal 9 [Killed] > compilation terminated. > make[2]: *** [Makefile:3339: libgraph_tool_inference.la] Error 1 The full build log is available from: http://qa-logs.debian.net/2023/07/24/graph-tool_2.45+ds-10_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230724;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230724=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Hi Lucas, I could not reproduce the issue in the current Sid environment (I tried twice) so I am closing the bug. It is highly probable that your build encountered a resource issue as this software is really heavy to build. Best wishes, Jerome -- Jerome BENOIT | calculus+at-rezozer^dot*net https://qa.debian.org/developer.php?login=calcu...@rezozer.net AE28 AE15 710D FF1D 87E5 A762 3F92 19A6 7F36 C68B OpenPGP_signature Description: OpenPGP digital signature --- End Message ---
Bug#1042130: libgit2-glib: FTBFS: dh_install: error: missing files, aborting
On Wed, 26 Jul 2023 at 22:03:40 +0200, Lucas Nussbaum wrote: > > Compiling > > '/<>/debian/tmp/usr/local/lib/python3.11/dist-packages/gi/overrides/Ggit.py'... ... > > dh_install: warning: Cannot find (any matches for) > > "usr/lib/python3*/*-packages/gi/overrides" (tried in ., debian/tmp) This looks like another instance of #1041537. smcv
Processed: Re: Bug#1041250 closed by Sebastian Ramacher (closing 1041250)
Processing commands for cont...@bugs.debian.org:
> notfound 1041250 5.15.14+dfsg-6
Bug #1041250 {Done: Sebastian Ramacher }
[src:qtwebengine-opensource-src] qtwebengine-opensource-src: FTBFS on mipsel
Ignoring request to alter found versions of bug #1041250 to the same values
previously set
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1041250: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041250
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: retitle 1042260 to nbsdgames: FTBFS: mmv '*' 'nb#1': realloc(): invalid pointer
Processing commands for cont...@bugs.debian.org: > retitle 1042260 nbsdgames: FTBFS: mmv '*' 'nb#1': realloc(): invalid pointer Bug #1042260 [src:nbsdgames] nbsdgames: FTBFS: make[1]: *** [debian/rules:33: override_dh_fixperms] Error 134 Changed Bug title to 'nbsdgames: FTBFS: mmv '*' 'nb#1': realloc(): invalid pointer' from 'nbsdgames: FTBFS: make[1]: *** [debian/rules:33: override_dh_fixperms] Error 134'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1042260: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042260 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: retitle 1042277 to gamescope: FTBFS: Dependency wlroots found: NO found 0.16.2 but need: '< 0.16.0'
Processing commands for cont...@bugs.debian.org: > retitle 1042277 gamescope: FTBFS: Dependency wlroots found: NO found 0.16.2 > but need: '< 0.16.0' Bug #1042277 [src:gamescope] gamescope: FTBFS: ../meson.build:50:14: ERROR: Subproject exists but has no meson.build file Changed Bug title to 'gamescope: FTBFS: Dependency wlroots found: NO found 0.16.2 but need: '< 0.16.0'' from 'gamescope: FTBFS: ../meson.build:50:14: ERROR: Subproject exists but has no meson.build file'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1042277: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042277 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1041253: pyside2: stop depending on qtwebengine5-dev on mipsel
[Sebastian Ramacher] > qtwebengine-opensource-src currently FTBFS on mipsel (see #1041250). To > complete the currently ongoing Qt transition, please disable support for > qtwebeninge-opensource-src on mipsel for the time being. This would > allow us to (temporarily) remove qtwebengine-opensource-src from mipsel. Note, qtwebengine-opensource-src was successfully built on mipsel after a rebuild was manually scheduled, so the problem seem to be solved without dropping mipsel too. -- Happy hacking Petter Reinholdtsen
Bug#1042112: gexiv2: FTBFS: dh_install: error: missing files, aborting
On Wed, 26 Jul 2023 at 22:03:11 +0200, Lucas Nussbaum wrote: > During a rebuild of all packages in sid, your package failed to build > on amd64. > > > dh_install: warning: Cannot find (any matches for) "usr/lib/python*" (tried > > in ., debian/tmp) This looks like #1041537 in Meson. smcv
Bug#1042216: gedit: FTBFS: dh_install: error: missing files, aborting
On Wed, 26 Jul 2023 at 22:03:02 +0200, Lucas Nussbaum wrote: > Relevant part (hopefully): > > Compiling > > '/<>/debian/tmp/usr/local/lib/python3.11/dist-packages/gi/overrides/Gedit.py'... ... > > dh_install: warning: Cannot find (any matches for) "usr/lib/python*" (tried > > in ., debian/tmp) Meson installing Python files to /usr/local/lib/python3.11/dist-packages looks like #1041537. smcv
Processed: Bug#1042219 marked as pending in minilla
Processing control commands: > tag -1 pending Bug #1042219 [src:minilla] minilla: FTBFS: find: ‘/<>/debian/minilla/usr/share/man/man1’: No such file or directory Added tag(s) pending. -- 1042219: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042219 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1042219: marked as pending in minilla
Control: tag -1 pending Hello, Bug #1042219 in minilla reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/perl-team/modules/packages/minilla/-/commit/d6c06d71c48de16d8e481d6e574eab185f541ac9 Drop manpage removal from debian/rules. Build-depend on libmodule-build-tiny-perl (>= 0.040) instead, which doesn't create the empty manpages in the first place. Closes: #1042219 (this message was generated automatically) -- Greetings https://bugs.debian.org/1042219
Bug#1040896: marked as done (raspi-firmware: Unable to uninstall raspi-firmware on amd64 systems)
Your message dated Wed, 26 Jul 2023 20:59:06 + with message-id and subject line Bug#1040896: fixed in raspi-firmware 1.20230405+ds-2 has caused the Debian Bug report #1040896, regarding raspi-firmware: Unable to uninstall raspi-firmware on amd64 systems to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1040896: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040896 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: raspi-firmware Version: 1.20220830+ds-1 Severity: important X-Debbugs-Cc: wiiliamchung...@gmail.com Dear Maintainer, Users are not able to uninstall raspi-firmware on amd64 systems, as the initramfs hook will exit with the following error: > raspi-firmware: missing /boot/firmware, did you forget to mount it? > run-parts: /etc/initramfs/post-update.d//z50-raspi-firmware exited with > return code 1 > run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 > dpkg: error processing package linux-image-6.1.0-10-amd64 (--configure): >installed linux-image-6.1.0-10-amd64 package post-installation script >subprocess returned error exit status 1 > dpkg: dependency problems prevent configuration of linux-image-amd64: >linux-image-amd64 depends on linux-image-6.1.0-10-amd64 (= 6.1.37-1); >however: > Package linux-image-6.1.0-10-amd64 is not configured yet. > > dpkg: error processing package linux-image-amd64 (--configure): >dependency problems - leaving unconfigured > Errors were encountered while processing: >linux-image-6.1.0-10-amd64 >linux-image-amd64 > E: Sub-process /usr/bin/dpkg returned an error code (1) To purge raspi-firmware, users will need to prevent /etc/kernel/postinst.d/z50-raspi-firmware from triggering. A current workaround is to add `exit 0` at the first line of /etc/kernel/postinst.d/z50-raspi-firmware I don't know where raspi-firmware was pulled in from, but the package was found in both systems where I installed debian bookworm (12) using the amd64 KDE live image. I assume that raspi-firmware is included by default. -- System Information: Debian Release: 12.0 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-9-amd64 (SMP w/16 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages raspi-firmware depends on: ii dosfstools 4.2-1 ii dpkg1.21.22 raspi-firmware recommends no packages. Versions of packages raspi-firmware suggests: ii bluez-firmware 1.2-9 ii firmware-brcm80211 20230210-5 ii firmware-misc-nonfree 20230210-5 --- End Message --- --- Begin Message --- Source: raspi-firmware Source-Version: 1.20230405+ds-2 Done: Gunnar Wolf We believe that the bug you reported is fixed in the latest version of raspi-firmware, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1040...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Gunnar Wolf (supplier of updated raspi-firmware package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 26 Jul 2023 12:39:57 -0600 Source: raspi-firmware Architecture: source Version: 1.20230405+ds-2 Distribution: unstable Urgency: medium Maintainer: pkg-raspi Changed-By: Gunnar Wolf Closes: 1040485 1040669 1040896 1042070 Changes: raspi-firmware (1.20230405+ds-2) unstable; urgency=medium . * Skip running postinst if installing on a system that's not arch:arm* (Closes: #1040896, #1040485, #1042070, #1040669) Checksums-Sha1: e788af22c6429841799ab8a227f8d1ebd3fd1b08 1536 raspi-firmware_1.20230405+ds-2.dsc 6ecdb8aee90dc8e4c47d11ff1c1ccd2ddc9135a0 379436 raspi-firmware_1.20230405+ds-2.debian.tar.xz db5063cffb3638bc92bb6b80c938e1c0a312ca1d 7781 raspi-firmware_1.20230405+ds-2_source.buildinfo Checksums-Sha256: 1c8531a14b4db41a6bd28ccf0938dd5d0d3a2aeedfa90a5a9379962b1db925c4 1536 raspi-firmware_1.20230405+ds-2.dsc
Bug#1040485: marked as done (raspi-firmware breaks kernel upgrade)
Your message dated Wed, 26 Jul 2023 20:59:06 + with message-id and subject line Bug#1040485: fixed in raspi-firmware 1.20230405+ds-2 has caused the Debian Bug report #1040485, regarding raspi-firmware breaks kernel upgrade to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1040485: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040485 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: raspi-firmware Severity: serious Justification: 6 X-Debbugs-Cc: okgomdjgbm...@gmail.com Dear Maintainer, I tried to upgrade the kernel today( bookworm amd64), and it failed because of raspi-firmware scripts. I had to rm manually files and purge raspi-firmware so that the kernel can complete the install. The messy removal is a second agravating problem. The package was included accidentally in the live CD for amd64. This problem affect every one that installed with the live CD. -- System Information: Debian Release: 12.0 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-9-amd64 (SMP w/2 CPU threads; PREEMPT) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages raspi-firmware depends on: ii dosfstools 4.2-1 ii dpkg1.21.22 raspi-firmware recommends no packages. Versions of packages raspi-firmware suggests: ii bluez-firmware 1.2-9 ii firmware-brcm80211 20230210-5 ii firmware-misc-nonfree 20230210-5 --- End Message --- --- Begin Message --- Source: raspi-firmware Source-Version: 1.20230405+ds-2 Done: Gunnar Wolf We believe that the bug you reported is fixed in the latest version of raspi-firmware, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1040...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Gunnar Wolf (supplier of updated raspi-firmware package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 26 Jul 2023 12:39:57 -0600 Source: raspi-firmware Architecture: source Version: 1.20230405+ds-2 Distribution: unstable Urgency: medium Maintainer: pkg-raspi Changed-By: Gunnar Wolf Closes: 1040485 1040669 1040896 1042070 Changes: raspi-firmware (1.20230405+ds-2) unstable; urgency=medium . * Skip running postinst if installing on a system that's not arch:arm* (Closes: #1040896, #1040485, #1042070, #1040669) Checksums-Sha1: e788af22c6429841799ab8a227f8d1ebd3fd1b08 1536 raspi-firmware_1.20230405+ds-2.dsc 6ecdb8aee90dc8e4c47d11ff1c1ccd2ddc9135a0 379436 raspi-firmware_1.20230405+ds-2.debian.tar.xz db5063cffb3638bc92bb6b80c938e1c0a312ca1d 7781 raspi-firmware_1.20230405+ds-2_source.buildinfo Checksums-Sha256: 1c8531a14b4db41a6bd28ccf0938dd5d0d3a2aeedfa90a5a9379962b1db925c4 1536 raspi-firmware_1.20230405+ds-2.dsc 5a15ae946029887963d25a7956009fff9fe27cddce2a0211476620ad54d20fc3 379436 raspi-firmware_1.20230405+ds-2.debian.tar.xz ab4ed4556aa860ad9ae731f7eafcfb170428e65d20834cd03ac973efe2d799e3 7781 raspi-firmware_1.20230405+ds-2_source.buildinfo Files: c6b2d2fca56180a1fc86bfc65cbf6262 1536 non-free-firmware/misc optional raspi-firmware_1.20230405+ds-2.dsc 6ff275261d2952c3f7f20067e71885c8 379436 non-free-firmware/misc optional raspi-firmware_1.20230405+ds-2.debian.tar.xz 3e1c7f33fdc6dd1de235b545862e6903 7781 non-free-firmware/misc optional raspi-firmware_1.20230405+ds-2_source.buildinfo -BEGIN PGP SIGNATURE- iHUEARYIAB0WIQRNFAUGU6QC1zaHBJ0kBMlUbhRTYAUCZMFswAAKCRAkBMlUbhRT YCqMAQCqxCbTO6ISsgMPBsu0qd/KsUBLhFXIZXOjXKRAI47dDgEAskDUays4q0SH 98t/I9qAXGY44rGr6NsuVDWfxlVhngY= =Hp5D -END PGP SIGNATURE End Message ---
Bug#1042104: marked as done (ocamlgraph FTBFS with ocaml-dune 3.9.1)
Your message dated Wed, 26 Jul 2023 20:56:42 + with message-id and subject line Bug#1042104: fixed in ocamlgraph 2.0.0-4 has caused the Debian Bug report #1042104, regarding ocamlgraph FTBFS with ocaml-dune 3.9.1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1042104: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042104 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ocamlgraph Version: 2.0.0-3 Severity: serious Tags: ftbfs trixie sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ocamlgraph.html ... debian/rules override_dh_auto_install make[1]: Entering directory '/build/1st/ocamlgraph-2.0.0' touch _build/default/ocamlgraph_gtk.install DESTDIR=/build/1st/ocamlgraph-2.0.0/debian/tmp dune install -pocamlgraph Error: The mandir installation directory is unknown. Hint: It can be specified with --prefix or by setting --mandir make[1]: *** [debian/rules:16: override_dh_auto_install] Error 1 --- End Message --- --- Begin Message --- Source: ocamlgraph Source-Version: 2.0.0-4 Done: Stéphane Glondu We believe that the bug you reported is fixed in the latest version of ocamlgraph, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1042...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Stéphane Glondu (supplier of updated ocamlgraph package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 26 Jul 2023 21:54:59 +0200 Source: ocamlgraph Architecture: source Version: 2.0.0-4 Distribution: unstable Urgency: medium Maintainer: Debian OCaml Maintainers Changed-By: Stéphane Glondu Closes: 1042104 Changes: ocamlgraph (2.0.0-4) unstable; urgency=medium . * Team upload * Use ocaml_dune DH buildsystem (Closes: #1042104) * Bump Standards-Version to 4.6.2 Checksums-Sha1: 2a73f027b5bd69b59e55b324220227ea99b0563f 2027 ocamlgraph_2.0.0-4.dsc d2eaba17b24d2e6fa9a7e4c52d1f8c14e323625b 12220 ocamlgraph_2.0.0-4.debian.tar.xz Checksums-Sha256: 2b32b0d7428eaff006713331c2f5cd20cd47613c63d4599f335840ab98693779 2027 ocamlgraph_2.0.0-4.dsc 796667695b0562fcc7206ad650d0023674c61fd5947365cf5c04fcfd1f0fff35 12220 ocamlgraph_2.0.0-4.debian.tar.xz Files: b08a2fa6672a8a28c4f8fe521c2464a1 2027 libdevel optional ocamlgraph_2.0.0-4.dsc 6f8710f5c67e6e5a48538ef618c52988 12220 libdevel optional ocamlgraph_2.0.0-4.debian.tar.xz -BEGIN PGP SIGNATURE- iQFGBAEBCgAwFiEEbeJOl+yohsxW5iUOIbju8bGJMIEFAmTBesUSHGdsb25kdUBk ZWJpYW4ub3JnAAoJECG47vGxiTCBW/sH/i9ZkRtxdGzdMOC6pbSiJQiu7b8m3dwb CxlvY6mqXxKTXBVN5uObC/IWlwhaJNvSrh84ddjWUAcYjMzX6Kr8NoYYz6nP0mJo qTKvAVpOCy8N2bvKWwIjhTwsx6Q7XEoEXLeCZPOQWxx4VWnuOnr1SvSF/Ubcba1F EuN6SYWyqzaBULJ3vHSznjHgnrmWaXZqq0Y3t/dglC6LAI1Auy2L3OR3B+LsyY6d tUd+gZbuJpTMlOO0kdYTBz0uAV1wo1sDDIBzUcAGeOF0Wy0ok8oo0RAhiqLn/MWP cBRAB7EGlv+0C3x4wE1h0z3seeYfGvnCiDVqfz8XG22RgbYgEPmiVNM= =q6Y/ -END PGP SIGNATURE End Message ---
Bug#1040735: marked as done (ms-gsl: autopkgtest failure due to new CMake deprecation warning)
Your message dated Wed, 26 Jul 2023 20:56:34 + with message-id and subject line Bug#1040735: fixed in ms-gsl 4.0.0-2.1 has caused the Debian Bug report #1040735, regarding ms-gsl: autopkgtest failure due to new CMake deprecation warning to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1040735: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040735 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ms-gsl Version: 4.0.0-2 Severity: important User: roehl...@debian.org Usertags: cmake3.27 Dear maintainer, your package ms-gsl will soon experience autopkgtest failures because the new CMake release 3.27 will issue a deprecation warning on stderr if cmake_minimum_required() asks for compatibility with CMake 3.4 or older. You can check for the exact failure on the cmake pseudo-excuses page from experimental: https://qa.debian.org/excuses.php?experimental=1=cmake For a more in-depth discussion, kindly refer to the debian-devel thread: https://lists.debian.org/debian-devel/2023/06/msg00150.html Cheers Timo --- End Message --- --- Begin Message --- Source: ms-gsl Source-Version: 4.0.0-2.1 Done: Timo Röhling We believe that the bug you reported is fixed in the latest version of ms-gsl, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1040...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Timo Röhling (supplier of updated ms-gsl package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 23 Jul 2023 21:10:48 +0200 Source: ms-gsl Architecture: source Version: 4.0.0-2.1 Distribution: unstable Urgency: medium Maintainer: Nicholas Guriev Changed-By: Timo Röhling Closes: 1040735 Changes: ms-gsl (4.0.0-2.1) unstable; urgency=medium . * Non-maintainer upload. * Fix autopkgtest regression due to CMake warning (Closes: #1040735) Checksums-Sha1: f9e97d8c46d59582cf1d1c2037178c37e1b68c83 1891 ms-gsl_4.0.0-2.1.dsc 0efd01f7d4d7413d2ba0d79c67dca1cdbf85dac6 5184 ms-gsl_4.0.0-2.1.debian.tar.xz 56dcfb0ba1a6444758e0ba62687663c711d841ee 6747 ms-gsl_4.0.0-2.1_amd64.buildinfo Checksums-Sha256: 590ab88004a41feea5590f53ffede3bd29fa4126f3c20a70a3c7f81a15dab87e 1891 ms-gsl_4.0.0-2.1.dsc 280db124a59f38b9f9e1d8ac780167d7c987bd3667fed4afe209db39844341f4 5184 ms-gsl_4.0.0-2.1.debian.tar.xz f60bea0122a8e3f493aaf125ae15e7e23f83b7b9d7d966b50ab98baa50b19d81 6747 ms-gsl_4.0.0-2.1_amd64.buildinfo Files: c94f666f1ca76edfca70517afbdee7c6 1891 libdevel optional ms-gsl_4.0.0-2.1.dsc 17635e0026edc526b25caf5b52889bcf 5184 libdevel optional ms-gsl_4.0.0-2.1.debian.tar.xz 7553d1670d20590f7639c5ae946fe149 6747 libdevel optional ms-gsl_4.0.0-2.1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQHIBAEBCgAyFiEEJvtDgpxjkjCIVtam+C8H+466LVkFAmS9fVIUHHJvZWhsaW5n QGRlYmlhbi5vcmcACgkQ+C8H+466LVnkLwwA0CrKCLWZHbTsG2CaZPjy2fme5V6d YRgs7PuIntCGg6h4N65/gx5cjBTi+BZr/5cfBhsDOWbIAZzu86kONJSBTPXQDaae DxhhUtfDngAar6q7MOfJ0j/zYt65DMF5DNzEzCDPQ0E4t7rlHBMxXqVweZPJGvGn pgk40FQkKq7CBGMM42fs2oXlHM8wEwnos+M3EblWPYT7hqYK7xDyoYeaUGNvZOCC YYAR6oovA5MBWxIIHMh9zHk1HgjQEFrWHV32VORvJ4nSgBUgsHEWmFeTUkgUKa9T cJQ5lklzBd4rawJwOjc0BwOkMUzWylE7l9EB0Dn2FjRLUYxGx1VNbLkzkeQSp96u bjtALv1eXehZCNoFXkFOYSE4cHpIBB6GPPnHO0Xlk0Kil7xAUV9Jmz863f+SDcEm GsomK6+ONmrnueYkIqZMfTvxpiwuFS35QlN6qft8rT20lxB3A2uE4yAQkqmOYlSY PTTBX1os/A30lN0pYeUr08in1YINV4BXaAxl =4fwq -END PGP SIGNATURE End Message ---
Bug#1038684: marked as done (firmware-ath9k-htc: TP-Link TL-WN722N is not reported by "iw dev".)
Your message dated Wed, 26 Jul 2023 20:56:51 + with message-id and subject line Bug#1038684: fixed in open-ath9k-htc-firmware 1.4.0-108-gd856466+dfsg1-1.4 has caused the Debian Bug report #1038684, regarding firmware-ath9k-htc: TP-Link TL-WN722N is not reported by "iw dev". to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1038684: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038684 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: firmware-ath9k-htc Version: 1.4.0-106-gc583009+dfsg1-1 Severity: grave Justification: renders package unusable Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? I'm interested to use the TP-Link TL-WN722N which has worked for several years in earlier Debian releases. * What exactly did you do (or not do) that was effective (or ineffective)? As instructed in https://wiki.debian.org/ath9k_htc, I executed "iw dev". The device was not reported. * What was the outcome of this action? "iw dev" failed to report the device. * What outcome did you expect instead? I expected to "iw dev" to report the device, as documented. *** End of the template - remove these template lines *** -- System Information: Debian Release: 11.7 APT prefers oldstable-updates APT policy: (500, 'oldstable-updates'), (500, 'oldstable-security'), (500, 'oldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-23-amd64 (SMP w/4 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages firmware-ath9k-htc is related to: ii network-manager 1.30.6-1+deb11u1 ii wpasupplicant2:2.9.0-21 -- no debconf information - mobile: +1 778 951 5147 VoIP: +1 604 670 0140 --- End Message --- --- Begin Message --- Source: open-ath9k-htc-firmware Source-Version: 1.4.0-108-gd856466+dfsg1-1.4 Done: Bastian Germann We believe that the bug you reported is fixed in the latest version of open-ath9k-htc-firmware, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1038...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bastian Germann (supplier of updated open-ath9k-htc-firmware package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 26 Jul 2023 21:09:48 +0200 Source: open-ath9k-htc-firmware Architecture: source Version: 1.4.0-108-gd856466+dfsg1-1.4 Distribution: unstable Urgency: medium Maintainer: John Scott Changed-By: Bastian Germann Closes: 1038684 Changes: open-ath9k-htc-firmware (1.4.0-108-gd856466+dfsg1-1.4) unstable; urgency=medium . * Non-maintainer upload. * Add notes on how to generate modaliases. * Remove Qwest/Actiontec 802AIN ID. * Prevent requesting dev firmware. (Closes: #1038684) Checksums-Sha1: 9c01bab2cd02cf86877ea427f83296c2d0424030 2067 open-ath9k-htc-firmware_1.4.0-108-gd856466+dfsg1-1.4.dsc 2bfdaebd905b45e46578e5e6e9c8bb62c7e7cff1 15064 open-ath9k-htc-firmware_1.4.0-108-gd856466+dfsg1-1.4.debian.tar.xz 4ec322e71014271eb1282db7506b73cba5cbd15f 7304 open-ath9k-htc-firmware_1.4.0-108-gd856466+dfsg1-1.4_source.buildinfo Checksums-Sha256: 7efbf878c3a056e360b7f4104a33a7cde72a583dfc77ed6d1bdbe45f19e426e3 2067 open-ath9k-htc-firmware_1.4.0-108-gd856466+dfsg1-1.4.dsc 3bb6e8a21e4098049b1348e40b038056cebd76a38eb805a569729f55a9db92d7 15064 open-ath9k-htc-firmware_1.4.0-108-gd856466+dfsg1-1.4.debian.tar.xz fb5787b27e3806651c49087090a6bdf475ff6b8647ea9ec0a4d9ecd2b7a45e97 7304 open-ath9k-htc-firmware_1.4.0-108-gd856466+dfsg1-1.4_source.buildinfo Files: ea03676eca9b8806e90d6c20df4b55f8 2067 kernel optional open-ath9k-htc-firmware_1.4.0-108-gd856466+dfsg1-1.4.dsc ba2458078ab7f36bf43fd749462a2d9f 15064 kernel optional open-ath9k-htc-firmware_1.4.0-108-gd856466+dfsg1-1.4.debian.tar.xz 00db22a20a98aada6b4f2554cafbd39a 7304 kernel optional open-ath9k-htc-firmware_1.4.0-108-gd856466+dfsg1-1.4_source.buildinfo -BEGIN PGP SIGNATURE-
Bug#1042253: libxlsxwriter: FTBFS: make[1]: *** [debian/rules:12: override_dh_auto_configure] Error 2
Hi Ma Aiguo, Can you check the bug report and prepare a fix? Thanks, Boyuan Yang 在 2023-07-26星期三的 22:25 +0200，Lucas Nussbaum写道： > Source: libxlsxwriter > Version: 1.1.4-2 > Severity: serious > Justification: FTBFS > Tags: trixie sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-20230726 ftbfs-trixie > > Hi, > > During a rebuild of all packages in sid, your package failed to build > on amd64. > > > Relevant part (hopefully): > > make[1]: Entering directory '/<>' > > dh_auto_configure -- \ > > -DBUILD_SHARED_LIBS=ON \ > > -DUSE_SYSTEM_MINIZIP=ON \ > > -DUSE_OPENSSL_MD5=ON \ > > -DBUILD_TESTS=ON \ > > -DBUILD_EXAMPLES=ON \ > > > > cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr > > -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc > > -DCMAKE_INSTALL_LOCALSTATEDIR=/var - > > DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF > > -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON > > -DFETCHCONTENT_FULLY_DISCONNECTED=ON - > > DCMAKE_INSTALL_RUNSTATEDIR=/run -DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=ON > > "-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON > > -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu - > > DBUILD_SHARED_LIBS=ON -DUSE_SYSTEM_MINIZIP=ON -DUSE_OPENSSL_MD5=ON > > -DBUILD_TESTS=ON -DBUILD_EXAMPLES=ON .. > > CMake Deprecation Warning at CMakeLists.txt:106 (cmake_minimum_required): > > Compatibility with CMake < 3.5 will be removed from a future version of > > CMake. > > > > Update the VERSION argument value or use a ... suffix to tell > > CMake that the project does not need compatibility with older versions. > > > > > > -- The C compiler identification is GNU 13.1.0 > > -- Detecting C compiler ABI info > > -- Detecting C compiler ABI info - done > > -- Check for working C compiler: /usr/bin/cc - skipped > > -- Detecting C compile features > > -- Detecting C compile features - done > > -- The CXX compiler identification is GNU 13.1.0 > > -- Detecting CXX compiler ABI info > > -- Detecting CXX compiler ABI info - done > > -- Check for working CXX compiler: /usr/bin/c++ - skipped > > -- Detecting CXX compile features > > -- Detecting CXX compile features - done > > CMake Warning (dev) at /usr/share/cmake-3.27/Modules/FindZLIB.cmake:88 > > (message): > > ZLIB does not provide any COMPONENTS. Calling > > > > find_package(ZLIB COMPONENTS ...) > > > > will always fail. > > Call Stack (most recent call first): > > CMakeLists.txt:219 (find_package) > > This warning is for project developers. Use -Wno-dev to suppress it. > > > > CMake Error at > > /usr/share/cmake-3.27/Modules/FindPackageHandleStandardArgs.cmake:230 > > (message): > > Could NOT find ZLIB (missing: 1.0) (found version "1.2.13") > > Call Stack (most recent call first): > > /usr/share/cmake-3.27/Modules/FindPackageHandleStandardArgs.cmake:600 > > (_FPHSA_FAILURE_MESSAGE) > > /usr/share/cmake-3.27/Modules/FindZLIB.cmake:200 > > (FIND_PACKAGE_HANDLE_STANDARD_ARGS) > > CMakeLists.txt:219 (find_package) > > > > > > -- Configuring incomplete, errors occurred! > > cd obj-x86_64-linux-gnu && tail -v -n \+0 CMakeCache.txt > > ==> CMakeCache.txt <== > > # This is the CMakeCache file. > > # For build in directory: /<>/obj-x86_64-linux-gnu > > # It was generated by CMake: /usr/bin/cmake > > # You can edit this file to change values found and used by cmake. > > # If you do not want to change any of the values, simply exit the editor. > > # If you do want to change a value, simply edit, save, and exit the editor. > > # The syntax for the file is as follows: > > # KEY:TYPE=VALUE > > # KEY is the name of a variable in the cache. > > # TYPE is a hint to GUIs for the type of VALUE, DO NOT EDIT TYPE!. > > # VALUE is the current value for the KEY. > > > > > > # EXTERNAL cache entries > > > > > > //Build libxlsxwriter examples > > BUILD_EXAMPLES:BOOL=ON > > > > //No help, variable specified on the command line. > > BUILD_SHARED_LIBS:UNINITIALIZED=ON > > > > //Build libxlsxwriter tests > > BUILD_TESTS:BOOL=ON > > > > //Path to a program. > > CMAKE_ADDR2LINE:FILEPATH=/usr/bin/addr2line > > > > //Path to a program. > > CMAKE_AR:FILEPATH=/usr/bin/ar > > > > //Choose the type of build, options are: N
Bug#1042097: marked as done (menhir FTBFS with ocaml-dune 3.9.1)
Your message dated Wed, 26 Jul 2023 20:56:26 + with message-id and subject line Bug#1042097: fixed in menhir 20220210+ds1-1 has caused the Debian Bug report #1042097, regarding menhir FTBFS with ocaml-dune 3.9.1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1042097: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042097 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: menhir Version: 20220210+ds-2 Severity: serious Tags: ftbfs trixie sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/menhir.html ... debian/rules override_dh_auto_install make[1]: Entering directory '/build/1st/menhir-20220210+ds' DESTDIR=/build/1st/menhir-20220210+ds/debian/tmp dune install --prefix=usr --libdir=lib/ocaml dune: option '--libdir': the path must be absolute to avoid ambiguity Usage: dune install [OPTION]… [PACKAGE]… Try 'dune install --help' or 'dune --help' for more information. make[1]: *** [debian/rules:18: override_dh_auto_install] Error 1 --- End Message --- --- Begin Message --- Source: menhir Source-Version: 20220210+ds1-1 Done: Stéphane Glondu We believe that the bug you reported is fixed in the latest version of menhir, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1042...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Stéphane Glondu (supplier of updated menhir package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 26 Jul 2023 21:36:14 +0200 Source: menhir Architecture: source Version: 20220210+ds1-1 Distribution: unstable Urgency: medium Maintainer: Debian OCaml Maintainers Changed-By: Stéphane Glondu Closes: 1042097 Changes: menhir (20220210+ds1-1) unstable; urgency=medium . * Team upload * Properly repack upstream sources, without coq-menhirlib * Use ocaml_dune DH buildsystem (Closes: #1042097) * Bump Standards-Version to 4.6.2 Checksums-Sha1: 7f2106b677e81ef541951c0a7811307d85b1b370 2095 menhir_20220210+ds1-1.dsc 392e1d09a344ab85635a332a42f59f87e1190b22 503944 menhir_20220210+ds1.orig.tar.xz c0644f8f7767f8231825df2d45e2a055c92a27b8 13472 menhir_20220210+ds1-1.debian.tar.xz Checksums-Sha256: 7f1c8aba0ef60ea3d2d55ab208588c2b195ccf006440bf8f531cd7341dac6199 2095 menhir_20220210+ds1-1.dsc 48e69ea28608a5c6f6e8865e14f4282c7a54145f9159d5f523c755a1a002c6a5 503944 menhir_20220210+ds1.orig.tar.xz 7852ea7c6c0569755f8ccaf3c49082a922b29e4df620f07aa315e8e3cc17c9b9 13472 menhir_20220210+ds1-1.debian.tar.xz Files: 8d5f6db7566cd1431c3d089f6a802df1 2095 ocaml optional menhir_20220210+ds1-1.dsc 8b5ccf91b21800315904dc4683f14ef6 503944 ocaml optional menhir_20220210+ds1.orig.tar.xz cdb8ebb31068435747bab28ccff2dae3 13472 ocaml optional menhir_20220210+ds1-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQFGBAEBCgAwFiEEbeJOl+yohsxW5iUOIbju8bGJMIEFAmTBdn4SHGdsb25kdUBk ZWJpYW4ub3JnAAoJECG47vGxiTCB8H8H/REG6Ahf6vkeUsE+4DVfuoDO/gNBFmrv Urhs2ELVyPg+D9rXdXB0gJSMb8f9SUzrukiV625ZcWi1gu4pAgVYsdGqF7rwcyak QyW2it5jzRSx87HNq9nZ7VEZK/n2BPP583qCE93c8QbAGRyUfzUS8WDbhb1yb9k4 gf4CN6D7MDXVs+tviZlAk3UViRD5fb7P/VD+/ZJWiwJebsz7zKzzCKg9t433nVVq FwU4Jl7daDm9Vq5DlwCrSTNjXXn9gewoslqq5iII4rkNbChMRkELYgik70lpKAm/ 09Cq/kDJJkdrm1WTnDeIbA5926EcIYeR+hayehz7Tz3Ys/QZgIJo3i0= =rP+6 -END PGP SIGNATURE End Message ---
Bug#1041899: marked as done (libreoffice-uiconfig-report-builder: undeclared file conflicts with libreoffice-report-builder/unstable)
Your message dated Wed, 26 Jul 2023 20:52:23 + with message-id and subject line Bug#1041899: fixed in libreoffice 4:7.6.0~rc2-1 has caused the Debian Bug report #1041899, regarding libreoffice-uiconfig-report-builder: undeclared file conflicts with libreoffice-report-builder/unstable to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1041899: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041899 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libreoffice-uiconfig-report-builder Version: 4:7.6.0~rc1-1 Severity: serious Hi Rene, thanks for the fixes to the other file conflict issues. Unfortunately, your upload also introduces new problems. libreoffice-uiconfig-report-builder now contains a lot of files below /usr/lib/libreoffice/share/config/soffice.cfg/modules/dbreport that also happen to be contained in libreoffice-report-builder (from bullseye-backports to unstable). Are you missing replaces here? Helmut --- End Message --- --- Begin Message --- Source: libreoffice Source-Version: 4:7.6.0~rc2-1 Done: Rene Engelhard We believe that the bug you reported is fixed in the latest version of libreoffice, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1041...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Rene Engelhard (supplier of updated libreoffice package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 26 Jul 2023 20:19:42 +0200 Source: libreoffice Architecture: source Version: 4:7.6.0~rc2-1 Distribution: experimental Urgency: medium Maintainer: Debian LibreOffice Maintainers Changed-By: Rene Engelhard Closes: 1041899 Changes: libreoffice (4:7.6.0~rc2-1) experimental; urgency=medium . [ Rene Engelhard ] * New upstream release candidate . * debian/control.reportbuilder.in: also fix version in Replaces: here (closes: #1041899) * debian/watch: watch rcs again * debian/rules, debian/control.gtk4.in: move libavmediagtk.so to -gtk4 . [ merge from Ubuntu ] * debian/rules: - use gcc for skia on ppc64el for now Checksums-Sha1: 71400f85ede5895d577d9c9759cd8a00701b9134 34101 libreoffice_7.6.0~rc2-1.dsc 95ee9f36e4d950a039011d4241e01685de146f18 165067940 libreoffice_7.6.0~rc2.orig-helpcontent2.tar.xz 6c823e415953ade01d730b98b322afba1f8764c6 206706712 libreoffice_7.6.0~rc2.orig-translations.tar.xz a74e413625b408863707298b67e6625b7893dff0 280011792 libreoffice_7.6.0~rc2.orig.tar.xz abfc42060771c38df3eea234f45f8e13e1944ef1 833 libreoffice_7.6.0~rc2.orig.tar.xz.asc e530078858cbccb4365e468a1af93b6067e9a6b0 24119092 libreoffice_7.6.0~rc2-1.debian.tar.xz a0459e0cdf09964016147331bade67c774a1a827 35651 libreoffice_7.6.0~rc2-1_source.buildinfo Checksums-Sha256: 370d3c7e1d11f0fbb9429f6401a4dfcebc27765e8cdc5c0fb38973745b7b623c 34101 libreoffice_7.6.0~rc2-1.dsc c192ebdb7b7d3d9a17e8f9074e95ea8599876a3f02dac514f5fa4406ff92419f 165067940 libreoffice_7.6.0~rc2.orig-helpcontent2.tar.xz 363928c4021ef1e9f9caf04b1b92efb722c1f32f52ca15feb7ed366cd7f89de0 206706712 libreoffice_7.6.0~rc2.orig-translations.tar.xz 40c1697c887b0f3d4f47c5719fa6048315fa02e5ca46f1ded2310f4105d069c3 280011792 libreoffice_7.6.0~rc2.orig.tar.xz 5fe477ed8a3d69cc5db7cab606dce4931626c57958df45ba0612185e5c8392b3 833 libreoffice_7.6.0~rc2.orig.tar.xz.asc f9db36fd9850329a73ebc021f87126899be0a87993c2fb5e7214e671d5614ed8 24119092 libreoffice_7.6.0~rc2-1.debian.tar.xz 0a04d169e1baadf7d4b9930f2000425b9c8f19d95f8382df4561c1f28257d954 35651 libreoffice_7.6.0~rc2-1_source.buildinfo Files: 090269d5781a4d755e6f338eed8ce965 34101 editors optional libreoffice_7.6.0~rc2-1.dsc 239453ba250b00847f8fb426d1375b86 165067940 editors optional libreoffice_7.6.0~rc2.orig-helpcontent2.tar.xz 46e2c8f7258104628a62f221c4c964ae 206706712 editors optional libreoffice_7.6.0~rc2.orig-translations.tar.xz 710b16baf6cc18d842636a4101f19f0a 280011792 editors optional libreoffice_7.6.0~rc2.orig.tar.xz db2170ee62753ef2016d2d421bc11a07 833 editors optional libreoffice_7.6.0~rc2.orig.tar.xz.asc 48c2bfc45f5047550e6238b4650ad27e 24119092 editors optional libreoffice_7.6.0~rc2-1.debian.tar.xz
Bug#1041136: marked as done (lomiri-indicator-transfer FTBFS with googletest 1.13.0)
Your message dated Wed, 26 Jul 2023 20:52:40 + with message-id and subject line Bug#1041136: fixed in lomiri-indicator-transfer 1.0.0-3 has caused the Debian Bug report #1041136, regarding lomiri-indicator-transfer FTBFS with googletest 1.13.0 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1041136: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041136 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: lomiri-indicator-transfer Version: 1.0.0-2 Severity: serious Tags: ftbfs trixie sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/lomiri-indicator-transfer.html ... In file included from /usr/src/googletest/googlemock/include/gmock/internal/gmock-port.h:57, from /usr/src/googletest/googlemock/include/gmock/internal/gmock-internal-utils.h:49, from /usr/src/googletest/googlemock/include/gmock/gmock-actions.h:145, from /usr/src/googletest/googlemock/include/gmock/gmock.h:56, from /build/1st/lomiri-indicator-transfer-1.0.0/tests/source-mock.h:25, from /build/1st/lomiri-indicator-transfer-1.0.0/tests/mock-source-plugin.cpp:20: /usr/src/googletest/googletest/include/gtest/internal/gtest-port.h:270:2: error: #error C++ versions less than C++14 are not supported. 270 | #error C++ versions less than C++14 are not supported. | ^ ... This can be fixed by changing -std=c++11 to -std=c++14 in tests/CMakeLists.txt --- End Message --- --- Begin Message --- Source: lomiri-indicator-transfer Source-Version: 1.0.0-3 Done: Marius Gripsgard We believe that the bug you reported is fixed in the latest version of lomiri-indicator-transfer, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1041...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Marius Gripsgard (supplier of updated lomiri-indicator-transfer package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 26 Jul 2023 21:19:46 +0200 Source: lomiri-indicator-transfer Architecture: source Version: 1.0.0-3 Distribution: unstable Urgency: medium Maintainer: Debian UBports Team Changed-By: Marius Gripsgard Closes: 1041136 Changes: lomiri-indicator-transfer (1.0.0-3) unstable; urgency=medium . * debian/patches: Add patch to fix FTBFS with googletest 1.13.0 (closes: #1041136) * debian/control: Use my debian email Checksums-Sha1: aaee3a2f4ef24abf4ee7b42f7771674ccd62e389 2223 lomiri-indicator-transfer_1.0.0-3.dsc 07a47fa4c4f6d0ba631ee58901bed36763a273fe 55050 lomiri-indicator-transfer_1.0.0.orig.tar.gz e3fbd0cc4a3a4bee4776de17382953df750dec88 4700 lomiri-indicator-transfer_1.0.0-3.debian.tar.xz 214fc0968fb33b40eb904454dcd5a339292ca23a 9786 lomiri-indicator-transfer_1.0.0-3_source.buildinfo Checksums-Sha256: 0c724c464518a975bea77b0312d736372f1934b036c4854cb6137f6bd0bf24a3 2223 lomiri-indicator-transfer_1.0.0-3.dsc 4d9111d05c8134243f4cf5337e933a5d1fc1883b3138153e901d0293b347768c 55050 lomiri-indicator-transfer_1.0.0.orig.tar.gz 10d37c86c34a3f640fe56be5374a786fc12e749a8d840e58fbe9aeec94e88224 4700 lomiri-indicator-transfer_1.0.0-3.debian.tar.xz b08168210da27e3dc9e980a5b562cc319949734dafe83f20bebc09412019c04f 9786 lomiri-indicator-transfer_1.0.0-3_source.buildinfo Files: e7229ce2af0f345b374523f8ecc7c324 2223 misc optional lomiri-indicator-transfer_1.0.0-3.dsc 7c534fd5393a4c7a670da2e185290a16 55050 misc optional lomiri-indicator-transfer_1.0.0.orig.tar.gz d813711145a85b41d7759737fb70ae1a 4700 misc optional lomiri-indicator-transfer_1.0.0-3.debian.tar.xz 9d9f4514c68525946d17f2330a800390 9786 misc optional lomiri-indicator-transfer_1.0.0-3_source.buildinfo -BEGIN PGP SIGNATURE- iIsEARYIADMWIQT0KegCiCm6mh1JH2jwqyDIdgBMKgUCZMFyMRUcbWFyaW9ncmlw QGRlYmlhbi5vcmcACgkQ8KsgyHYATCpL9QEAj8sctG198FGe83Ab97LxpyusMVr8 occNKGOviX2YxZYBAORhGYgg+7f3Dq727D74Tbzjsqi4U6BTGmL9XjwMvq0H =46Ii -END PGP SIGNATURE End Message ---
Bug#1042041: marked as done (tpm2-pkcs11: FTBFS: gcc: error: unrecognized command-line option '-V')
Your message dated Wed, 26 Jul 2023 22:35:59 +0200 with message-id and subject line Re: tpm2-pkcs11: FTBFS: gcc: error: unrecognized command-line option '-V' has caused the Debian Bug report #1042041, regarding tpm2-pkcs11: FTBFS: gcc: error: unrecognized command-line option '-V' to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1042041: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042041 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: tpm2-pkcs11 Version: 1.9.0-0.2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > gcc version 13.1.0 (Debian 13.1.0-9) > ... rest of stderr output deleted ... > configure:3441: $? = 0 > configure:3430: gcc -V >&5 > gcc: error: unrecognized command-line option '-V' > gcc: fatal error: no input files > compilation terminated. > configure:3441: $? = 1 > configure:3430: gcc -qversion >&5 > gcc: error: unrecognized command-line option '-qversion'; did you mean > '--version'? > gcc: fatal error: no input files > compilation terminated. > configure:3441: $? = 1 > configure:3430: gcc -version >&5 > gcc: error: unrecognized command-line option '-version' > gcc: fatal error: no input files > compilation terminated. > configure:3441: $? = 1 > configure:3461: checking whether the C compiler works > configure:3483: gcc -g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > -D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-z,now conftest.c >&5 > configure:3487: $? = 0 > configure:3537: result: yes > configure:3540: checking for C compiler default output file name > configure:3542: result: a.out > configure:3548: checking for suffix of executables > configure:3555: gcc -o conftest -g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > -D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-z,now conftest.c >&5 > configure:3559: $? = 0 > configure:3582: result: > configure:3604: checking whether we are cross compiling > configure:3612: gcc -o conftest -g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > -D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-z,now conftest.c >&5 > configure:3616: $? = 0 > configure:3623: ./conftest > configure:3627: $? = 0 > configure:3642: result: no > configure:3647: checking for suffix of object files > configure:3670: gcc -c -g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > -D_FORTIFY_SOURCE=2 conftest.c >&5 > configure:3674: $? = 0 > configure:3696: result: o > configure:3700: checking whether the compiler supports GNU C > configure:3720: gcc -c -g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > -D_FORTIFY_SOURCE=2 conftest.c >&5 > configure:3720: $? = 0 > configure:3730: result: yes > configure:3741: checking whether gcc accepts -g > configure:3762: gcc -c -g -Wdate-time -D_FORTIFY_SOURCE=2 conftest.c >&5 > configure:3762: $? = 0 > configure:3806: result: yes > configure:3826: checking for gcc option to enable C11 features > configure:3841: gcc -c -g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > -D_FORTIFY_SOURCE=2 conftest.c >&5 > configure:3841: $? = 0 > configure:3859: result: none needed > configure:3980: checking whether gcc understands -c and -o together > configure:4003: gcc -c conftest.c -o conftest2.o > configure:4006: $? = 0 > configure:4003: gcc -c conftest.c -o conftest2.o > configure:4006: $? = 0 > configure:4018: result: yes > configure:4067: checking build system type > configure:4082: result: x86_64-pc-linux-gnu > configure:4102: checking host system type > configure:4116: result: x86_64-pc-linux-gnu > configure:4157: checking how to print strings > configure:4184: result: printf > configure:4205: checking for a sed that does not truncate output > configure:4275: result: /bin/sed > configure:4293: checking for grep that handles long lines and -e > configure:4357: result: /bin/grep > configure:4362: checking for egrep > configure:4430: result: /bin/grep -E > configure:4435: checking for fgrep > configure:4503: result: /bin/grep -F > configure:4539: checking for ld used by gcc > configure:4607: result: /usr/bin/ld > configure:4614: checking if the linker (/usr/bin/ld) is GNU ld > configure:4630: result: yes > configure:4642: checking for BSD- or MS-compatible name lister (nm) > configure:4697:
Bug#1037609: marked as done (content-hub: ftbfs with GCC-13)
Your message dated Wed, 26 Jul 2023 20:37:01 + with message-id and subject line Bug#1037609: fixed in content-hub 1.0.2-2 has caused the Debian Bug report #1037609, regarding content-hub: ftbfs with GCC-13 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1037609: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037609 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:content-hub Version: 1.0.2-1 Severity: normal Tags: sid trixie User: debian-...@lists.debian.org Usertags: ftbfs-gcc-13 [This bug is targeted to the upcoming trixie release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-13/g++-13, but succeeds to build with gcc-12/g++-12. The severity of this report will be raised before the trixie release. The full build log can be found at: http://qa-logs.debian.net/2023/05/22/logs/content-hub_1.0.2-1_unstable_gccexp.log The last lines of the build log are at the end of this report. To build with GCC 13, either set CC=gcc-13 CXX=g++-13 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-13/porting_to.html [...] Normalized debian/content-hub/usr/share/locale/mi/LC_MESSAGES/content-hub.mo Normalized debian/content-hub/usr/share/locale/th/LC_MESSAGES/content-hub.mo Normalized debian/content-hub/usr/share/locale/kn/LC_MESSAGES/content-hub.mo Normalized debian/content-hub/usr/share/locale/gd/LC_MESSAGES/content-hub.mo Normalized debian/content-hub/usr/share/locale/oc/LC_MESSAGES/content-hub.mo Normalized debian/content-hub/usr/share/locale/eu/LC_MESSAGES/content-hub.mo Normalized debian/content-hub/usr/share/locale/jbo/LC_MESSAGES/content-hub.mo Normalized debian/content-hub/usr/share/locale/te/LC_MESSAGES/content-hub.mo Normalized debian/content-hub/usr/share/locale/tr/LC_MESSAGES/content-hub.mo Normalized debian/content-hub/usr/share/locale/ka/LC_MESSAGES/content-hub.mo Normalized debian/content-hub/usr/share/locale/da/LC_MESSAGES/content-hub.mo Normalized debian/content-hub/usr/share/locale/pam/LC_MESSAGES/content-hub.mo Normalized debian/content-hub/usr/share/locale/lo/LC_MESSAGES/content-hub.mo Normalized debian/content-hub/usr/share/locale/nan/LC_MESSAGES/content-hub.mo Normalized debian/content-hub/usr/share/locale/sr/LC_MESSAGES/content-hub.mo Normalized debian/content-hub/usr/share/locale/nl/LC_MESSAGES/content-hub.mo Normalized debian/content-hub/usr/share/locale/ps/LC_MESSAGES/content-hub.mo Normalized debian/content-hub/usr/share/locale/dv/LC_MESSAGES/content-hub.mo Normalized debian/content-hub/usr/share/locale/mk/LC_MESSAGES/content-hub.mo Normalized debian/content-hub/usr/share/locale/ko/LC_MESSAGES/content-hub.mo Normalized debian/content-hub/usr/share/locale/ja/LC_MESSAGES/content-hub.mo Normalized debian/content-hub/usr/share/locale/en_AU/LC_MESSAGES/content-hub.mo Normalized debian/content-hub/usr/share/locale/ln/LC_MESSAGES/content-hub.mo Normalized debian/content-hub/usr/share/locale/cy/LC_MESSAGES/content-hub.mo Normalized debian/content-hub/usr/share/locale/ar/LC_MESSAGES/content-hub.mo Normalized debian/content-hub/usr/share/locale/ca/LC_MESSAGES/content-hub.mo Normalized debian/content-hub/usr/share/locale/id/LC_MESSAGES/content-hub.mo Normalized debian/content-hub/usr/share/locale/si/LC_MESSAGES/content-hub.mo Normalized debian/content-hub/usr/share/locale/he/LC_MESSAGES/content-hub.mo Normalized debian/content-hub/usr/share/locale/sv/LC_MESSAGES/content-hub.mo dh_compress -O-- -O-Bbuild dh_fixperms -O-- -O-Bbuild debian/rules override_dh_missing make[1]: Entering directory '/<>' dh_missing --fail-missing make[1]: Leaving directory '/<>' dh_dwz -a -O-- -O-Bbuild dh_strip -a -O-- -O-Bbuild dh_makeshlibs -a -O-- -O-Bbuild dpkg-gensymbols: error: some new
Processed: bug 1042164 is forwarded to https://github.com/MEGA65/open-roms/pull/74
Processing commands for cont...@bugs.debian.org: > forwarded 1042164 https://github.com/MEGA65/open-roms/pull/74 Bug #1042164 [src:open-roms] open-roms: FTBFS: tools/build_segment.cc:94:60: error: ‘uint16_t’ was not declared in this scope Set Bug forwarded-to-address to 'https://github.com/MEGA65/open-roms/pull/74'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1042164: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042164 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1042354: golang-github-marten-seemann-qtls-go1-19: FTBFS: dh_auto_test: error: cd _build && go test -vet=off -v -p 8 github.com/marten-seemann/qtls-go1-19 returned exit code 1
Source: golang-github-marten-seemann-qtls-go1-19 Version: 0.1.0-3 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230726 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules binary > dh binary --builddirectory=_build --buildsystem=golang --with=golang >dh_update_autotools_config -O--builddirectory=_build -O--buildsystem=golang >dh_autoreconf -O--builddirectory=_build -O--buildsystem=golang >dh_auto_configure -O--builddirectory=_build -O--buildsystem=golang >dh_auto_build -O--builddirectory=_build -O--buildsystem=golang > cd _build && go install -trimpath -v -p 8 > github.com/marten-seemann/qtls-go1-19 > internal/goarch > internal/coverage/rtcov > internal/unsafeheader > internal/goos > internal/goexperiment > runtime/internal/syscall > runtime/internal/atomic > internal/race > internal/abi > internal/cpu > runtime/internal/math > runtime/internal/sys > sync/atomic > unicode > unicode/utf8 > container/list > internal/itoa > math/bits > crypto/internal/alias > crypto/subtle > crypto/internal/boring/sig > unicode/utf16 > vendor/golang.org/x/crypto/cryptobyte/asn1 > internal/nettrace > vendor/golang.org/x/crypto/internal/alias > golang.org/x/crypto/internal/alias > golang.org/x/crypto/cryptobyte/asn1 > internal/bytealg > math > runtime > internal/reflectlite > sync > internal/testlog > internal/singleflight > internal/godebug > runtime/cgo > internal/intern > math/rand > errors > sort > io > internal/oserror > path > internal/safefilepath > strconv > crypto/internal/nistec/fiat > syscall > vendor/golang.org/x/net/dns/dnsmessage > hash > bytes > crypto/internal/randutil > strings > crypto > reflect > crypto/rc4 > net/netip > internal/syscall/execenv > time > internal/syscall/unix > context > io/fs > internal/poll > embed > internal/fmtsort > encoding/binary > os > encoding/base64 > crypto/md5 > crypto/internal/edwards25519/field > crypto/cipher > vendor/golang.org/x/crypto/internal/poly1305 > golang.org/x/crypto/internal/poly1305 > crypto/internal/nistec > golang.org/x/crypto/curve25519/internal/field > encoding/pem > crypto/internal/boring > crypto/des > crypto/internal/edwards25519 > crypto/aes > crypto/sha512 > crypto/hmac > crypto/sha1 > crypto/sha256 > vendor/golang.org/x/crypto/chacha20 > vendor/golang.org/x/crypto/hkdf > fmt > net > path/filepath > io/ioutil > crypto/ecdh > golang.org/x/crypto/chacha20 > golang.org/x/crypto/curve25519 > vendor/golang.org/x/sys/cpu > golang.org/x/sys/cpu > golang.org/x/crypto/hkdf > golang.org/x/crypto/chacha20poly1305 > vendor/golang.org/x/crypto/chacha20poly1305 > encoding/hex > net/url > math/big > crypto/elliptic > crypto/internal/bigmod > crypto/internal/boring/bbig > crypto/dsa > crypto/rand > encoding/asn1 > crypto/ed25519 > crypto/rsa > crypto/x509/pkix > vendor/golang.org/x/crypto/cryptobyte > golang.org/x/crypto/cryptobyte > crypto/ecdsa > crypto/x509 > crypto/tls > github.com/marten-seemann/qtls-go1-19 >dh_auto_test -O--builddirectory=_build -O--buildsystem=golang > cd _build && go test -vet=off -v -p 8 > github.com/marten-seemann/qtls-go1-19 > === RUN TestSignatureSelection > --- PASS: TestSignatureSelection (0.00s) > === RUN TestLegacyTypeAndHash > --- PASS: TestLegacyTypeAndHash (0.00s) > === RUN TestSupportedSignatureAlgorithms > --- PASS: TestSupportedSignatureAlgorithms (0.00s) > === RUN TestRoundUp > --- PASS: TestRoundUp (0.00s) > === RUN TestRemovePadding > --- PASS: TestRemovePadding (0.00s) > === RUN TestCertificateSelection > --- PASS: TestCertificateSelection (0.00s) > === RUN TestDynamicRecordSizingWithStreamCipher > --- PASS: TestDynamicRecordSizingWithStreamCipher (0.00s) > === RUN TestDynamicRecordSizingWithCBC > --- PASS: TestDynamicRecordSizingWithCBC (0.00s) > === RUN TestDynamicRecordSizingWithAEAD > --- PASS: TestDynamicRecordSizingWithAEAD (0.00s) > === RUN TestDynamicRecordSizingWithTLSv13 > --- PASS: TestDynamicRecordSizingWithTLSv13 (0.00s) > === RUN TestHairpinInClose > --- PASS: TestHairpinInClose (0.00s) > === RUN TestHandshakeClientRSARC4 > === RUN TestHandshakeClientRSARC4/TLSv10 > === PAUSE TestHandshakeClientRSARC4/TLSv10 > === RUN TestHandshakeClientRSARC4/TLSv11 > === PAUSE TestHandshakeClientRSARC4/TLSv11 > === RUN TestHandshakeClientRSARC4/TLSv12 > === PAUSE TestHandshakeClientRSARC4/TLSv12 > === CONT TestHandshak
Bug#1042357: qt6-quick3d: FTBFS: dh_missing: error: missing files, aborting
Source: qt6-quick3d Version: 6.4.2-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230726 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > # Reproducible builds: remove build paths from .prl files > sed -i -e '/^QMAKE_PRL_BUILD_DIR/d' > debian/tmp/usr/lib/x86_64-linux-gnu/libQt6*.prl > make[1]: Leaving directory '/<>' >dh_install -O--buildsystem=cmake\+ninja >dh_installdocs -O--buildsystem=cmake\+ninja >dh_installchangelogs -O--buildsystem=cmake\+ninja >dh_installsystemduser -O--buildsystem=cmake\+ninja >dh_perl -O--buildsystem=cmake\+ninja >dh_link -O--buildsystem=cmake\+ninja >dh_strip_nondeterminism -O--buildsystem=cmake\+ninja > debian/qml6-module-quick3d/usr/lib/x86_64-linux-gnu/qt6/qml/QtQuick3D/designer/images/cubemaptext...@2x.png: > 2797 bytes of garbage after IEND chunk at > /usr/share/perl5/File/StripNondeterminism/handlers/png.pm line 172. > debian/qml6-module-quick3d/usr/lib/x86_64-linux-gnu/qt6/qml/QtQuick3D/designer/images/cubemaptexture.png: > 2879 bytes of garbage after IEND chunk at > /usr/share/perl5/File/StripNondeterminism/handlers/png.pm line 172. > debian/qml6-module-quick3d-particles3d/usr/lib/x86_64-linux-gnu/qt6/qml/QtQuick3D/Particles3D/designer/images/repeller-16px.png: > 266 bytes of garbage after IEND chunk at > /usr/share/perl5/File/StripNondeterminism/handlers/png.pm line 172. > debian/qml6-module-quick3d-particles3d/usr/lib/x86_64-linux-gnu/qt6/qml/QtQuick3D/Particles3D/designer/images/scale-affector-16px.png: > 284 bytes of garbage after IEND chunk at > /usr/share/perl5/File/StripNondeterminism/handlers/png.pm line 172. >dh_compress -O--buildsystem=cmake\+ninja >dh_fixperms -O--buildsystem=cmake\+ninja >dh_missing -O--buildsystem=cmake\+ninja > dh_missing: warning: > usr/lib/x86_64-linux-gnu/qt6/examples/quick3d/antialiasing/antialiasing > exists in debian/tmp but is not installed to anywhere > dh_missing: warning: > usr/lib/x86_64-linux-gnu/qt6/examples/quick3d/bakedlightmap/bakedlightmap > exists in debian/tmp but is not installed to anywhere > dh_missing: warning: > usr/lib/x86_64-linux-gnu/qt6/examples/quick3d/customeffect/customeffect > exists in debian/tmp but is not installed to anywhere > dh_missing: warning: > usr/lib/x86_64-linux-gnu/qt6/examples/quick3d/customgeometry/customgeometry > exists in debian/tmp but is not installed to anywhere > dh_missing: warning: > usr/lib/x86_64-linux-gnu/qt6/examples/quick3d/custominstancing/custominstancing > exists in debian/tmp but is not installed to anywhere > dh_missing: warning: > usr/lib/x86_64-linux-gnu/qt6/examples/quick3d/custommaterial/custommaterial > exists in debian/tmp but is not installed to anywhere > dh_missing: warning: > usr/lib/x86_64-linux-gnu/qt6/examples/quick3d/custommorphing/custommorphing > exists in debian/tmp but is not installed to anywhere > dh_missing: warning: > usr/lib/x86_64-linux-gnu/qt6/examples/quick3d/customshaders/customshaders > exists in debian/tmp but is not installed to anywhere > dh_missing: warning: > usr/lib/x86_64-linux-gnu/qt6/examples/quick3d/dynamiccreation/dynamiccreation > exists in debian/tmp but is not installed to anywhere > dh_missing: warning: > usr/lib/x86_64-linux-gnu/qt6/examples/quick3d/dynamictexture/dynamictexture > exists in debian/tmp but is not installed to anywhere > dh_missing: warning: > usr/lib/x86_64-linux-gnu/qt6/examples/quick3d/effects/effects exists in > debian/tmp but is not installed to anywhere > dh_missing: warning: > usr/lib/x86_64-linux-gnu/qt6/examples/quick3d/hellocube/hellocube exists in > debian/tmp but is not installed to anywhere > dh_missing: warning: > usr/lib/x86_64-linux-gnu/qt6/examples/quick3d/helloqtquick3d/helloqtquick3d > exists in debian/tmp but is not installed to anywhere > dh_missing: warning: > usr/lib/x86_64-linux-gnu/qt6/examples/quick3d/instancing/instancing exists in > debian/tmp but is not installed to anywhere > dh_missing: warning: > usr/lib/x86_64-linux-gnu/qt6/examples/quick3d/intro/intro exists in > debian/tmp but is not installed to anywhere > dh_missing: warning: > usr/lib/x86_64-linux-gnu/qt6/examples/quick3d/lights/lights exists in > debian/tmp but is not installed to anywhere > dh_missing: warning: > usr/lib/x86_64-linux-gnu/qt6/examples/quick3d/morphing/morphing exists in > debian/tmp but is not installed to anywhere > dh_missing: warning: > usr/lib/x86_64-linux-gnu/qt6/examples/quick3d/offlineshaders/offlineshaders > exists in debian/tmp but is not installed to anywhere > dh_mi
Bug#1042356: rapid-photo-downloader: FTBFS: make: *** [debian/rules:8: clean] Error 25
Source: rapid-photo-downloader
Version: 0.9.33-1.1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230726 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules clean
> dh clean --with python3 --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:240: python3.11 setup.py clean
> error in rapid-photo-downloader setup command: 'python_requires' must be a
> string containing valid version specifiers; Invalid specifier: '>=3.6.*'
> E: pybuild pybuild:388: clean: plugin distutils failed with: exit code=1:
> python3.11 setup.py clean
> dh_auto_clean: error: pybuild --clean -i python{version} -p 3.11 returned
> exit code 13
> make: *** [debian/rules:8: clean] Error 25
The full build log is available from:
http://qa-logs.debian.net/2023/07/26/rapid-photo-downloader_0.9.33-1.1_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230726;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230726=lu...@debian.org=1=1=1=1#results
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
Bug#1042352: glib-networking: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 MESON_TESTTHREADS=8 meson test returned exit code 3
Source: glib-networking Version: 2.74.0-4 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230726 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_auto_configure -- \ > -Dauto_features=enabled \ > -Denvironment_proxy=disabled \ > -Dinstalled_tests=true > cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson setup .. > --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc > --localstatedir=/var --libdir=lib/x86_64-linux-gnu -Dauto_features=enabled > -Denvironment_proxy=disabled -Dinstalled_tests=true > The Meson build system > Version: 1.2.0 > Source dir: /<> > Build dir: /<>/obj-x86_64-linux-gnu > Build type: native build > Project name: glib-networking > Project version: 2.74.0 > C compiler for the host machine: cc (gcc 13.1.0 "cc (Debian 13.1.0-9) 13.1.0") > C linker for the host machine: cc ld.bfd 2.40.90.20230720 > Host machine cpu family: x86_64 > Host machine cpu: x86_64 > Compiler for C supports arguments -Werror=declaration-after-statement: YES > Compiler for C supports arguments -Werror=implicit-function-declaration: YES > Compiler for C supports link arguments > -Wl,--version-script,/<>/glib-networking.map: YES > Found pkg-config: /usr/bin/pkg-config (1.8.1) > Run-time dependency glib-2.0 found: YES 2.76.4 > Run-time dependency gio-2.0 found: YES 2.76.4 > Run-time dependency gobject-2.0 found: YES 2.76.4 > Run-time dependency gmodule-2.0 found: YES 2.76.4 > Run-time dependency libproxy-1.0 found: YES 0.4.18 > Run-time dependency gsettings-desktop-schemas found: YES 44.0 > Header "dlfcn.h" has symbol "RTLD_NOLOAD" : YES > Run-time dependency gnutls found: YES 3.7.9 > Configuring config.h using configuration > Program msgfmt found: YES (/usr/bin/msgfmt) > Program msginit found: YES (/usr/bin/msginit) > Program msgmerge found: YES (/usr/bin/msgmerge) > Program xgettext found: YES (/usr/bin/xgettext) > Configuring org.gtk.GLib.PACRunner.service using configuration > Configuring glib-pacrunner.service using configuration > Configuring environment-libproxy.test using configuration > Configuring gnome.test using configuration > Configuring certificate-gnutls.test using configuration > Checking for size of "time_t" : 8 > Configuring file-database-gnutls.test using configuration > Checking for size of "time_t" : 8 (cached) > Configuring connection-gnutls.test using configuration > Checking for size of "time_t" : 8 (cached) > Dependency gio-2.0 found: YES 2.76.4 (cached) > Program gio-querymodules found: YES > (/usr/lib/x86_64-linux-gnu/glib-2.0/gio-querymodules) > Build targets in project: 85 > > glib-networking 2.74.0 > > GnuTLS support : YES > OpenSSL support : NO > Environment proxy support: NO > libproxy support : YES > GNOME proxy support : YES > > User defined options > auto_features: enabled > buildtype: plain > libdir : lib/x86_64-linux-gnu > localstatedir: /var > prefix : /usr > sysconfdir : /etc > wrap_mode: nodownload > environment_proxy: disabled > installed_tests : true > > Found ninja-1.11.1 at /usr/bin/ninja > make[1]: Leaving directory '/<>' >dh_auto_build > cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 ninja -j8 -v > [1/108] /usr/bin/msgfmt -o po/ar/LC_MESSAGES/glib-networking.mo ../po/ar.po > [2/108] /usr/bin/msgfmt -o po/an/LC_MESSAGES/glib-networking.mo ../po/an.po > [3/108] /usr/bin/msgfmt -o po/ab/LC_MESSAGES/glib-networking.mo ../po/ab.po > [4/108] /usr/bin/msgfmt -o po/as/LC_MESSAGES/glib-networking.mo ../po/as.po > [5/108] /usr/bin/msgfmt -o po/bs/LC_MESSAGES/glib-networking.mo ../po/bs.po > [6/108] /usr/bin/msgfmt -o po/bg/LC_MESSAGES/glib-networking.mo ../po/bg.po > [7/108] /usr/bin/msgfmt -o po/be/LC_MESSAGES/glib-networking.mo ../po/be.po > [8/108] /usr/bin/msgfmt -o po/bn_IN/LC_MESSAGES/glib-networking.mo > ../po/bn_IN.po > [9/108] /usr/bin/msgfmt -o po/cs/LC_MESSAGES/glib-networking.mo ../po/cs.po > [10/108] /usr/bin/msgfmt -o po/ca@valencia/LC_MESSAGES/glib-networking.mo > ../po/c...@valencia.po > [11/108] /usr/bin/msgfmt -o po/ca/LC_MESSAGES/glib-networking.mo ../po/ca.po > [12/108] /usr/bin/msgfmt -o po/da/LC_MESSAGES/glib-networking.mo ../po/da.po > [13/108] /usr/bin/msgfmt -o po/el/LC_MESSAGES/glib-networking.mo ../po/el.po > [14/108] /usr/bin/msgfmt -o
Bug#1042355: subdownloader: FTBFS: make: *** [debian/rules:9: clean] Error 25
Source: subdownloader
Version: 2.1.0-5
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230726 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules clean
> dh clean --buildsystem pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:240: python3.11 setup.py clean
> /usr/lib/python3/dist-packages/setuptools/config/setupcfg.py:293:
> _DeprecatedConfig: Deprecated config in `setup.cfg`
> !!
>
>
>
> The license_file parameter is deprecated, use license_files instead.
>
> By 2023-Oct-30, you need to update your project and remove deprecated
> calls
> or your builds will no longer be supported.
>
> See
> https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for
> details.
>
>
>
> !!
> parsed = self.parsers.get(option_name, lambda x: x)(value)
> error in subdownloader setup command: 'python_requires' must be a string
> containing valid version specifiers; Invalid specifier: '>=3.5.*'
> E: pybuild pybuild:388: clean: plugin distutils failed with: exit code=1:
> python3.11 setup.py clean
> dh_auto_clean: error: pybuild --clean -i python{version} -p 3.11 returned
> exit code 13
> make: *** [debian/rules:9: clean] Error 25
The full build log is available from:
http://qa-logs.debian.net/2023/07/26/subdownloader_2.1.0-5_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230726;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230726=lu...@debian.org=1=1=1=1#results
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
Bug#1042353: scikit-build: FTBFS: make[1]: *** [debian/rules:35: override_dh_auto_test] Error 4
Source: scikit-build Version: 0.16.4-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230726 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > py3versions: no X-Python3-Version in control file, using supported versions > set -e ; set -x ; for i in 3.11 ; do \ > python$i -m pytest -k 'not test_hello_sdist and not > test_hello_sdist_with_base and not test_sdist_with_symlinks and not > test_manifest_in_sdist and not test_generator_cleanup and not test_fortran > and not test_pep518_findpython and not test_pep518 and not test_dual_pep518 > and not test_hello_develop and not test_install_command and not > test_help_commands and not test_test_command'; \ > done > + python3.11 -m pytest -k not test_hello_sdist and not > test_hello_sdist_with_base and not test_sdist_with_symlinks and not > test_manifest_in_sdist and not test_generator_cleanup and not test_fortran > and not test_pep518_findpython and not test_pep518 and not test_dual_pep518 > and not test_hello_develop and not test_install_command and not > test_help_commands and not test_test_command > ImportError while loading conftest '/<>/tests/conftest.py'. > tests/__init__.py:20: in > import pkg_resources > /usr/lib/python3/dist-packages/pkg_resources/__init__.py:118: in > warnings.warn( > E DeprecationWarning: pkg_resources is deprecated as an API. See > https://setuptools.pypa.io/en/latest/pkg_resources.html > make[1]: *** [debian/rules:35: override_dh_auto_test] Error 4 The full build log is available from: http://qa-logs.debian.net/2023/07/26/scikit-build_0.16.4-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230726;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230726=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime.
Bug#1042351: binutils-avr: FTBFS: make: *** [debian/rules:88: install] Error 2
Source: binutils-avr Version: 2.26.20160125+Atmel3.6.2-5 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230726 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[4]: Entering directory '/<>/binutils/libiberty/testsuite' > make[4]: Nothing to be done for 'install'. > make[4]: Leaving directory '/<>/binutils/libiberty/testsuite' > make[3]: Leaving directory '/<>/binutils/libiberty' > make[2]: Nothing to be done for 'install-target'. > make[2]: Leaving directory '/<>/binutils' > make[1]: Leaving directory '/<>/binutils' > #cp debian/gasp.1 debian/binutils-avr/usr/share/man/man1/avr-gasp.1 > # Non standard avr dir to keep FHS happy > mv debian/binutils-avr/usr/avr debian/binutils-avr/usr/lib/ > # Convert hardlinks to softlinks > cd debian/binutils-avr/usr/lib/avr/bin && for f in *; do \ > rm ../../../bin/avr-$f; \ > ln -s ../lib/avr/bin/$f ../../../bin/avr-$f; \ > done > /bin/sh: 1: cd: can't cd to debian/binutils-avr/usr/lib/avr/bin > make: *** [debian/rules:88: install] Error 2 The full build log is available from: http://qa-logs.debian.net/2023/07/26/binutils-avr_2.26.20160125+Atmel3.6.2-5_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230726;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230726=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime.
Bug#1042348: qt6-webview: FTBFS: dh_missing: error: missing files, aborting
Source: qt6-webview
Version: 6.4.2-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230726 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> # Reproducible builds: remove build paths from .prl files
> sed -i -e '/^QMAKE_PRL_BUILD_DIR/d'
> debian/tmp/usr/lib/x86_64-linux-gnu/libQt6*.prl
> make[1]: Leaving directory '/<>'
>dh_install -O--buildsystem=cmake\+ninja
>dh_installdocs -O--buildsystem=cmake\+ninja
>dh_installchangelogs -O--buildsystem=cmake\+ninja
>dh_installsystemduser -O--buildsystem=cmake\+ninja
>dh_perl -O--buildsystem=cmake\+ninja
>dh_link -O--buildsystem=cmake\+ninja
>dh_strip_nondeterminism -O--buildsystem=cmake\+ninja
>dh_compress -O--buildsystem=cmake\+ninja
>dh_fixperms -O--buildsystem=cmake\+ninja
>dh_missing -O--buildsystem=cmake\+ninja
> dh_missing: warning:
> usr/lib/x86_64-linux-gnu/qt6/examples/webview/minibrowser/minibrowser exists
> in debian/tmp but is not installed to anywhere
> dh_missing: error: missing files, aborting
> The following debhelper tools have reported what they installed (with
> files per package)
>* dh_install: libqt6webview6 (2), libqt6webviewquick6 (2),
> qml6-module-qtwebview (3), qt6-webview-dev (46), qt6-webview-plugins (1)
>* dh_installdocs: libqt6webview6 (0), libqt6webviewquick6 (0),
> qml6-module-qtwebview (0), qt6-webview-dev (0), qt6-webview-plugins (0)
> If the missing files are installed by another tool, please file a bug
> against it.
> When filing the report, if the tool is not part of debhelper itself,
> please reference the
> "Logging helpers and dh_missing" section from the "PROGRAMMING" guide
> for debhelper (10.6.3+).
> (in the debhelper package: /usr/share/doc/debhelper/PROGRAMMING.gz)
> Be sure to test with dpkg-buildpackage -A/-B as the results may vary
> when only a subset is built
> If the omission is intentional or no other helper can take care of this
> consider adding the
> paths to debian/not-installed.
>
> Remember to be careful with paths containing "x86_64-linux-gnu", where
> you might need to
> use a wildcard or (assuming compat 13+) e.g. ${DEB_HOST_MULTIARCH} in
> debian/not-installed
> to ensure it works on all architectures (see #961104).
> make: *** [debian/rules:12: binary] Error 25
The full build log is available from:
http://qa-logs.debian.net/2023/07/26/qt6-webview_6.4.2-2_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230726;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230726=lu...@debian.org=1=1=1=1#results
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
Bug#1042347: cool-retro-term: FTBFS: make[2]: *** No rule to make target 'qml/fonts/1979-atari-400-800/AtariClassic-Regular.ttf', needed by 'qrc_resources.cpp'. Stop.
Source: cool-retro-term Version: 1.2.0+ds2-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230726 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[2]: Entering directory '/<>/app' > g++ -c -pipe -g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > -D_FORTIFY_SOURCE=2 -Wall -Wextra -D_REENTRANT -fPIC -DQT_NO_DEBUG > -DQT_QUICKCONTROLS2_LIB -DQT_QUICK_LIB -DQT_WIDGETS_LIB -DQT_GUI_LIB > -DQT_QMLMODELS_LIB -DQT_QML_LIB -DQT_NETWORK_LIB -DQT_SQL_LIB -DQT_CORE_LIB > -I. -I/usr/include/x86_64-linux-gnu/qt5 > -I/usr/include/x86_64-linux-gnu/qt5/QtQuickControls2 > -I/usr/include/x86_64-linux-gnu/qt5/QtQuick > -I/usr/include/x86_64-linux-gnu/qt5/QtWidgets > -I/usr/include/x86_64-linux-gnu/qt5/QtGui > -I/usr/include/x86_64-linux-gnu/qt5/QtQmlModels > -I/usr/include/x86_64-linux-gnu/qt5/QtQml > -I/usr/include/x86_64-linux-gnu/qt5/QtNetwork > -I/usr/include/x86_64-linux-gnu/qt5/QtSql > -I/usr/include/x86_64-linux-gnu/qt5/QtCore -I. > -I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -o main.o main.cpp > main.cpp: In function ‘int main(int, char**)’: > main.cpp:52:154: warning: ‘QTextStream& > QTextStreamFunctions::endl(QTextStream&)’ is deprecated: Use Qt::endl > [-Wdeprecated-declarations] >52 | cout << "Usage: " << argv[0] << " [--default-settings] > [--workdir ] [--program ] [-p|--profile ] [--fullscreen] > [-h|--help]" << endl; > | > > ^~~~ > In file included from /usr/include/x86_64-linux-gnu/qt5/QtCore/qdebug.h:49, > from > /usr/include/x86_64-linux-gnu/qt5/QtQml/qqmlprivate.h:68, > from /usr/include/x86_64-linux-gnu/qt5/QtQml/qqml.h:43, > from /usr/include/x86_64-linux-gnu/qt5/QtQml/qqmlengine.h:47, > from > /usr/include/x86_64-linux-gnu/qt5/QtQml/qqmlapplicationengine.h:43, > from > /usr/include/x86_64-linux-gnu/qt5/QtQml/QQmlApplicationEngine:1, > from main.cpp:1: > /usr/include/x86_64-linux-gnu/qt5/QtCore/qtextstream.h:293:75: note: declared > here > 293 | Q_CORE_EXPORT QT_DEPRECATED_VERSION_X(5, 15, "Use Qt::endl") > QTextStream (QTextStream ); > | > ^~~~ > main.cpp:53:90: warning: ‘QTextStream& > QTextStreamFunctions::endl(QTextStream&)’ is deprecated: Use Qt::endl > [-Wdeprecated-declarations] >53 | cout << " --default-settings Run cool-retro-term with the > default settings" << endl; > | >^~~~ > /usr/include/x86_64-linux-gnu/qt5/QtCore/qtextstream.h:293:75: note: declared > here > 293 | Q_CORE_EXPORT QT_DEPRECATED_VERSION_X(5, 15, "Use Qt::endl") > QTextStream (QTextStream ); > | > ^~~~ > main.cpp:54:78: warning: ‘QTextStream& > QTextStreamFunctions::endl(QTextStream&)’ is deprecated: Use Qt::endl > [-Wdeprecated-declarations] >54 | cout << " --workdir Change working directory to > 'dir'" << endl; > | >^~~~ > /usr/include/x86_64-linux-gnu/qt5/QtCore/qtextstream.h:293:75: note: declared > here > 293 | Q_CORE_EXPORT QT_DEPRECATED_VERSION_X(5, 15, "Use Qt::endl") > QTextStream (QTextStream ); > | > ^~~~ > main.cpp:55:142: warning: ‘QTextStream& > QTextStreamFunctions::endl(QTextStream&)’ is deprecated: Use Qt::endl > [-Wdeprecated-declarations] >55 | cout << " -e Command to execute. This > option will catch all following arguments, so use it as the last option." << > endl; > | >^~~~ > /usr/include/x86_64-linux-gnu/qt5/QtCore/qtextstream.h:293:75: note: declared > here > 293 | Q_CORE_EXPORT QT_DEPRECATED_VERSION_X(5, 15, "Use Qt::endl") > QTextStream (QTextStream ); > | &
Bug#1042349: python-wsgi-intercept: FTBFS: failed tests
Source: python-wsgi-intercept Version: 1.9.3-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230726 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > make[1]: pyversions: No such file or directory > py3versions: no X-Python3-Version in control file, using supported versions > set -e ; set -x ; for i in 3.11 ; do \ > PYMAJOR=`echo $i | cut -d'.' -f1` ; \ > echo "===> Testing with python$i (python$PYMAJOR)" ; \ > WSGI_INTERCEPT_SKIP_NETWORK=true PYTHON=$i PYTHONPATH=. python$i -m > pytest wsgi_intercept/tests ; \ > done > + echo 3.11 > + cut -d. -f1 > + PYMAJOR=3 > + echo ===> Testing with python3.11 (python3) > ===> Testing with python3.11 (python3) > + WSGI_INTERCEPT_SKIP_NETWORK=true PYTHON=3.11 PYTHONPATH=. python3.11 -m > pytest wsgi_intercept/tests > = test session starts > == > platform linux -- Python 3.11.4, pytest-7.4.0, pluggy-1.2.0 > rootdir: /<> > collected 2 items / 8 errors > > ERRORS > > __ ERROR collecting wsgi_intercept/tests/test_http_client.py > ___ > ImportError while importing test module > '/<>/wsgi_intercept/tests/test_http_client.py'. > Hint: make sure your test modules/packages have valid Python names. > Traceback: > /usr/lib/python3.11/importlib/__init__.py:126: in import_module > return _bootstrap._gcd_import(name[level:], package, level) > wsgi_intercept/tests/test_http_client.py:1: in > import py.test > E ModuleNotFoundError: No module named 'py.test'; 'py' is not a package > ERROR collecting wsgi_intercept/tests/test_httplib2.py > > ImportError while importing test module > '/<>/wsgi_intercept/tests/test_httplib2.py'. > Hint: make sure your test modules/packages have valid Python names. > Traceback: > /usr/lib/python3.11/importlib/__init__.py:126: in import_module > return _bootstrap._gcd_import(name[level:], package, level) > wsgi_intercept/tests/test_httplib2.py:1: in > import py.test > E ModuleNotFoundError: No module named 'py.test'; 'py' is not a package > __ ERROR collecting wsgi_intercept/tests/test_interceptor.py > ___ > ImportError while importing test module > '/<>/wsgi_intercept/tests/test_interceptor.py'. > Hint: make sure your test modules/packages have valid Python names. > Traceback: > /usr/lib/python3.11/importlib/__init__.py:126: in import_module > return _bootstrap._gcd_import(name[level:], package, level) > wsgi_intercept/tests/test_interceptor.py:10: in > import py.test > E ModuleNotFoundError: No module named 'py.test'; 'py' is not a package > ERROR collecting wsgi_intercept/tests/test_requests.py > > ImportError while importing test module > '/<>/wsgi_intercept/tests/test_requests.py'. > Hint: make sure your test modules/packages have valid Python names. > Traceback: > /usr/lib/python3.11/importlib/__init__.py:126: in import_module > return _bootstrap._gcd_import(name[level:], package, level) > wsgi_intercept/tests/test_requests.py:2: in > import py.test > E ModuleNotFoundError: No module named 'py.test'; 'py' is not a package > ERROR collecting wsgi_intercept/tests/test_response_headers.py > > ImportError while importing test module > '/<>/wsgi_intercept/tests/test_response_headers.py'. > Hint: make sure your test modules/packages have valid Python names. > Traceback: > /usr/lib/python3.11/importlib/__init__.py:126: in import_module > return _bootstrap._gcd_import(name[level:], package, level) > wsgi_intercept/tests/test_response_headers.py:11: in > import py.test > E ModuleNotFoundError: No module named 'py.test'; 'py' is not a package > _ ERROR collecting wsgi_intercept/tests/test_urllib.py > _ > ImportError while importing test module > '/<>/wsgi_intercept/tests/test_urllib.py'. > Hint: make sure your test modules/packages have valid Python names. > Traceback: > /usr/lib/python3.11/importlib/__init__.py:126: in import_module > return _bootstrap._gcd_import(name[level:], package, level) > wsgi_intercept/tests/test_urllib.py:2: in > import py.test > E ModuleNotFoundError: No module named 'py.test'; 'py' is not a package > ERROR collecting wsgi_intercept/tests/test_urllib3.py > _ > ImportError while importing test module > '/<>/wsgi_intercept/tests/te
Bug#1042350: mate-system-monitor: FTBFS: make[3]: *** [Makefile:1069: org.mate.mate-system-monitor.policy] Error 1
Source: mate-system-monitor Version: 1.26.0-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230726 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[3]: Entering directory '/<>' > /usr/bin/msgfmt --desktop --keyword= --keyword=Name --keyword=Comment > --keyword=Keywords --template mate-system-monitor.desktop.in -d ./po -o > mate-system-monitor.desktop > /usr/bin/msgfmt --xml --template mate-system-monitor.appdata.xml.in -d ./po > -o mate-system-monitor.appdata.xml > sed -e "s|\@pkglibexecdir\@|/usr/lib/mate-system-monitor|" > org.mate.mate-system-monitor.policy.in.in > > org.mate.mate-system-monitor.policy.in > /usr/bin/msgfmt --xml --template org.mate.mate-system-monitor.policy.in -d > ./po -o org.mate.mate-system-monitor.policy > /usr/bin/msgfmt: cannot locate ITS rules for > org.mate.mate-system-monitor.policy.in > make[3]: *** [Makefile:1069: org.mate.mate-system-monitor.policy] Error 1 The full build log is available from: http://qa-logs.debian.net/2023/07/26/mate-system-monitor_1.26.0-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230726;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230726=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime.
Bug#1042342: yarl: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13
Source: yarl Version: 1.8.2-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230726 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > cd docs && \ > PYTHONPATH=/<> http_proxy='http://127.0.0.1:9/' > https_proxy='https://127.0.0.1:9/' \ > python3 -m sphinx -N -E -T -b html . /<>/.pybuild/docs/html/ > Running Sphinx v5.3.0 > making output directory... done > building [mo]: targets for 0 po files that are out of date > building [html]: targets for 2 source files that are out of date > updating environment: [new config] 2 added, 0 changed, 0 removed > reading sources... [ 50%] api > reading sources... [100%] index > > looking for now-outdated files... none found > pickling environment... done > checking consistency... done > preparing documents... done > writing output... [ 50%] api > writing output... [100%] index > > /<>/docs/api.rst:1: WARNING: py:class reference target not > found: multidict.MultiDictProxy > /<>/docs/api.rst:5: WARNING: py:class reference target not > found: collections.abc.Mapping > /<>/docs/api.rst:5: WARNING: py:class reference target not > found: multidict.MultiDict > /<>/docs/api.rst:10: WARNING: py:class reference target not > found: collections.abc.Mapping > /<>/docs/api.rst:10: WARNING: py:class reference target not > found: multidict.MultiDict > /<>/docs/api.rst:1: WARNING: py:func reference target not found: > functools.lru_cache > /<>/docs/api.rst:943: WARNING: py:mod reference target not > found: urllib.parse > /<>/docs/api.rst:946: WARNING: py:mod reference target not > found: pathlib > /<>/docs/index.rst:118: WARNING: py:mod reference target not > found: multidict > generating indices... genindex py-modindex done > highlighting module code... [100%] yarl._url > > writing additional pages... search done > copying static files... done > copying extra files... done > dumping search index in English (code: en)... done > dumping object inventory... done > build succeeded, 9 warnings. > > The HTML pages are in ../.pybuild/docs/html. > rm -rf /<>/.pybuild/docs/html/.doctrees > make[1]: Leaving directory '/<>' >dh_auto_build -O--buildsystem=pybuild -Npython-yarl-doc > I: pybuild pybuild:307: cython3 yarl/_quoting_c.pyx > I: pybuild base:240: /usr/bin/python3 setup.py build > /usr/lib/python3/dist-packages/setuptools/config/setupcfg.py:293: > _DeprecatedConfig: Deprecated config in `setup.cfg` > !! > > > > The license_file parameter is deprecated, use license_files instead. > > By 2023-Oct-30, you need to update your project and remove deprecated > calls > or your builds will no longer be supported. > > See > https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for > details. > > > > !! > parsed = self.parsers.get(option_name, lambda x: x)(value) > ** > * Accelerated build * > ** > running build > running build_py > creating /<>/.pybuild/cpython3_3.11_yarl/build/yarl > copying yarl/_quoting.py -> > /<>/.pybuild/cpython3_3.11_yarl/build/yarl > copying yarl/__init__.py -> > /<>/.pybuild/cpython3_3.11_yarl/build/yarl > copying yarl/_quoting_py.py -> > /<>/.pybuild/cpython3_3.11_yarl/build/yarl > copying yarl/_url.py -> > /<>/.pybuild/cpython3_3.11_yarl/build/yarl > running egg_info > writing yarl.egg-info/PKG-INFO > writing dependency_links to yarl.egg-info/dependency_links.txt > writing requirements to yarl.egg-info/requires.txt > writing top-level names to yarl.egg-info/top_level.txt > reading manifest file 'yarl.egg-info/SOURCES.txt' > reading manifest template 'MANIFEST.in' > warning: no previously-included files matching '*.cache' found anywhere in > distribution > warning: no previously-included files found matching 'yarl/*.html' > warning: no previously-included files found matching 'yarl/*.so' > warning: no previously-included files found matching 'yarl/*.pyd' > no previously-included directories found matching 'docs/_build' > adding license file 'LICENSE' > writing manifest file 'yarl.egg-info/SOURCES.txt' > copying yarl/__init__.pyi -> > /<>/.pybuild/cpython3_3.11_yarl/build/yarl > copying yarl/_quoting_c.pyi -> > /<>/.pybuild/cpython3_3.11_y
Bug#1042346: rust-versionize-derive: FTBFS: dh_auto_test: error: /usr/share/cargo/bin/cargo test --all returned exit code 101
Source: rust-versionize-derive
Version: 0.1.4-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230726 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_test -- test --all
> debian cargo wrapper: options, profiles, parallel: ['parallel=8'] [] ['-j8']
> debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu,
> x86_64-linux-gnu
> debian cargo wrapper: running subprocess (['env', 'RUST_BACKTRACE=1',
> '/usr/bin/cargo', '-Zavoid-dev-deps', 'test', '--verbose', '--verbose',
> '-j8', '--target', 'x86_64-unknown-linux-gnu', '--all'],) {}
>Compiling proc-macro2 v1.0.65
>Compiling quote v1.0.30
>Compiling unicode-ident v1.0.0
> Running `CARGO=/usr/bin/cargo CARGO_CRATE_NAME=build_script_build
> CARGO_MANIFEST_DIR=/<>/debian/cargo_registry/quote-1.0.30
> CARGO_PKG_AUTHORS='David Tolnay '
> CARGO_PKG_DESCRIPTION='Quasi-quoting macro quote'\!'(...)'
> CARGO_PKG_HOMEPAGE='' CARGO_PKG_LICENSE='MIT OR Apache-2.0'
> CARGO_PKG_LICENSE_FILE='' CARGO_PKG_NAME=quote
> CARGO_PKG_REPOSITORY='https://github.com/dtolnay/quote'
> CARGO_PKG_RUST_VERSION=1.31 CARGO_PKG_VERSION=1.0.30
> CARGO_PKG_VERSION_MAJOR=1 CARGO_PKG_VERSION_MINOR=0
> CARGO_PKG_VERSION_PATCH=30 CARGO_PKG_VERSION_PRE=''
> LD_LIBRARY_PATH='/<>/target/debug/deps:/usr/lib' rustc
> --crate-name build_script_build --edition=2018
> /<>/debian/cargo_registry/quote-1.0.30/build.rs
> --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat
> --crate-type bin --emit=dep-info,link -C embed-bitcode=no -C debuginfo=2
> --cfg 'feature="default"' --cfg 'feature="proc-macro"' -C
> metadata=7a34db8af5b2571c -C extra-filename=-7a34db8af5b2571c --out-dir
> /<>/target/debug/build/quote-7a34db8af5b2571c -L
> dependency=/<>/target/debug/deps --cap-lints warn`
> Running `CARGO=/usr/bin/cargo CARGO_CRATE_NAME=unicode_ident
> CARGO_MANIFEST_DIR=/<>/debian/cargo_registry/unicode-ident-1.0.0
> CARGO_PKG_AUTHORS='David Tolnay '
> CARGO_PKG_DESCRIPTION='Determine whether characters have the XID_Start or
> XID_Continue properties according to Unicode Standard Annex #31'
> CARGO_PKG_HOMEPAGE='' CARGO_PKG_LICENSE='MIT OR Apache-2.0'
> CARGO_PKG_LICENSE_FILE='' CARGO_PKG_NAME=unicode-ident
> CARGO_PKG_REPOSITORY='https://github.com/dtolnay/unicode-ident'
> CARGO_PKG_RUST_VERSION=1.31 CARGO_PKG_VERSION=1.0.0 CARGO_PKG_VERSION_MAJOR=1
> CARGO_PKG_VERSION_MINOR=0 CARGO_PKG_VERSION_PATCH=0 CARGO_PKG_VERSION_PRE=''
> LD_LIBRARY_PATH='/<>/target/debug/deps:/usr/lib' rustc
> --crate-name unicode_ident --edition=2018
> /<>/debian/cargo_registry/unicode-ident-1.0.0/src/lib.rs
> --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat
> --crate-type lib --emit=dep-info,metadata,link -C embed-bitcode=no -C
> debuginfo=2 -C metadata=e2db5faa88c7ef07 -C extra-filename=-e2db5faa88c7ef07
> --out-dir /<>/target/debug/deps -L
> dependency=/<>/target/debug/deps --cap-lints warn`
> Running `CARGO=/usr/bin/cargo CARGO_CRATE_NAME=build_script_build
> CARGO_MANIFEST_DIR=/<>/debian/cargo_registry/proc-macro2-1.0.65
> CARGO_PKG_AUTHORS='David Tolnay :Alex Crichton
> ' CARGO_PKG_DESCRIPTION='A substitute implementation
> of the compiler'\''s `proc_macro` API to decouple token-based libraries from
> the procedural macro use case.' CARGO_PKG_HOMEPAGE='' CARGO_PKG_LICENSE='MIT
> OR Apache-2.0' CARGO_PKG_LICENSE_FILE='' CARGO_PKG_NAME=proc-macro2
> CARGO_PKG_REPOSITORY='https://github.com/dtolnay/proc-macro2'
> CARGO_PKG_RUST_VERSION=1.31 CARGO_PKG_VERSION=1.0.65
> CARGO_PKG_VERSION_MAJOR=1 CARGO_PKG_VERSION_MINOR=0
> CARGO_PKG_VERSION_PATCH=65 CARGO_PKG_VERSION_PRE=''
> LD_LIBRARY_PATH='/<>/target/debug/deps:/usr/lib' rustc
> --crate-name build_script_build --edition=2018
> /<>/debian/cargo_registry/proc-macro2-1.0.65/build.rs
> --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat
> --crate-type bin --emit=dep-info,link -C embed-bitcode=no -C debuginfo=2
> --cfg 'feature="default"' --cfg 'feature="proc-macro"' -C
> metadata=f3e892f69b1638b3 -C extra-filename=-f3e892f69b1638b3 --out-dir
> /<>/target/debug/build/proc-macro2-f3e892f69b1638b3 -L
> dependency=/<>/target/debug/deps --cap-lints warn`
> Running
> `/<>/target/debug/build/quote-7a34db8af5b2571c/build-script-build`
> [quote 1.0.30] cargo:rerun-if-changed=build.rs
> Running
> `/<>/target/debug/build/proc-macro2-f3e892f69b1638b3/build-script-build`
>
Bug#1042345: python-w3lib: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13
Source: python-w3lib
Version: 2.1.1-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230726 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules binary
> dh binary --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:240: python3.11 setup.py config
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:240: /usr/bin/python3 setup.py build
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.11_w3lib/build/w3lib
> copying w3lib/url.py ->
> /<>/.pybuild/cpython3_3.11_w3lib/build/w3lib
> copying w3lib/util.py ->
> /<>/.pybuild/cpython3_3.11_w3lib/build/w3lib
> copying w3lib/_infra.py ->
> /<>/.pybuild/cpython3_3.11_w3lib/build/w3lib
> copying w3lib/__init__.py ->
> /<>/.pybuild/cpython3_3.11_w3lib/build/w3lib
> copying w3lib/html.py ->
> /<>/.pybuild/cpython3_3.11_w3lib/build/w3lib
> copying w3lib/_types.py ->
> /<>/.pybuild/cpython3_3.11_w3lib/build/w3lib
> copying w3lib/http.py ->
> /<>/.pybuild/cpython3_3.11_w3lib/build/w3lib
> copying w3lib/encoding.py ->
> /<>/.pybuild/cpython3_3.11_w3lib/build/w3lib
> copying w3lib/_url.py ->
> /<>/.pybuild/cpython3_3.11_w3lib/build/w3lib
> running egg_info
> writing w3lib.egg-info/PKG-INFO
> writing dependency_links to w3lib.egg-info/dependency_links.txt
> writing top-level names to w3lib.egg-info/top_level.txt
> writing manifest file 'w3lib.egg-info/SOURCES.txt'
> reading manifest file 'w3lib.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> warning: no files found matching '*.txt' under directory 'tests'
> adding license file 'LICENSE'
> writing manifest file 'w3lib.egg-info/SOURCES.txt'
> copying w3lib/py.typed ->
> /<>/.pybuild/cpython3_3.11_w3lib/build/w3lib
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:240: cd /<>/.pybuild/cpython3_3.11_w3lib/build;
> python3.11 -m pytest tests
> = test session starts
> ==
> platform linux -- Python 3.11.4, pytest-7.4.0, pluggy-1.2.0
> rootdir: /<>
> configfile: pytest.ini
> collected 314 items
>
> tests/test_encoding.py ... [
> 6%]
> tests/test_html.py . [
> 22%]
> .. [
> 23%]
> tests/test_http.py ... [
> 25%]
> tests/test_url.py x...xxxx..x.xx [
> 42%]
> xxx.Fx...xx..xxxFxxx.x.. [
> 65%]
> xxx..xx....xx... [
> 88%]
> .. [
> 98%]
> tests/test_util.py .
> [100%]
>
> === FAILURES
> ===
> _
> test_safe_url_string_url[https://"%;<=>@[]^`{|}\x7f:"%;<=>@[]^`{|}\x7f:@example.com-https://%22%25%3B%3C%3D%3E%40%5B%5D%5E%60%7B%7C%7D%7F:%22%25%3b%3c%3d%3e%40%5b%5d%5e%60%7b%7c%7d%7f...@example.com]
> _
>
> url = 'https://"%;<=>@[]^`{|}\x7f:"%;<=>@[]^`{|}\x7f:@example.com'
> output =
> 'https://%22%25%3B%3C%3D%3E%40%5B%5D%5E%60%7B%7C%7D%7F:%22%25%3b%3c%3d%3e%40%5b%5d%5e%60%7b%7c%7d%7f...@example.com'
>
> @pytest.mark.parametrize(
> "url,output",
> tuple(
> case
> if case[0] not in KNOWN_SAFE_URL_STRING_URL_ISSUES
> else pytest.param(*case, marks=pytest.mark.xfail(strict=True))
> for case in SAFE_URL_URL_CASES
> ),
> )
> def test_safe_url_string_url(
> url: StrOrBytes, output: Union[str, Type[Exception]]
> ) -> None:
> > _test_safe_url_string(url, output=output)
>
> tests/test_url.py:435:
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> _
> tests/test_url.py:343: in _test_safe_url_string
> return _test_safe_url_func(
> tests/test_url.py:332: in _test_safe_url_func
> actual = func(url, **kwargs)
> w3lib/url.py:142: in safe_url_string
> parts = urlsplit(_strip(decoded))
> /usr/lib/python3.11/urllib/parse.py:500: in urlsplit
> _check_bracketed
Bug#1042344: safeclib: FTBFS: dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2
Source: safeclib Version: 3.7.1-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230726 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[5]: Entering directory '/<>/tests' > PASS: t_memcpy_s > PASS: t_strcat_s > PASS: t_memmove_s > PASS: t_memset_s > PASS: t_strncat_s > PASS: t_strncpy_s > PASS: t_sprintf_s > PASS: t_strcpy_s > PASS: t_vsprintf_s > PASS: t_strnlen_s > PASS: t_strerror_s > PASS: t_strtok_s > PASS: t_strerrorlen_s > PASS: t_mbstowcs_s > PASS: t_sscanf_s > PASS: t_mbsrtowcs_s > PASS: t_wcsrtombs_s > PASS: t_wcstombs_s > PASS: t_wcrtomb_s > PASS: t_wctomb_s > PASS: t_wcsnlen_s > PASS: t_wcscpy_s > PASS: t_wcsncpy_s > PASS: t_wcscat_s > PASS: t_wcsncat_s > PASS: t_wmemcpy_s > PASS: t_wmemmove_s > PASS: t_wcstok_s > FAIL: t_vswprintf_s > PASS: t_fwprintf_s > PASS: t_swprintf_s > PASS: t_vfwprintf_s > PASS: t_swscanf_s > PASS: t_vwscanf_s > PASS: t_vswscanf_s > PASS: t_fwscanf_s > PASS: t_vfwscanf_s > PASS: t_wscanf_s > PASS: t_wmemcmp_s > PASS: t_wcscmp_s > PASS: t_wcsncmp_s > PASS: t_wcsicmp_s > PASS: t_wcsnatcmp_s > PASS: t_wcsset_s > PASS: t_wcsstr_s > PASS: t_wcsnset_s > PASS: t_wcscoll_s > PASS: t_wcslwr_s > PASS: t_wcsupr_s > PASS: t_towupper > PASS: t_towlower > PASS: t_towfc_s > PASS: t_memcpy32_s > PASS: t_memcpy16_s > PASS: t_wcsnorm_s > PASS: t_memcmp32_s > PASS: t_memcmp16_s > PASS: t_memcmp_s > PASS: t_memmove32_s > PASS: t_memmove16_s > PASS: t_memzero_s > PASS: t_memset16_s > PASS: t_memzero32_s > PASS: t_memset32_s > PASS: t_memzero16_s > PASS: t_stpncpy_s > PASS: t_stpcpy_s > PASS: t_strcasecmp_s > PASS: t_strcasestr_s > PASS: t_strcmp_s > PASS: t_strcpyfldin_s > PASS: t_strcmpfld_s > PASS: t_strcpyfldout_s > PASS: t_strcpyfld_s > PASS: t_strcspn_s > PASS: t_strfirstchar_s > PASS: t_strfirstdiff_s > PASS: t_strfirstsame_s > PASS: t_strisascii_s > PASS: t_strisalphanumeric_s > PASS: t_strisdigit_s > PASS: t_strishex_s > PASS: t_strismixed_s > PASS: t_strislowercase_s > PASS: t_strisuppercase_s > PASS: t_strlastdiff_s > PASS: t_strlastchar_s > PASS: t_strispassword_s > PASS: t_strlastsame_s > PASS: t_strljustify_s > PASS: t_strnatcmp_s > PASS: t_strnterminate_s > PASS: t_strpbrk_s > PASS: t_strremovews_s > PASS: t_strprefix_s > PASS: t_strspn_s > PASS: t_strchr_s > PASS: t_memchr_s > PASS: t_strrchr_s > PASS: t_strstr_s > PASS: t_memrchr_s > PASS: t_strtolowercase_s > PASS: t_strtouppercase_s > PASS: t_strnset_s > PASS: t_strset_s > PASS: t_strzero_s > PASS: t_strcoll_s > PASS: t_timingsafe_memcmp > PASS: t_timingsafe_bcmp > PASS: t_memccpy_s > PASS: t_fprintf_s > PASS: t_vprintf_s > PASS: t_tmpfile_s > PASS: t_printf_s > PASS: t_vfprintf_s > PASS: t_gets_s > PASS: t_fopen_s > PASS: t_freopen_s > PASS: t_ctime_s > PASS: t_asctime_s > PASS: t_gmtime_s > PASS: t_getenv_s > PASS: t_localtime_s > PASS: t_bsearch_s > PASS: t_qsort_s > PASS: t_wcsfc_s > >Safe C Library 3.7.1: tests/test-suite.log > > > # TOTAL: 126 > # PASS: 125 > # SKIP: 0 > # XFAIL: 0 > # FAIL: 1 > # XPASS: 0 > # ERROR: 0 > > .. contents:: :depth: 2 > > FAIL: t_vswprintf_s > === > > FAIL t_vswprintf_s (exit status: 2) > > > Testsuite summary for Safe C Library 3.7.1 > > # TOTAL: 126 > # PASS: 125 > # SKIP: 0 > # XFAIL: 0 > # FAIL: 1 > # XPASS: 0 > # ERROR: 0 > > See tests/test-suite.log > Please report to https://github.com/rurban/safeclib/issues > > make[5]: *** [Makefile:3148: test-suite.log] Error 1 > make[5]: Leaving directory '/<>/tests' > make[4]: *** [Makefile:3256: check-TESTS] Error 2 > make[4]: Leaving directory '/<>/tests' > make[3]: *** [Makefile:4267: check-am] Error 2 > make[3]: Leaving directory '/<>/tests' > make[2]: *** [Makefile:1185: check-recursive] Error 1 > make[2]: Leaving directory '/<>' > make[1]: *** [Makefile:1488: check] Error 2 > make[1]: Leaving directory '/<>' > dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 > returned exit code 2 T
Bug#1042343: binutils-msp430: FTBFS: make[1]: *** [debian/rules:36: override_dh_auto_build] Error 1
Source: binutils-msp430 Version: 2.40.50~ti1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230726 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > patch -p1 < debian/patches/fix-spelling-error-in-binary > can't find file to patch at input line 8 > Perhaps you used the wrong -p or --strip option? > The text leading up to this was: > -- > |Description: fix typos in source files. > |Author: Thiago Marques Siqueira > |Last-Update: 2023-06-29 > |Index: binutils-msp430-2.40.50/binutils-2.40.50/binutils/readelf.c > |=== > |--- binutils-msp430-2.40.50.orig/binutils-2.40.50/binutils/readelf.c > |+++ binutils-msp430-2.40.50/binutils-2.40.50/binutils/readelf.c > -- > File to patch: > Skip this patch? [y] > Skipping patch. > 2 out of 2 hunks ignored > make[1]: *** [debian/rules:36: override_dh_auto_build] Error 1 The full build log is available from: http://qa-logs.debian.net/2023/07/26/binutils-msp430_2.40.50~ti1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230726;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230726=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime.
Bug#1042341: gstreamer-editing-services1.0: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 MESON_TESTTHREADS=8 meson test returned exit code 1
Source: gstreamer-editing-services1.0 Version: 1.22.4-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230726 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_auto_test > cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 MESON_TESTTHREADS=8 meson test > ninja: Entering directory `/<>/obj-x86_64-linux-gnu' > ninja: no work to do. > 1/23 ges_backgroundsource OK 0.72s > 2/23 ges_uriclip OK 0.92s > 3/23 ges_assetOK 1.00s > 4/23 ges_timelineedition OK 1.17s > 5/23 ges_effects OK 1.22s > 6/23 ges_basicOK 1.37s > 7/23 ges_titles OK 0.72s > 8/23 ges_transition OK 0.68s > 9/23 ges_overlays OK 0.72s > 10/23 ges_trackOK 0.52s > 11/23 ges_layerOK 2.08s > 12/23 ges_tempochange OK 0.51s > 13/23 ges_negative OK 0.52s > 14/23 ges_groupOK 1.07s > 15/23 ges_project OK 0.98s > 16/23 ges_clip OK 2.90s > 17/23 ges_markerlist OK 0.99s > 18/23 ges_mixers OK 8.82s > 19/23 nle_nlecomposition OK 10.82s > 20/23 nle_simple OK 11.96s > 21/23 nle_complex OK 29.76s > 22/23 nle_nleoperation OK 67.05s > 23/23 nle_tempochange FAIL80.45s exit status 2 > >>> GST_STATE_IGNORE_ELEMENTS='' MALLOC_PERTURB_=187 CK_DEFAULT_TIMEOUT=20 > >>> GST_REGISTRY=/<>/obj-x86_64-linux-gnu/tests/check/nle_tempochange.registry > >>> > >>> GST_PLUGIN_PATH_1_0=/<>/obj-x86_64-linux-gnu:/usr/lib/x86_64-linux-gnu/gstreamer-1.0:/usr/lib/x86_64-linux-gnu/gstreamer-1.0:/usr/lib/x86_64-linux-gnu/gstreamer-1.0 > >>> GST_PLUGIN_SYSTEM_PATH_1_0='' > >>> LD_LIBRARY_PATH=/<>/obj-x86_64-linux-gnu/ges > >>> /<>/obj-x86_64-linux-gnu/tests/check/nle_tempochange > > > Ok: 22 > Expected Fail: 0 > Fail: 1 > Unexpected Pass:0 > Skipped:0 > Timeout:0 > > Full log written to > /<>/obj-x86_64-linux-gnu/meson-logs/testlog.txt > cd obj-x86_64-linux-gnu && tail -v -n \+0 meson-logs/testlog.txt > ==> meson-logs/testlog.txt <== > Log of Meson test suite run on 2023-07-26T19:19:52.948039 > > Inherited environment: SCHROOT_GID=1001 DEB_HOST_MULTIARCH=x86_64-linux-gnu > LC_ALL=C.UTF-8 DEB_HOST_GNU_SYSTEM=linux-gnu > DEB_BUILD_GNU_TYPE=x86_64-linux-gnu DEB_LDFLAGS_MAINT_APPEND='-Wl,-O1 > -Wl,-z,defs' DEB_TARGET_ARCH_LIBC=gnu FFLAGS='-g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong' > DEB_BUILD_ARCH_ENDIAN=little DEB_BUILD_GNU_SYSTEM=linux-gnu > DEB_BUILD_ARCH_BITS=64 DEB_BUILD_OPTIONS=parallel=8 DEB_HOST_ARCH=amd64 > DEB_TARGET_ARCH_ENDIAN=little SOURCE_DATE_EPOCH=1687992837 OBJCXXFLAGS='-g > -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security' DEB_HOST_ARCH_BITS=64 LANG=C.UTF-8 MAKEFLAGS=w > SCHROOT_GROUP=user42 DEB_TARGET_ARCH=amd64 DH_INTERNAL_OPTIONS='' > DEB_HOST_GNU_CPU=x86_64 DEB_BUILD_ARCH_LIBC=gnu MFLAGS=-w > DEB_TARGET_ARCH_BITS=64 ASFLAGS='' DEB_BUILD_ARCH_CPU=amd64 > LC_COLLATE=C.UTF-8 SCHROOT_ALIAS_NAME=unstable DEB_HOST_ARCH_OS=linux > SHELL=/bin/sh FCFLAGS='-g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong' DEB_HOST_ARCH_CPU=amd64 SCHROOT_USER=user42 > PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games > DEB_BUILD_ARCH_ABI=base DEB_BUILD_ARCH=amd64 DEB_HOST_ARCH_LIBC=gnu > SCHROOT_SESSION_ID=sid-amd64-sbuild-82bac9e4-214c-4219-ab42-d2502bd42ada > GCJFLAGS='-g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong' DEB_TARGET_ARCH_CPU=amd64 > DEB_HOST_GNU_TYPE=x86_64-linux-gnu DEB_BUILD_ARCH_OS=linux LOGNAME=user42 > CPPFLAGS='-Wdate-time -D_FORTIFY_SOURCE=2' > DEB_TARGET_MULTIARCH=x86_64-linux-gnu DEB_BUILD_GNU_CPU=x86_64 > DEB_TARGET_ARCH_OS=linux USER=user42 DEB_HOST_ARCH_ABI=base > DEB_BUILD_MULTIARCH=x86_64-linux-gnu LDFLAGS='-Wl,-z,relro -Wl,-z,now -Wl,-O1 > -Wl,-z,defs' DEB_TARGET_GNU_TYPE=x86_64-linux-gnu DEB_TARGET_ARCH_ABI=base > CFLAGS='-g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong > -Wformat -Werror=format-security' SCHROOT_UID=1001 > SCHROOT_COMMAND='dpkg-buildpackage --sanitize-env -
Bug#1042340: xxsds-dynamic: FTBFS: make: *** [debian/rules:9: binary] Error 2
Source: xxsds-dynamic Version: 1.0~alpha.1+git20210426.548c6f7-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230726 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules binary > dh binary >dh_update_autotools_config >dh_autoreconf >dh_auto_configure > cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr > -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc > -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON > -DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF > -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON > -DFETCHCONTENT_FULLY_DISCONNECTED=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run > -DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=ON "-GUnix Makefiles" > -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu .. > CMake Deprecation Warning at CMakeLists.txt:1 (cmake_minimum_required): > Compatibility with CMake < 3.5 will be removed from a future version of > CMake. > > Update the VERSION argument value or use a ... suffix to tell > CMake that the project does not need compatibility with older versions. > > > -- The C compiler identification is GNU 13.1.0 > -- The CXX compiler identification is GNU 13.1.0 > -- Detecting C compiler ABI info > -- Detecting C compiler ABI info - done > -- Check for working C compiler: /usr/bin/cc - skipped > -- Detecting C compile features > -- Detecting C compile features - done > -- Detecting CXX compiler ABI info > -- Detecting CXX compiler ABI info - done > -- Check for working CXX compiler: /usr/bin/c++ - skipped > -- Detecting CXX compile features > -- Detecting CXX compile features - done > Building in None mode > -- Configuring done (0.4s) > CMake Error at CMakeLists.txt:49 (add_dependencies): > The dependency target "hopscotch_map" of target "debug" does not exist. > > > CMake Error at CMakeLists.txt:50 (add_dependencies): > The dependency target "hopscotch_map" of target "rle_lz77_v1" does not > exist. > > > CMake Error at CMakeLists.txt:51 (add_dependencies): > The dependency target "hopscotch_map" of target "rle_lz77_v2" does not > exist. > > > CMake Error at CMakeLists.txt:52 (add_dependencies): > The dependency target "hopscotch_map" of target "h0_lz77" does not exist. > > > CMake Error at CMakeLists.txt:53 (add_dependencies): > The dependency target "hopscotch_map" of target "rle_bwt" does not exist. > > > CMake Error at CMakeLists.txt:54 (add_dependencies): > The dependency target "hopscotch_map" of target "cw-bwt" does not exist. > > > CMake Error at CMakeLists.txt:55 (add_dependencies): > The dependency target "hopscotch_map" of target "benchmark" does not exist. > > > CMake Error at CMakeLists.txt:56 (add_dependencies): > The dependency target "hopscotch_map" of target "wm_string" does not exist. > > > -- Generating done (0.0s) > CMake Warning: > Manually-specified variables were not used by the project: > > CMAKE_EXPORT_NO_PACKAGE_REGISTRY > CMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY > CMAKE_FIND_USE_PACKAGE_REGISTRY > CMAKE_INSTALL_LIBDIR > CMAKE_INSTALL_LOCALSTATEDIR > CMAKE_INSTALL_RUNSTATEDIR > CMAKE_INSTALL_SYSCONFDIR > FETCHCONTENT_FULLY_DISCONNECTED > > > CMake Generate step failed. Build files cannot be regenerated correctly. > cd obj-x86_64-linux-gnu && tail -v -n \+0 CMakeCache.txt > ==> CMakeCache.txt <== > # This is the CMakeCache file. > # For build in directory: /<>/obj-x86_64-linux-gnu > # It was generated by CMake: /usr/bin/cmake > # You can edit this file to change values found and used by cmake. > # If you do not want to change any of the values, simply exit the editor. > # If you do want to change a value, simply edit, save, and exit the editor. > # The syntax for the file is as follows: > # KEY:TYPE=VALUE > # KEY is the name of a variable in the cache. > # TYPE is a hint to GUIs for the type of VALUE, DO NOT EDIT TYPE!. > # VALUE is the current value for the KEY. > > > # EXTERNAL cache entries > > > //Path to a program. > CMAKE_ADDR2LINE:FILEPATH=/usr/bin/addr2line > > //Path to a program. > CMAKE_AR:FILEPATH=/usr/bin/ar > > //Choose the type of build, options are: None Debug Release RelWithDebInfo > // MinSizeRel ... > CMAKE_BUILD_TYPE:STRING=None > > //Enable/Disable
Bug#1042338: dnf: FTBFS: dh_auto_test: error: cd build && make -j8 test ARGS\+=--verbose ARGS\+=-j8 ARGS=-VV returned exit code 2
Source: dnf Version: 4.14.0-4 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230726 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[2]: Entering directory '/<>/build' > Running tests... > /usr/bin/ctest --force-new-ctest-process -VV > UpdateCTestConfiguration from :/<>/build/DartConfiguration.tcl > UpdateCTestConfiguration from :/<>/build/DartConfiguration.tcl > Test project /<>/build > Constructing a list of tests > Done constructing a list of tests > Updating test list for fixtures > Added 0 tests to meet fixture requirements > Checking test dependency graph... > Checking test dependency graph end > test 1 > Start 1: test > > 1: Test command: /usr/bin/python3 "-m" "unittest" "discover" "-s" "tests" > "-t" "/<>" > 1: Working Directory: /<> > 1: Environment variables: > 1: PYTHONPATH=/<>/ > 1: ASAN_OPTIONS=verify_asan_link_order=0,detect_leaks=0 > 1: Test timeout computed to be: 1000 > 1: History database cannot be created, using in-memory database instead: > SQLite error on "/tmp/tests/history.sqlite": Open failed: unable to open > database file > 1: ..History database cannot be created, using in-memory database > instead: SQLite error on "/tmp/tests/history.sqlite": Open failed: unable to > open database file > 1: ...History database cannot be created, using in-memory database instead: > SQLite error on "/tmp/tests/history.sqlite": Open failed: unable to open > database file > 1: .History database cannot be created, using in-memory database instead: > SQLite error on "/tmp/tests/history.sqlite": Open failed: unable to open > database file > 1: .History database cannot be created, using in-memory database instead: > SQLite error on "/tmp/tests/history.sqlite": Open failed: unable to open > database file > 1: ...History database cannot be created, using in-memory database instead: > SQLite error on "/tmp/tests/history.sqlite": Open failed: unable to open > database file > 1: .History database cannot be created, using in-memory database instead: > SQLite error on "/tmp/tests/history.sqlite": Open failed: unable to open > database file > 1: .History database cannot be created, using in-memory database instead: > SQLite error on "/tmp/tests/history.sqlite": Open failed: unable to open > database file > 1: ..Package tour not installed, cannot downgrade it. > 1: Package tour not installed, cannot update it. > 1: ...History database cannot be created, using in-memory database > instead: SQLite error on "/tmp/tests/history.sqlite": Open failed: unable to > open database file > 1: > ... > 1/1 Test #1: test .***Exception: SegFault 4.09 > sec > History database cannot be created, using in-memory database instead: > SQLite error on "/tmp/tests/history.sqlite": Open failed: unable to open > database file > ..History database cannot be created, using in-memory database instead: > SQLite error on "/tmp/tests/history.sqlite": Open failed: unable to open > database file > ...History database cannot be created, using in-memory database instead: > SQLite error on "/tmp/tests/history.sqlite": Open failed: unable to open > database file > .History database cannot be created, using in-memory database instead: SQLite > error on "/tmp/tests/history.sqlite": Open failed: unable to open database > file > .History database cannot be created, using in-memory database instead: SQLite > error on "/tmp/tests/history.sqlite": Open failed: unable to open database > file > ...History database cannot be created, using in-memory database instead: > SQLite error on "/tmp/tests/history.sqlite": Open failed: unable to open > database file > .History database cannot be created, using in-memory database instead: SQLite > error on "/tmp/tests/history.sqlite": Open failed: unable to open database > file > .History database cannot be created, using in-memory database instead: SQLite > error on "/tmp/tests/history.sqlite": Open failed: unable to open database > file > ..Package tour not installed, cannot downgra
Bug#1042339: pyflakes: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13
Source: pyflakes Version: 2.5.0-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230726 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules binary > dh binary --with python3 --buildsystem=pybuild >dh_update_autotools_config -O--buildsystem=pybuild >dh_autoreconf -O--buildsystem=pybuild >dh_auto_configure -O--buildsystem=pybuild > I: pybuild base:240: python3.11 setup.py config > /usr/lib/python3/dist-packages/setuptools/config/setupcfg.py:293: > _DeprecatedConfig: Deprecated config in `setup.cfg` > !! > > > > The license_file parameter is deprecated, use license_files instead. > > By 2023-Oct-30, you need to update your project and remove deprecated > calls > or your builds will no longer be supported. > > See > https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for > details. > > > > !! > parsed = self.parsers.get(option_name, lambda x: x)(value) > running config >dh_auto_build -O--buildsystem=pybuild > I: pybuild base:240: /usr/bin/python3 setup.py build > /usr/lib/python3/dist-packages/setuptools/config/setupcfg.py:293: > _DeprecatedConfig: Deprecated config in `setup.cfg` > !! > > > > The license_file parameter is deprecated, use license_files instead. > > By 2023-Oct-30, you need to update your project and remove deprecated > calls > or your builds will no longer be supported. > > See > https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for > details. > > > > !! > parsed = self.parsers.get(option_name, lambda x: x)(value) > running build > running build_py > creating /<>/.pybuild/cpython3_3.11_pyflakes/build/pyflakes > copying pyflakes/__init__.py -> > /<>/.pybuild/cpython3_3.11_pyflakes/build/pyflakes > copying pyflakes/reporter.py -> > /<>/.pybuild/cpython3_3.11_pyflakes/build/pyflakes > copying pyflakes/api.py -> > /<>/.pybuild/cpython3_3.11_pyflakes/build/pyflakes > copying pyflakes/__main__.py -> > /<>/.pybuild/cpython3_3.11_pyflakes/build/pyflakes > copying pyflakes/messages.py -> > /<>/.pybuild/cpython3_3.11_pyflakes/build/pyflakes > copying pyflakes/checker.py -> > /<>/.pybuild/cpython3_3.11_pyflakes/build/pyflakes > creating > /<>/.pybuild/cpython3_3.11_pyflakes/build/pyflakes/scripts > copying pyflakes/scripts/__init__.py -> > /<>/.pybuild/cpython3_3.11_pyflakes/build/pyflakes/scripts > copying pyflakes/scripts/pyflakes.py -> > /<>/.pybuild/cpython3_3.11_pyflakes/build/pyflakes/scripts > creating /<>/.pybuild/cpython3_3.11_pyflakes/build/pyflakes/test > copying pyflakes/test/test_dict.py -> > /<>/.pybuild/cpython3_3.11_pyflakes/build/pyflakes/test > copying pyflakes/test/test_doctests.py -> > /<>/.pybuild/cpython3_3.11_pyflakes/build/pyflakes/test > copying pyflakes/test/test_imports.py -> > /<>/.pybuild/cpython3_3.11_pyflakes/build/pyflakes/test > copying pyflakes/test/__init__.py -> > /<>/.pybuild/cpython3_3.11_pyflakes/build/pyflakes/test > copying pyflakes/test/test_other.py -> > /<>/.pybuild/cpython3_3.11_pyflakes/build/pyflakes/test > copying pyflakes/test/test_builtin.py -> > /<>/.pybuild/cpython3_3.11_pyflakes/build/pyflakes/test > copying pyflakes/test/test_checker.py -> > /<>/.pybuild/cpython3_3.11_pyflakes/build/pyflakes/test > copying pyflakes/test/harness.py -> > /<>/.pybuild/cpython3_3.11_pyflakes/build/pyflakes/test > copying pyflakes/test/test_undefined_names.py -> > /<>/.pybuild/cpython3_3.11_pyflakes/build/pyflakes/test > copying pyflakes/test/test_code_segment.py -> > /<>/.pybuild/cpython3_3.11_pyflakes/build/pyflakes/test > copying pyflakes/test/test_match.py -> > /<>/.pybuild/cpython3_3.11_pyflakes/build/pyflakes/test > copying pyflakes/test/test_is_literal.py -> > /<>/.pybuild/cpython3_3.11_pyflakes/build/pyflakes/test > copying pyflakes/test/test_api.py -> > /<>/.pybuild/cpython3_3.11_pyflakes/build/pyflakes/test > copying pyflakes/test/test_type_annotations.py -> > /<>/.pybuild/cpython3_3.11_pyflake
Bug#1042337: gdnsd: FTBFS: dh_auto_test: error: make -j8 test "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2
Source: gdnsd Version: 3.8.1-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230726 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[4]: Entering directory '/<>/t' > Test data/outputs will be stored at /<>/t/testout > if test "x" != "x"; then \ > TOP_BUILDDIR=/<> TESTOUT_DIR=/<>/t/testout > TESTPORT_START=12345 /usr/bin/prove -v -f --norc -I. ./; \ > else \ > TOP_BUILDDIR=/<> TESTOUT_DIR=/<>/t/testout > TESTPORT_START=12345 /usr/bin/prove -v -f --norc -I. ./[0-9]*/*.t; \ > fi > ./001basic/001self.t > 1..4 > ok 1 - use _GDT; > ok 2 > ok 3 > ok 4 > ok > ./002simple/002noerr.t .. > 1..19 > ok 1 > ok 2 > ok 3 > ok 4 > ok 5 > ok 6 > ok 7 > ok 8 > ok 9 > ok 10 > ok 11 > ok 12 > ok 13 > ok 14 > ok 15 > ok 16 > ok 17 > ok 18 > ok 19 > ok > ./002simple/003simple_errs.t > 1..15 > ok 1 > ok 2 > ok 3 > ok 4 > ok 5 > ok 6 > ok 7 > ok 8 > ok 9 > ok 10 > ok 11 > ok 12 > ok 13 > ok 14 > ok 15 > ok > ./003complex/004delegations.t ... > 1..29 > ok 1 > ok 2 > ok 3 > ok 4 > ok 5 > ok 6 > ok 7 > ok 8 > ok 9 > ok 10 > ok 11 > ok 12 > ok 13 > ok 14 > ok 15 > ok 16 > ok 17 > ok 18 > ok 19 > ok 20 > ok 21 > ok 22 > ok 23 > ok 24 > ok 25 > ok 26 > ok 27 > ok 28 > ok 29 > ok > deprecated method; size() is an alias of "UDPsize()" at ./003complex/005big.t > line 8. > ./003complex/005big.t ... > 1..14 > ok 1 > ok 2 > ok 3 > ok 4 > ok 5 > ok 6 > ok 7 > ok 8 > ok 9 > ok 10 > ok 11 > ok 12 > ok 13 > ok 14 > ok > ./003complex/006limits.t > 1..23 > ok 1 > ok 2 > ok 3 > ok 4 > ok 5 > ok 6 > ok 7 > ok 8 > ok 9 > ok 10 > ok 11 > ok 12 > ok 13 > ok 14 > ok 15 > ok 16 > ok 17 > ok 18 > ok 19 > ok 20 > ok 21 > ok 22 > ok 23 > ok > ./003complex/007cname.t . > 1..12 > ok 1 > ok 2 > ok 3 > ok 4 > ok 5 > ok 6 > ok 7 > ok 8 > ok 9 > ok 10 > ok 11 > ok 12 > ok > deprecated method; size() is an alias of "UDPsize()" at > ./003complex/008compress.t line 72. > ./003complex/008compress.t .. > 1..4 > ok 1 > ok 2 > ok 3 - Packet size as expected > ok 4 > ok > > # Failed test at ./003complex/009broken.t line 46. > # Stats check: Stats check failed: tcp_close_c mismatch (hard-fail), wanted > 0, got 1 at /<>/t/_GDT.pm line 256. > > # Failed test at ./003complex/009broken.t line 53. > # Stats check: Stats check failed: tcp_close_c mismatch (hard-fail), wanted > 0, got 1 at /<>/t/_GDT.pm line 256. > > # Failed test at ./003complex/009broken.t line 63. > # Stats check: Stats check failed: tcp_close_c mismatch (hard-fail), wanted > 0, got 1 at /<>/t/_GDT.pm line 256. > > # Failed test at ./003complex/009broken.t line 68. > # Stats check: Stats check failed: tcp_close_c mismatch (hard-fail), wanted > 0, got 1 at /<>/t/_GDT.pm line 256. > deprecated method; size() is an alias of "UDPsize()" at > ./003complex/009broken.t line 84. > > # Failed test at ./003complex/009broken.t line 87. > # Stats check: Stats check failed: tcp_close_c mismatch (hard-fail), wanted > 0, got 1 at /<>/t/_GDT.pm line 256. > > # Failed test at ./003complex/009broken.t line 101. > # Stats check: Stats check failed: tcp_close_c mismatch (hard-fail), wanted > 0, got 1 at /<>/t/_GDT.pm line 256. > > # Failed test at ./003complex/009broken.t line 131. > # Stats check: Stats check failed: tcp_close_c mismatch (hard-fail), wanted > 0, got 1 at /<>/t/_GDT.pm line 256. > > # Failed test at ./003complex/009broken.t line 152. > # Stats check: Stats check failed: tcp_close_c mismatch (hard-fail), wanted > 0, got 1 at /<>/t/_GDT.pm line 256. > > # Failed test at ./003complex/009broken.t line 166. > # Stats check: Stats check failed: tcp_close_c mismatch (hard-fail), wanted > 0, got 1 at /<>/t/_GDT.pm line 256. > # Looks like you failed 9 tests of 15. > ./003complex/009broken.t > 1..15 > ok 1 > ok 2 > ok 3 > ok 4 > ok 5 > not ok 6 > not ok 7 > not ok 8 > not ok 9 > not ok 10 > not ok 11 > not ok 12 > not ok 13 > not ok 14 > ok 15 > Dubious, test returned 9 (wstat 2304, 0x900) > Failed 9/15 subtests
Bug#1042335: ros2-colcon-core: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13
Source: ros2-colcon-core Version: 0.12.1-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230726 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules binary > dh binary --buildsystem=pybuild >dh_update_autotools_config -O--buildsystem=pybuild >dh_autoreconf -O--buildsystem=pybuild >dh_auto_configure -O--buildsystem=pybuild > I: pybuild base:240: python3.11 setup.py config > /<>/setup.py:7: DeprecationWarning: pkg_resources is deprecated > as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html > from pkg_resources import parse_version > running config >dh_auto_build -O--buildsystem=pybuild > I: pybuild base:240: /usr/bin/python3 setup.py build > /<>/setup.py:7: DeprecationWarning: pkg_resources is deprecated > as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html > from pkg_resources import parse_version > running build > running build_py > creating /<>/.pybuild/cpython3_3.11/build/colcon_core > copying colcon_core/subprocess.py -> > /<>/.pybuild/cpython3_3.11/build/colcon_core > copying colcon_core/topological_order.py -> > /<>/.pybuild/cpython3_3.11/build/colcon_core > copying colcon_core/argument_default.py -> > /<>/.pybuild/cpython3_3.11/build/colcon_core > copying colcon_core/python_install_path.py -> > /<>/.pybuild/cpython3_3.11/build/colcon_core > copying colcon_core/logging.py -> > /<>/.pybuild/cpython3_3.11/build/colcon_core > copying colcon_core/command.py -> > /<>/.pybuild/cpython3_3.11/build/colcon_core > copying colcon_core/__init__.py -> > /<>/.pybuild/cpython3_3.11/build/colcon_core > copying colcon_core/entry_point.py -> > /<>/.pybuild/cpython3_3.11/build/colcon_core > copying colcon_core/environment_variable.py -> > /<>/.pybuild/cpython3_3.11/build/colcon_core > copying colcon_core/plugin_system.py -> > /<>/.pybuild/cpython3_3.11/build/colcon_core > copying colcon_core/package_decorator.py -> > /<>/.pybuild/cpython3_3.11/build/colcon_core > copying colcon_core/location.py -> > /<>/.pybuild/cpython3_3.11/build/colcon_core > copying colcon_core/package_descriptor.py -> > /<>/.pybuild/cpython3_3.11/build/colcon_core > copying colcon_core/event_reactor.py -> > /<>/.pybuild/cpython3_3.11/build/colcon_core > copying colcon_core/dependency_descriptor.py -> > /<>/.pybuild/cpython3_3.11/build/colcon_core > creating /<>/.pybuild/cpython3_3.11/build/colcon > copying colcon/__init__.py -> > /<>/.pybuild/cpython3_3.11/build/colcon > copying colcon/__main__.py -> > /<>/.pybuild/cpython3_3.11/build/colcon > creating /<>/.pybuild/cpython3_3.11/build/colcon_core/event > copying colcon_core/event/output.py -> > /<>/.pybuild/cpython3_3.11/build/colcon_core/event > copying colcon_core/event/command.py -> > /<>/.pybuild/cpython3_3.11/build/colcon_core/event > copying colcon_core/event/__init__.py -> > /<>/.pybuild/cpython3_3.11/build/colcon_core/event > copying colcon_core/event/test.py -> > /<>/.pybuild/cpython3_3.11/build/colcon_core/event > copying colcon_core/event/timer.py -> > /<>/.pybuild/cpython3_3.11/build/colcon_core/event > copying colcon_core/event/job.py -> > /<>/.pybuild/cpython3_3.11/build/colcon_core/event > creating /<>/.pybuild/cpython3_3.11/build/colcon_core/executor > copying colcon_core/executor/__init__.py -> > /<>/.pybuild/cpython3_3.11/build/colcon_core/executor > copying colcon_core/executor/sequential.py -> > /<>/.pybuild/cpython3_3.11/build/colcon_core/executor > creating /<>/.pybuild/cpython3_3.11/build/colcon_core/shell > copying colcon_core/shell/installed_packages.py -> > /<>/.pybuild/cpython3_3.11/build/colcon_core/shell > copying colcon_core/shell/__init__.py -> > /<>/.pybuild/cpython3_3.11/build/colcon_core/shell > copying colcon_core/shell/dsv.py -> > /<>/.pybuild/cpython3_3.11/build/colcon_core/shell > copying colcon_core/shell/sh.py -> > /<>/.pybuild/cpython3_3.11/build/colcon_core/shell > copying colcon_core/shell/bat.py -> > /<>/.pybuild/cpython3_3.11/build/colcon_core/shell > creating > /<>/.pybuild/cpython3_3.11/build/colcon_core/package_identification > copying colcon_core/package_identification/__init__.py -> > /<>/.pybuild/cpython3_3.11/build/colcon_core/package_identification > copying colcon_core/package_identification/python.py -> > /<&g
Bug#1042336: moment-timezone.js: FTBFS: cp: cannot stat '/usr/share/zoneinfo/posix/*': No such file or directory
Source: moment-timezone.js Version: 0.5.40+dfsg-1+2023c Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230726 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > mkdir -p temp/download/2023c > ln -s /usr/share/zoneinfo/*.tab temp/download/2023c/ > zcat /usr/share/doc/tzdata/changelog.gz > temp/download/2023c/NEWS > grunt data-meta:2023c > >> Local Npm module "grunt-contrib-jshint" not found. Is it installed? > >> Local Npm module "grunt-contrib-uglify" not found. Is it installed? > >> Local Npm module "grunt-contrib-clean" not found. Is it installed? > >> Local Npm module "grunt-exec" not found. Is it installed? > > Running "data-meta:2023c" (data-meta) task > >> Added metadata for 2023c > > Done. > mkdir -p temp/zic/2023c temp/zdump/2023c > cp -RL /usr/share/zoneinfo/posix/* temp/zic/2023c/ > cp: cannot stat '/usr/share/zoneinfo/posix/*': No such file or directory > make[1]: *** [debian/rules:51: data/unpacked/2023c.json] Error 1 The full build log is available from: http://qa-logs.debian.net/2023/07/26/moment-timezone.js_0.5.40+dfsg-1+2023c_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230726;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230726=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime.
Bug#1042334: heudiconv: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13
Source: heudiconv
Version: 0.11.6-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230726 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules binary
> dh binary --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> pybuild --configure -i python{version} -p 3.11
> I: pybuild base:240: python3.11 setup.py config
> running config
>dh_auto_build -O--buildsystem=pybuild
> pybuild --build -i python{version} -p 3.11
> I: pybuild base:240: /usr/bin/python3 setup.py build
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.11_heudiconv/build/heudiconv
> copying heudiconv/_version.py ->
> /<>/.pybuild/cpython3_3.11_heudiconv/build/heudiconv
> copying heudiconv/dicoms.py ->
> /<>/.pybuild/cpython3_3.11_heudiconv/build/heudiconv
> copying heudiconv/due.py ->
> /<>/.pybuild/cpython3_3.11_heudiconv/build/heudiconv
> copying heudiconv/utils.py ->
> /<>/.pybuild/cpython3_3.11_heudiconv/build/heudiconv
> copying heudiconv/__init__.py ->
> /<>/.pybuild/cpython3_3.11_heudiconv/build/heudiconv
> copying heudiconv/queue.py ->
> /<>/.pybuild/cpython3_3.11_heudiconv/build/heudiconv
> copying heudiconv/convert.py ->
> /<>/.pybuild/cpython3_3.11_heudiconv/build/heudiconv
> copying heudiconv/info.py ->
> /<>/.pybuild/cpython3_3.11_heudiconv/build/heudiconv
> copying heudiconv/parser.py ->
> /<>/.pybuild/cpython3_3.11_heudiconv/build/heudiconv
> copying heudiconv/main.py ->
> /<>/.pybuild/cpython3_3.11_heudiconv/build/heudiconv
> copying heudiconv/bids.py ->
> /<>/.pybuild/cpython3_3.11_heudiconv/build/heudiconv
> creating
> /<>/.pybuild/cpython3_3.11_heudiconv/build/heudiconv/heuristics
> copying heudiconv/heuristics/banda-bids.py ->
> /<>/.pybuild/cpython3_3.11_heudiconv/build/heudiconv/heuristics
> copying heudiconv/heuristics/bids_with_ses.py ->
> /<>/.pybuild/cpython3_3.11_heudiconv/build/heudiconv/heuristics
> copying heudiconv/heuristics/bids_PhoenixReport.py ->
> /<>/.pybuild/cpython3_3.11_heudiconv/build/heudiconv/heuristics
> copying heudiconv/heuristics/__init__.py ->
> /<>/.pybuild/cpython3_3.11_heudiconv/build/heudiconv/heuristics
> copying heudiconv/heuristics/reproin.py ->
> /<>/.pybuild/cpython3_3.11_heudiconv/build/heudiconv/heuristics
> copying heudiconv/heuristics/convertall.py ->
> /<>/.pybuild/cpython3_3.11_heudiconv/build/heudiconv/heuristics
> copying heudiconv/heuristics/bids_ME.py ->
> /<>/.pybuild/cpython3_3.11_heudiconv/build/heudiconv/heuristics
> copying heudiconv/heuristics/studyforrest_phase2.py ->
> /<>/.pybuild/cpython3_3.11_heudiconv/build/heudiconv/heuristics
> copying heudiconv/heuristics/test_b0dwi_for_fmap.py ->
> /<>/.pybuild/cpython3_3.11_heudiconv/build/heudiconv/heuristics
> copying heudiconv/heuristics/multires_7Tbold.py ->
> /<>/.pybuild/cpython3_3.11_heudiconv/build/heudiconv/heuristics
> copying heudiconv/heuristics/test_reproin.py ->
> /<>/.pybuild/cpython3_3.11_heudiconv/build/heudiconv/heuristics
> copying heudiconv/heuristics/example.py ->
> /<>/.pybuild/cpython3_3.11_heudiconv/build/heudiconv/heuristics
> copying heudiconv/heuristics/cmrr_heuristic.py ->
> /<>/.pybuild/cpython3_3.11_heudiconv/build/heudiconv/heuristics
> copying heudiconv/heuristics/uc_bids.py ->
> /<>/.pybuild/cpython3_3.11_heudiconv/build/heudiconv/heuristics
> creating
> /<>/.pybuild/cpython3_3.11_heudiconv/build/heudiconv/tests
> copying heudiconv/tests/test_dicoms.py ->
> /<>/.pybuild/cpython3_3.11_heudiconv/build/heudiconv/tests
> copying heudiconv/tests/anonymize_script.py ->
> /<>/.pybuild/cpython3_3.11_heudiconv/build/heudiconv/tests
> copying heudiconv/tests/test_monitor.py ->
> /<>/.pybuild/cpython3_3.11_heudiconv/build/heudiconv/tests
> copying heudiconv/tests/test_bids.py ->
> /<>/.pybuild/cpython3_3.11_heudiconv/build/heudiconv/tests
> copying heudiconv/tests/test_main.py ->
> /<>/.pybuild/cpython3_3.11_heudiconv/build/heudiconv/tests
> copying heudiconv/tests/utils.py ->
> /<>/.pybuild/cpython3_3.11_heudiconv/build/heudiconv/tests
> copying heudiconv/tests/__init__.py ->
> /<>/.pybuild/cpython3_3.11_heudiconv/build/heudiconv/tests
> copying heudiconv/tests/test_queue.py ->
> /<>/.pybuild/cpython3_3.1
Bug#1042332: pytest-bdd: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 --system=custom "--test-args={interpreter} -m pytest -k 'not test_generate_with_quotes and
Source: pytest-bdd Version: 5.0.0-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230726 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_auto_install > I: pybuild base:240: /usr/bin/python3 setup.py install --root > /<>/debian/python3-pytest-bdd > running install > /usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py:66: > SetuptoolsDeprecationWarning: setup.py install is deprecated. > !! > > > > Please avoid running ``setup.py`` directly. > Instead, use pypa/build, pypa/installer or other > standards-based tools. > > See https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html > for details. > > > > !! > self.initialize_options() > running build > running build_py > running egg_info > writing pytest_bdd.egg-info/PKG-INFO > writing dependency_links to pytest_bdd.egg-info/dependency_links.txt > writing entry points to pytest_bdd.egg-info/entry_points.txt > writing requirements to pytest_bdd.egg-info/requires.txt > writing top-level names to pytest_bdd.egg-info/top_level.txt > reading manifest file 'pytest_bdd.egg-info/SOURCES.txt' > reading manifest template 'MANIFEST.in' > adding license file 'LICENSE.txt' > adding license file 'AUTHORS.rst' > writing manifest file 'pytest_bdd.egg-info/SOURCES.txt' > /usr/lib/python3/dist-packages/setuptools/command/build_py.py:201: _Warning: > Package 'pytest_bdd.templates' is absent from the `packages` configuration. > !! > > > > > # Package would be ignored # > > Python recognizes 'pytest_bdd.templates' as an importable package[^1], > but it is absent from setuptools' `packages` configuration. > > This leads to an ambiguous overall configuration. If you want to > distribute this > package, please make sure that 'pytest_bdd.templates' is explicitly > added > to the `packages` configuration field. > > Alternatively, you can also rely on setuptools' discovery methods > (for example by using `find_namespace_packages(...)`/`find_namespace:` > instead of `find_packages(...)`/`find:`). > > You can read more about "package discovery" on setuptools > documentation page: > > - > https://setuptools.pypa.io/en/latest/userguide/package_discovery.html > > If you don't want 'pytest_bdd.templates' to be distributed and are > already explicitly excluding 'pytest_bdd.templates' via > `find_namespace_packages(...)/find_namespace` or > `find_packages(...)/find`, > you can try to use `exclude_package_data`, or > `include-package-data=False` in > combination with a more fine grained `package-data` configuration. > > You can read more about "package data files" on setuptools > documentation page: > > - https://setuptools.pypa.io/en/latest/userguide/datafiles.html > > > [^1]: For Python, any directory (with suitable naming) can be > imported, > even if it does not contain any `.py` files. > On the other hand, currently there is no concept of package data > directory, all directories are treated like packages. > > > > !! > check.warn(importable) > running install_lib > creating /<>/debian/python3-pytest-bdd/usr > creating /<>/debian/python3-pytest-bdd/usr/lib > creating /<>/debian/python3-pytest-bdd/usr/lib/python3.11 > creating > /<>/debian/python3-pytest-bdd/usr/lib/python3.11/dist-packages > creating > /<>/debian/python3-pytest-bdd/usr/lib/python3.11/dist-packages/pytest_bdd > copying > /<>/.pybuild/cpython3_3.11_pytest-bdd/build/pytest_bdd/types.py > -> > /<>/debian/python3-pytest-bdd/usr/lib/python3.11/dist-packages/pytest_bdd > copying > /<>/.pybuild/cpython3_3.11_pytest-bdd/build/pytest_bdd/reporting.py > -> > /<>/debian/python3-pytest-bdd/usr/lib/python3.11/dist-packages/pytest_bdd > copying > /<>/.pybuild/cpython3_3.11_pytest-bdd/build/pytest_bdd/utils.py > -> > /<>/debian/python3-pyt
Bug#1042333: python-django-etcd-settings: FTBFS: make: *** [debian/rules:10: clean] Error 25
Source: python-django-etcd-settings
Version: 0.1.13+dfsg-4
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230726 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> fakeroot debian/rules clean
> dh clean --with python3,sphinxdoc --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:240: python3.11 setup.py clean
> error in django-etcd-settings setup command: 'install_requires' must be a
> string or list of strings containing valid project/version requirement
> specifiers; Expected end or semicolon (after version specifier)
> Django>=1.7.5python-etcd>=0.4.1
> ~~~^
> E: pybuild pybuild:388: clean: plugin distutils failed with: exit code=1:
> python3.11 setup.py clean
> dh_auto_clean: error: pybuild --clean -i python{version} -p 3.11 returned
> exit code 13
> make: *** [debian/rules:10: clean] Error 25
The full build log is available from:
http://qa-logs.debian.net/2023/07/26/python-django-etcd-settings_0.1.13+dfsg-4_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230726;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230726=lu...@debian.org=1=1=1=1#results
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
Bug#1042330: haskell-gi-gtk: FTBFS: make: *** [/usr/share/cdbs/1/class/hlibrary.mk:158: build-ghc-stamp] Error 25
Source: haskell-gi-gtk
Version: 3.0.39-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230726 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules binary
> test -x debian/rules
> dh_testroot
> dh_prep
> dh_installdirs -A
> mkdir -p "."
> CDBS WARNING:DEB_DH_STRIP_ARGS is deprecated since 0.4.85
> CDBS WARNING:DEB_COMPRESS_EXCLUDE is deprecated since 0.4.85
> Adding cdbs dependencies to debian/libghc-gi-gtk-doc.substvars
> dh_installdirs -plibghc-gi-gtk-doc \
>
> perl -d:Confess -MDebian::Debhelper::Buildsystem::Haskell::Recipes=/.*/ \
> -E 'make_setup_recipe'
> Running ghc --make Setup.hs -o debian/hlibrary.setup
> [1 of 1] Compiling Main ( Setup.hs, Setup.o )
> Linking debian/hlibrary.setup ...
> perl -d:Confess -MDebian::Debhelper::Buildsystem::Haskell::Recipes=/.*/ \
> -E 'configure_recipe'
> Running find . ! -newer /tmp/rdmFv1sUG1 -exec touch -d 1998-01-01 UTC {} ;
> Running dh_listpackages
> libghc-gi-gtk-dev
> libghc-gi-gtk-prof
> libghc-gi-gtk-doc
> Running dh_listpackages
> libghc-gi-gtk-dev
> libghc-gi-gtk-prof
> libghc-gi-gtk-doc
> Running dpkg-buildflags --get LDFLAGS
> -Wl,-z,relro
> Running debian/hlibrary.setup configure --ghc -v2
> --package-db=/var/lib/ghc/package.conf.d --prefix=/usr
> --libdir=/usr/lib/haskell-packages/ghc/lib --libexecdir=/usr/lib
> --builddir=dist-ghc --ghc-option=-optl-Wl,-z,relro
> --haddockdir=/usr/lib/ghc-doc/haddock/gi-gtk-3.0.39/ --datasubdir=gi-gtk
> --htmldir=/usr/share/doc/libghc-gi-gtk-doc/html/ --enable-library-profiling
> Using Parsec parser
> Configuring gi-gtk-3.0.39...
> Dependency base >=4.7 && <5: using base-4.15.1.0
> Dependency bytestring >=0.10 && <1: using bytestring-0.10.12.1
> Dependency containers >=0.5 && <1: using containers-0.6.4.1
> Dependency gi-atk >=2.0 && <2.1: using gi-atk-2.0.25
> Dependency gi-cairo >=1.0 && <1.1: using gi-cairo-1.0.27
> Dependency gi-gdk >=3.0 && <3.1: using gi-gdk-3.0.26
> Dependency gi-gdkpixbuf >=2.0 && <2.1: using gi-gdkpixbuf-2.0.29
> Dependency gi-gio >=2.0 && <2.1: using gi-gio-2.0.30
> Dependency gi-glib >=2.0 && <2.1: using gi-glib-2.0.27
> Dependency gi-gobject >=2.0 && <2.1: using gi-gobject-2.0.28
> Dependency gi-pango >=1.0 && <1.1: using gi-pango-1.0.27
> Dependency haskell-gi >=0.26 && <0.27: using haskell-gi-0.26.1
> Dependency haskell-gi-base >=0.26 && <0.27: using haskell-gi-base-0.26.2
> Dependency text >=1.0 && <3: using text-1.2.5.0
> Dependency transformers >=0.4 && <1: using transformers-0.5.6.2
> Dependency gtk+-3.0: using version 3.24.38
> Source component graph: component lib
> Configured component graph:
> component gi-gtk-3.0.39-DdnejyEWH1v6GfZxnbNKBx
> include base-4.15.1.0
> include bytestring-0.10.12.1
> include containers-0.6.4.1
> include gi-atk-2.0.25-CDaASSbJJIECZcqd5HHxMS
> include gi-cairo-1.0.27-71UBRX1jssc9uxAf0nueyE
> include gi-gdk-3.0.26-739nhnqaNuCB31cU3AsCWH
> include gi-gdkpixbuf-2.0.29-60e4qi0SseyGM7ZB4cIFCX
> include gi-gio-2.0.30-Le3XVxnPcE5GGrE1cpn3Om
> include gi-glib-2.0.27-KPNdhQB5q4lD3LJBp2P6eK
> include gi-gobject-2.0.28-1w6AMPQ7GsiBOSk5nE2INb
> include gi-pango-1.0.27-GuCK3XSnzHI1EaZNcfegsg
> include haskell-gi-0.26.1-JSRupHRF34I93KyyU4gimG
> include haskell-gi-base-0.26.2-BgiSD0snxm47Hg27HVVupt
> include text-1.2.5.0
> include transformers-0.5.6.2
> Linked component graph:
> unit gi-gtk-3.0.39-DdnejyEWH1v6GfZxnbNKBx
> include base-4.15.1.0
> include bytestring-0.10.12.1
> include containers-0.6.4.1
> include gi-atk-2.0.25-CDaASSbJJIECZcqd5HHxMS
> include gi-cairo-1.0.27-71UBRX1jssc9uxAf0nueyE
> include gi-gdk-3.0.26-739nhnqaNuCB31cU3AsCWH
> include gi-gdkpixbuf-2.0.29-60e4qi0SseyGM7ZB4cIFCX
> include gi-gio-2.0.30-Le3XVxnPcE5GGrE1cpn3Om
> include gi-glib-2.0.27-KPNdhQB5q4lD3LJBp2P6eK
> include gi-gobject-2.0.28-1w6AMPQ7GsiBOSk5nE2INb
> include gi-pango-1.0.27-GuCK3XSnzHI1EaZNcfegsg
> include haskell-gi-0.26.1-JSRupHRF34I93KyyU4gimG
> include haskell-gi-base-0.26.2-BgiSD0snxm47Hg27HVVupt
> include text-1.2.5.0
> include transformers-0.5.6.2
>
> GI.Gtk=gi-gtk-3.0.39-DdnejyEWH1v6GfZxnbNKBx:GI.Gtk,GI.Gtk.Callbacks=gi-gtk-3.0.3
Bug#1042327: taurus-pyqtgraph: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13
Source: taurus-pyqtgraph Version: 0.5.9-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230726 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules binary > dh binary --with python3 --buildsystem=pybuild >dh_update_autotools_config -O--buildsystem=pybuild >dh_autoreconf -O--buildsystem=pybuild >dh_auto_configure -O--buildsystem=pybuild > I: pybuild base:240: python3.11 setup.py config > running config >dh_auto_build -O--buildsystem=pybuild > I: pybuild base:240: /usr/bin/python3 setup.py build > running build > running build_py > creating > /<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph > copying taurus_pyqtgraph/util.py -> > /<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph > copying taurus_pyqtgraph/taurusmodelchoosertool.py -> > /<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph > copying taurus_pyqtgraph/taurusimageitem.py -> > /<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph > copying taurus_pyqtgraph/buffersizetool.py -> > /<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph > copying taurus_pyqtgraph/autopantool.py -> > /<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph > copying taurus_pyqtgraph/taurustrendset.py -> > /<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph > copying taurus_pyqtgraph/__init__.py -> > /<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph > copying taurus_pyqtgraph/cli.py -> > /<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph > copying taurus_pyqtgraph/curvespropertiestool.py -> > /<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph > copying taurus_pyqtgraph/dateaxisitem.py -> > /<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph > copying taurus_pyqtgraph/curvesmodel.py -> > /<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph > copying taurus_pyqtgraph/forcedreadtool.py -> > /<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph > copying taurus_pyqtgraph/trend.py -> > /<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph > copying taurus_pyqtgraph/plot.py -> > /<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph > copying taurus_pyqtgraph/curveproperties.py -> > /<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph > copying taurus_pyqtgraph/y2axis.py -> > /<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph > copying taurus_pyqtgraph/legendtool.py -> > /<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph > copying taurus_pyqtgraph/taurusplotdataitem.py -> > /<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph > copying taurus_pyqtgraph/datainspectortool.py -> > /<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph > creating > /<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph/examples > copying taurus_pyqtgraph/examples/axislabels.py -> > /<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph/examples > copying taurus_pyqtgraph/examples/taurustrendset.py -> > /<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph/examples > copying taurus_pyqtgraph/examples/__init__.py -> > /<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph/examples > copying taurus_pyqtgraph/examples/legendExample.py -> > /<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph/examples > copying taurus_pyqtgraph/examples/y2axis.py -> > /<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph/examples > copying taurus_pyqtgraph/examples/taurusplotdataitem.py -> > /<>/.pybuild/cpython3_3.11_taurus-pyqtgraph/build/taurus_pyqtgraph/examples > running egg_info > creating taurus_pyqtgraph.egg-info > writing taurus_pyqtgraph.egg-info/PKG-INFO > writing dependency_links to taurus_pyqtgraph.egg-info/dependency_links.txt > writing entry points to taurus_pyqtgraph.egg-info/entry_points.txt > writing requirements to taurus_pyqtgraph.egg-info/requires.txt > writing top-level names to taurus_pyqtgraph.egg-info/top_level.txt > writing manifest file 'taurus_pyqtgraph.egg-info/SOURCES.txt' > reading manifest file 'taurus_pyqtgraph.egg-info/SOURCES.txt' > reading manifest template 'MANIFEST.in' > warning: no previously-included files matching '__pycache__' found under > directory '*' > war
Bug#1042331: rygel: FTBFS: ../meson.build:1:0: ERROR: Unexpected "[provides]" section, did you mean "[provide]"?
Source: rygel Version: 0.42.3-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230726 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_auto_configure -- \ > -Dsystemd-user-units-dir=/usr/lib/systemd/user \ > -Dapi-docs=true \ > -Dintrospection=disabled \ > -Dexamples=false \ > -Dplugins=external,gst-launch,media-export,mpris,playbin,ruih,tracker3 > cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson setup .. > --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc > --localstatedir=/var --libdir=lib/x86_64-linux-gnu > -Dsystemd-user-units-dir=/usr/lib/systemd/user -Dapi-docs=true > -Dintrospection=disabled -Dexamples=false > -Dplugins=external,gst-launch,media-export,mpris,playbin,ruih,tracker3 > The Meson build system > Version: 1.2.0 > Source dir: /<> > Build dir: /<>/obj-x86_64-linux-gnu > Build type: native build > > ../meson.build:1:0: ERROR: Unexpected "[provides]" section, did you mean > "[provide]"? > > A full log can be found at > /<>/obj-x86_64-linux-gnu/meson-logs/meson-log.txt > cd obj-x86_64-linux-gnu && tail -v -n \+0 meson-logs/meson-log.txt > ==> meson-logs/meson-log.txt <== > Build started at 2023-07-26T19:14:20.247837 > Main binary: /usr/bin/python3 > Build Options: -Dsystemd-user-units-dir=/usr/lib/systemd/user -Dapi-docs=true > -Dintrospection=disabled -Dexamples=false > -Dplugins=external,gst-launch,media-export,mpris,playbin,ruih,tracker3 > -Dprefix=/usr -Dlibdir=lib/x86_64-linux-gnu -Dlocalstatedir=/var > -Dsysconfdir=/etc -Dbuildtype=plain -Dwrap_mode=nodownload > Python system: Linux > The Meson build system > Version: 1.2.0 > Source dir: /<> > Build dir: /<>/obj-x86_64-linux-gnu > Build type: native build > > ../meson.build:1:0: ERROR: Unexpected "[provides]" section, did you mean > "[provide]"? > dh_auto_configure: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson > setup .. --wrap-mode=nodownload --buildtype=plain --prefix=/usr > --sysconfdir=/etc --localstatedir=/var --libdir=lib/x86_64-linux-gnu > -Dsystemd-user-units-dir=/usr/lib/systemd/user -Dapi-docs=true > -Dintrospection=disabled -Dexamples=false > -Dplugins=external,gst-launch,media-export,mpris,playbin,ruih,tracker3 > returned exit code 1 > make[1]: *** [debian/rules:22: override_dh_auto_configure] Error 25 The full build log is available from: http://qa-logs.debian.net/2023/07/26/rygel_0.42.3-2_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230726;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230726=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime.
