Bug#983229: proj transition has started
On Tue, Oct 26, 2021 at 05:35:48AM +0200, Sebastiaan Couwenberg wrote: > PROJ 8.2.0 is scheduled for release next week, just wait for that. OK. > You also mentioned in the upstream issue that you need a solution for other > users who cannot upgrade to PROJ 8.2.0, did you give up on that and made > 8.2.0 a hard requirement? I'd certainly prefer not to hard require PROJ >= 8.2.0, but I don't see a good way to allow that without a lot of conditionalisation on PROJ version. It's not just the C code - there are some differences in the testsuite due to things like newer PROJ correcting for the vertical datum and older PROJ not. Maybe bumping the upstream minor version for the PROJ 8.2.0 compatible version would be a good approach - then people who don't have easy access to PROJ 8.2.0 have an obvious older Survex version to use, and any important bug fixes can be backported without having to add an extra version component. Cheers, Olly
Bug#983229: proj transition has started
On 10/25/21 23:56, Olly Betts wrote: On Fri, Oct 22, 2021 at 06:36:53AM +0200, Sebastiaan Couwenberg wrote: The proj transition has started, raising the severity accordingly. As I noted in the upstream ticket (which I know you are subscribed to) Survex requires a fix to make proj_factors() actually usable in the "new PROJ" world. According to the doc change in the patch and the milestone set, this will be in PROJ 8.2.0: https://github.com/OSGeo/PROJ/pull/2868 There isn't a sensible workaround I can see, so if you want to push through the transition before 8.2.0 is out, please apply the above patch to the proj package. PROJ 8.2.0 is scheduled for release next week, just wait for that. You also mentioned in the upstream issue that you need a solution for other users who cannot upgrade to PROJ 8.2.0, did you give up on that and made 8.2.0 a hard requirement? Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#997845: (no subject)
i'm not sure whether the "forwarded" tag applies in this case, but i've created an upstream bug (i am the upstream author) at https://github.com/dankamongmen/growlight/issues/153. signature.asc Description: PGP signature
Bug#997845: (no subject)
Package: growlight Version: 1.2.37-2 Tags: upstream Yep, I'm looking into it. For whatever reason, it's not exiting despite input having ended. I've tried reproducing this failure locally, but have not yet been able. I hope to fix it for 1.2.38. -- nick black -=- https://www.nick-black.com to make an apple pie from scratch, you need first invent a universe.
Bug#997500: marked as done (wxpython4.0: FTBFS: tar: wx_siplib-12.8.1.tar.gz: Cannot open: No such file or directory)
Your message dated Tue, 26 Oct 2021 02:24:28 + with message-id and subject line Bug#997500: fixed in wxpython4.0 4.0.7+dfsg-12 has caused the Debian Bug report #997500, regarding wxpython4.0: FTBFS: tar: wx_siplib-12.8.1.tar.gz: Cannot open: 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.) -- 997500: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997500 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: wxpython4.0 Version: 4.0.7+dfsg-11 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules build > dh build --with python3 --buildsystem=pybuild >dh_update_autotools_config -O--buildsystem=pybuild >dh_autoreconf -O--buildsystem=pybuild >dh_auto_configure -O--buildsystem=pybuild >debian/rules override_dh_auto_build > make[1]: Entering directory '/<>' > # Generate sip module code to replace bundled version > rm -rf sip/siplib > sip-module --abi-version 12.8 --sdist wx.siplib > tar -xf wx_siplib-12.8.1.tar.gz > tar: wx_siplib-12.8.1.tar.gz: Cannot open: No such file or directory > tar: Error is not recoverable: exiting now > make[1]: *** [debian/rules:23: override_dh_auto_build] Error 2 The full build log is available from: http://qa-logs.debian.net/2021/10/23/wxpython4.0_4.0.7+dfsg-11_unstable.log 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 marking 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: wxpython4.0 Source-Version: 4.0.7+dfsg-12 Done: Scott Talbert We believe that the bug you reported is fixed in the latest version of wxpython4.0, 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 997...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Scott Talbert (supplier of updated wxpython4.0 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: Mon, 25 Oct 2021 20:10:23 -0400 Source: wxpython4.0 Architecture: source Version: 4.0.7+dfsg-12 Distribution: unstable Urgency: medium Maintainer: wxWidgets Maintainers Changed-By: Scott Talbert Closes: 997500 Changes: wxpython4.0 (4.0.7+dfsg-12) unstable; urgency=medium . * Fix FTBFS with sip 6.3.1 (Closes: #997500) Checksums-Sha1: 98cec67aea303e96eeb8aaa5feaaf962f7723ee4 2560 wxpython4.0_4.0.7+dfsg-12.dsc 264ac4dbcb7e04823caa5e4178b33fea71fd1f67 38256 wxpython4.0_4.0.7+dfsg-12.debian.tar.xz 6755fd427f62845e4fe3b865953baed6a1be65e9 20155 wxpython4.0_4.0.7+dfsg-12_amd64.buildinfo Checksums-Sha256: 4015b05d82d3a4dad9f2b9b6f3821e54ffcdb27387495e72d1060441ed7a7040 2560 wxpython4.0_4.0.7+dfsg-12.dsc 2e007248c788d0cd98863356a09110d2750e84f027086def63caf93f4adb4056 38256 wxpython4.0_4.0.7+dfsg-12.debian.tar.xz 07dad2886ed8f650c0a57ed7ed2369367b1f709a863031c48dd9c27f52be8bc2 20155 wxpython4.0_4.0.7+dfsg-12_amd64.buildinfo Files: 86430b6846fbd43becbc3d7fd0633dbc 2560 python optional wxpython4.0_4.0.7+dfsg-12.dsc e039829895d41e016bab73affc857e7f 38256 python optional wxpython4.0_4.0.7+dfsg-12.debian.tar.xz c8fe379ba97e3b1f22127f7b1c185150 20155 python optional wxpython4.0_4.0.7+dfsg-12_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJDBAEBCgAtFiEEbnQ09Yl9Q7F/zVe3U9W8ZLUjeKIFAmF3Yi0PHHN3dEB0ZWNo aWUubmV0AAoJEFPVvGS1I3iiTPoQALOtuKVPALHWRTLSlwHTruIHKAVIYTmt8NWd l/6S09R+b7cU5+hcg5cyPVAmvwij88K9KffkSsEpV8xm4thDf6vH4Z1vbBaEnfem 1oUaf6QtTUgW4NlJcHhTrnnDwnJKqgSR+EftUafyoxfWy2dSmDxSjdPKxNm7mj3X GHN/qdxiieMgupionvQQ7UmFk6Er5A2Hs9y+WIY91qnVryyUcV9PqPHfTC5CJ9Ph I2SvKrjxsPbMbEFikndN7K38UnPnriec67KLbuVj8F8cbsDrXDygIfTNbCk65p8r lzDataM4/KPICjNEG8hLW3PRznoclmAAw+eqTye/rZsFZ8HI9jf9wc/d4+JahEd9
Bug#997280: marked as done (sra-sdk: FTBFS: ld: /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to `ZSTD_freeDCtx')
Your message dated Tue, 26 Oct 2021 02:24:19 + with message-id and subject line Bug#997280: fixed in sra-sdk 2.11.3+dfsg-1 has caused the Debian Bug report #997280, regarding sra-sdk: FTBFS: ld: /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to `ZSTD_freeDCtx' 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.) -- 997280: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997280 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: sra-sdk Version: 2.10.9+dfsg-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > g++ -static-libgcc -o > /<>/debian/tmp/usr/sra-tools/linux/gcc/x86_64/rel/bin/sratools.2.10.9 > -Wl,-z,relro -Wl,-z,now -DNDEBUG -m64 sratools.o sratools2.o > imp_fasterq_dump.o imp_fastq_dump.o imp_prefetch.o imp_sam_dump.o > imp_sra_pileup.o imp_srapath.o imp_vdb_dump.o cmdline.o config.o proc.o > run-source.o uuid.o service.o > -L/<>/debian/tmp/usr/sra-tools/linux/gcc/x86_64/rel/lib > -L/<>/debian/tmp/usr/sra-tools/linux/gcc/x86_64/rel/ilib > -L/usr/lib/x86_64-linux-gnu -L/usr/lib/x86_64-linux-gnu > -L/usr/lib/x86_64-linux-gnu -lncbi-vdb -ljson -Wl,-Bdynamic -ldl -lpthread > -lxml2 -Wl,-Bdynamic -lm -lz -lbz2 -lsz -lmbedx509 -lmbedtls -lmbedcrypto > /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to > `ZSTD_freeDCtx' > /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to > `ZSTD_decompressDCtx' > /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to > `ZSTD_createDCtx' > /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to > `ZSTD_isError' > /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libncbi-vdb.so: undefined reference to > `ZSTD_getErrorName' > collect2: error: ld returned 1 exit status The full build log is available from: http://qa-logs.debian.net/2021/10/23/sra-sdk_2.10.9+dfsg-2_unstable.log 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 marking 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: sra-sdk Source-Version: 2.11.3+dfsg-1 Done: Aaron M. Ucko We believe that the bug you reported is fixed in the latest version of sra-sdk, 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 997...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Aaron M. Ucko (supplier of updated sra-sdk 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: Mon, 25 Oct 2021 18:29:10 -0400 Source: sra-sdk Architecture: source Version: 2.11.3+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Aaron M. Ucko Closes: 997280 Changes: sra-sdk (2.11.3+dfsg-1) unstable; urgency=medium . [ Andreas Tille ] * Fix watchfile to detect new versions on github * New upstream version 2.11.2. * Standards-Version: 4.6.0 (routine-update) * Bump versioned Build-Depends: libngs-sdk-dev (>= 2.11.2) * Skip test that test needs a *lot* of memory * Link against libzstd. (Closes: #997280.) . [ Aaron M. Ucko ] * d/p/fix_libngs_linkage.patch (new): Substitute ngs-c++ library for absent ngs library. * debian/rules: Stop renaming kget (to avoid a file conflict, #851219) now that it's retired altogether. * d/p/allow_multi_help.patch (new): Tolerate redundant --help declarations within tools/driver-tool. * d/p/run_unversioned_tools.patch (new): Look for tools by their unversioned names, per Debian's simplified installation arrangement. * debian/tests: Switch to modern encryption/decryption setup. - run-unit-test: Replace protected repository configuration (no longer supported as of
Bug#617856: New version of apt-show-versions fixes 617856
On Mon, 2021-10-25 at 13:00 +0200, Christoph Martin wrote: > I will try to upload a new release. I could not do so in the last > weeks, because my signature-key had expired and the new one did not yet > make it into the keyring. You could upload to mentors.debian.net and file an RFS request: https://mentors.debian.net/sponsors/rfs-howto/ -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#997425: marked as done (cedar-backup3: FTBFS: Could not import extension autoapi.extension (exception: No module named 'typing_extensions'))
Your message dated Tue, 26 Oct 2021 01:18:30 + with message-id and subject line Bug#997425: fixed in cedar-backup3 3.6.3-4 has caused the Debian Bug report #997425, regarding cedar-backup3: FTBFS: Could not import extension autoapi.extension (exception: No module named 'typing_extensions') 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.) -- 997425: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997425 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: cedar-backup3 Version: 3.6.3-3 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[2]: Entering directory '/<>/docs' > sphinx-build -b html -d _build/doctrees . _build/html > Running Sphinx v4.2.0 > > Extension error: > Could not import extension autoapi.extension (exception: No module named > 'typing_extensions') > make[2]: *** [Makefile:53: html] Error 2 The full build log is available from: http://qa-logs.debian.net/2021/10/23/cedar-backup3_3.6.3-3_unstable.log 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 marking 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: cedar-backup3 Source-Version: 3.6.3-4 Done: Kenneth J. Pronovici We believe that the bug you reported is fixed in the latest version of cedar-backup3, 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 997...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Kenneth J. Pronovici (supplier of updated cedar-backup3 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: Mon, 25 Oct 2021 23:45:59 + Source: cedar-backup3 Architecture: source Version: 3.6.3-4 Distribution: unstable Urgency: medium Maintainer: Kenneth J. Pronovici Changed-By: Kenneth J. Pronovici Closes: 997425 Changes: cedar-backup3 (3.6.3-4) unstable; urgency=medium . * Add Lintian override for very-long-line-length-in-source-file. * Add Lintian override for package-contains-python-dot-directory. * Add build dep on python3-typing-extensions until we can sort out problems with python3-sphinx-autoapi (closes: #997425). Checksums-Sha1: 87ea4a6e2390aec3b46d636e57cd76fb83cbc61e 2164 cedar-backup3_3.6.3-4.dsc bd3827d1e0e2475121dcb27d70fc15055b6e9e71 12352 cedar-backup3_3.6.3-4.debian.tar.xz c9d493abdb0c3d0f075e476f1343547a3f728971 8402 cedar-backup3_3.6.3-4_amd64.buildinfo Checksums-Sha256: 397679be4280c9e5dcbefe56ae74c26c4cb89ba741560e047d65dd20c61f8dd6 2164 cedar-backup3_3.6.3-4.dsc a8aee219cc5305059eb4223e0748d2dad0d9d758c0fc08853e6e03c4d6900df8 12352 cedar-backup3_3.6.3-4.debian.tar.xz 6388199f4beb13e97b2efad613341fafdf81df3fde4e385a15971caf86fc6255 8402 cedar-backup3_3.6.3-4_amd64.buildinfo Files: 9a8683518260ecdd61d638ec942f8a8f 2164 admin optional cedar-backup3_3.6.3-4.dsc 6c1eb715d5fdffb8582bcc130ad96bdb 12352 admin optional cedar-backup3_3.6.3-4.debian.tar.xz e39f1263741fe04d99f7d3e50c5d4061 8402 admin optional cedar-backup3_3.6.3-4_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEECkY/XOB9CXm1xckHERkoku/XWTQFAmF3UAwACgkQERkoku/X WTRxRA//cIzgEza98Mardnbkyc+0MTwhELJ8tZSCgRb8UJfXEGGuocMzteRYCjiW u5Mo/2r9U4XZrfQ113dGWwdbb8Jy0t51HwtqsMSuvSUkuNa0TbfdxxyUOGt9qdut KBjUpGri2qUN3T8VPixEbSsd//B3hiBE5SgE3vH63m64xG6cvHbKuDXf/YlyFgcX zsiLgpKGIchYWodB6ZxoN7gXayu/CPv8EZ9ZRilvHRkENqDC/zzTB7QhnWzNWs67 A1PHA8Xu/LYPLrGX3AZVDWzRbMPBKSNWvuJnetpuv+tCmqG1k/ku+OnOzPZ7gGux MWolYSWAnj3iSKWOcp4Lfco3UcbYC5sB1wzfYhonnx9IYsAunOzMMNYyXZYa5QVZ X0I05t2ZvLBXYavjoCK8Mr/5LbyWrwiDPMRlYu9uWwiRney4EwGzJ4CKIuPl0QyP wNOG824Aghh7FhZ0T/bMCJHaWdTREkHxW3dPSCdtddSIkr72MZaMW8jC26ryRPf9
Bug#984243: Help: mothur: ftbfs with GCC-11
Andreas Tille writes: > I'm wondering why the makefile stopped working just because a new compiler > version is used. :-( Along the way, you pulled in a new upstream version, whose makefile evidently wasn't quite right. -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
Bug#997425: Adding dependency for now
I've decided to add the build dependency for the time being, to fix my FTBFS. If/when we sort things out with Sphinx, I can remove it. KEN -- Kenneth J. Pronovici signature.asc Description: PGP signature
Bug#995623: marked as done (refind FTBFS: error: conflicting types for ‘EFI_DEVICE_PATH_UTILITIES_PROTOCOL’)
Your message dated Mon, 25 Oct 2021 23:20:37 + with message-id and subject line Bug#995623: fixed in refind 0.13.2-1 has caused the Debian Bug report #995623, regarding refind FTBFS: error: conflicting types for ‘EFI_DEVICE_PATH_UTILITIES_PROTOCOL’ 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.) -- 995623: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995623 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: refind Version: 0.12.0-1 Severity: serious Tags: ftbfs refind fails to build from source in unstable on amd64 and it also fails to cross build for arm64 for the same reason. A build ends as follows: | make[3]: Entering directory '/<>/EfiLib' | /usr/bin/gcc -Os -fno-strict-aliasing -fno-tree-loop-distribute-patterns -fno-stack-protector -fshort-wchar -Wall -DEFIX64 -DEFI_FUNCTION_WRAPPER -m64 -mno-red-zone -fpic -I/usr/include/efi -I/usr/include/efi/x86_64 -I/usr/include/efi/protocol -I../include -I../refind -I../libeg -I../mok -I. -I./../include \ | -D__MAKEWITH_GNUEFI -c gnuefi-helper.c -o gnuefi-helper.o | In file included from gnuefi-helper.c:19: | DevicePathUtilities.h:229:3: error: conflicting types for ‘EFI_DEVICE_PATH_UTILITIES_PROTOCOL’ | 229 | } EFI_DEVICE_PATH_UTILITIES_PROTOCOL; | | ^~ | In file included from /usr/include/efi/efi.h:61, | from gnuefi-helper.h:24, | from gnuefi-helper.c:18: | /usr/include/efi/efidevp.h:648:3: note: previous declaration of ‘EFI_DEVICE_PATH_UTILITIES_PROTOCOL’ was here | 648 | } EFI_DEVICE_PATH_UTILITIES_PROTOCOL; | | ^~ | make[3]: *** [../Make.common:164: gnuefi-helper.o] Error 1 | make[3]: Leaving directory '/<>/EfiLib' | make[2]: *** [Makefile:86: gnuefi] Error 2 | make[2]: Leaving directory '/<>' | dh_auto_build: error: make -j1 gnuefi ARCH=x86_64 returned exit code 2 | make[1]: *** [debian/rules:33: override_dh_auto_build] Error 25 | make[1]: Leaving directory '/<>' | make: *** [debian/rules:26: build] Error 2 | dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2 Also seen by crossqa: http://crossqa.debian.net Reproduced natively on arm64 by reproducible builds: https://tests.reproducible-builds.org/debian/rbuild/unstable/arm64/refind_0.12.0-1.rbuild.log.gz Helmut --- End Message --- --- Begin Message --- Source: refind Source-Version: 0.13.2-1 Done: Tianon Gravi We believe that the bug you reported is fixed in the latest version of refind, 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 995...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Tianon Gravi (supplier of updated refind 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: Mon, 25 Oct 2021 15:44:40 -0700 Source: refind Architecture: source Version: 0.13.2-1 Distribution: unstable Urgency: medium Maintainer: Rod Smith Changed-By: Tianon Gravi Closes: 958744 995623 Changes: refind (0.13.2-1) unstable; urgency=medium . [ Debian Janitor ] * Remove constraints unnecessary since stretch: + Build-Depends: Drop versioned constraint on debhelper. . [ Tianon Gravi ] * Update to 0.13.2 upstream release - see http://www.rodsbooks.com/refind/revisions.html for changes - "Updated CentOS Secure Boot (MOK) keys" (Closes: #958744) * Backport "gnu-efi" fix (Closes: #995623) Checksums-Sha1: 9d8c6ea3caff89df6528c84711ae3bee97b98a0d 1903 refind_0.13.2-1.dsc 200c6a26ab8c6fac09337c987e7a670d6546e5a5 4554759 refind_0.13.2.orig.tar.gz 343a6e0569617f712e0d5e45f06b919d7c59a4ff 20868 refind_0.13.2-1.debian.tar.xz 8e3241579b40abc02d0d9efc918cd217294196e9 5429 refind_0.13.2-1_source.buildinfo Checksums-Sha256: 3678abebe122becd0852d5f4fb32ae4ffb190cbf08cfae99bc6396040c4a8454 1903 refind_0.13.2-1.dsc dd58944854a42df5a2a943f15e5dcfd995808f28580df96ad39d68fb1e48c970 4554759 refind_0.13.2.orig.tar.gz 2ed2039523a3ffe1aa0247d96a4dd82b4693fd3d438bf7074d9ba369aadde935 20868 refind_0.13.2-1.debian.tar.xz aee648830a0317c75bf35499f24f217748a86db7dd264899e68f1a34834557db 5429 refind_0.13.2-1_source.buildinfo
Bug#997513: dovecot: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2
The source of these test failure is LTO: it built fine with GCC 10.3 with LTO a month ago on buildd, GCC 11 without LTO works and Clang 13 with LTO also works. So either there is some subtle undefined behaviour in dovecot (which gets miscompiled) or the code generation in GCC 11 is buggy (maybe related [1]). For the mean time the simplest solution is probably to disable LTO (or switch to building with Clang?). [1]: https://bugs.gentoo.org/show_bug.cgi?id=787158
Processed: Re: Bug#995623: refind FTBFS: error: conflicting types for ‘EFI_DEVICE_PATH_UTILITIES_PROTOCOL’
Processing commands for cont...@bugs.debian.org: > tags 995623 + pending Bug #995623 [src:refind] refind FTBFS: error: conflicting types for ‘EFI_DEVICE_PATH_UTILITIES_PROTOCOL’ Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 995623: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995623 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#995623: refind FTBFS: error: conflicting types for ‘EFI_DEVICE_PATH_UTILITIES_PROTOCOL’
tags 995623 + pending thanks On Sat, 23 Oct 2021 at 07:25, Rod Smith wrote: > > I've fixed this problem with commit 10f838: > > https://sourceforge.net/p/refind/code/commit_browser > > You should be able to cherry-pick that, although changes to NEWS.txt and > include/version.h might need to be ignored. Also, there are a number of > other changes that have been made, and some others that I need to make, > so I may be releasing a new version before too long. I might do that > this weekend, but it might take another week or two before I can get to > them. Nice, this works well in my testing! I've committed this to the Debian Git repo in https://salsa.debian.org/debian/refind/-/commit/f99402677816ef91dd63a6afcb47fc89fb72b904 I hope to get it uploaded soon (which will include the update to 0.13.2 as well). ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4
Bug#997351: marked as done (med-fichier: FTBFS: configure: error: This HDF5 version ..7 must not be used with med-fichier4.1.0.)
Your message dated Mon, 25 Oct 2021 22:33:33 + with message-id and subject line Bug#997351: fixed in med-fichier 4.1.0+repack-3 has caused the Debian Bug report #997351, regarding med-fichier: FTBFS: configure: error: This HDF5 version ..7 must not be used with med-fichier4.1.0. to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 997351: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997351 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: med-fichier Version: 4.1.0+repack-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > checking for sys/types.h... yes > checking for unistd.h... yes > checking for sys/time.h... yes > checking absolute name of ... checking for H5public.h... yes > ///usr/lib/x86_64-linux-gnu/hdf5/openmpi/include/H5public.h > configure: error: > This HDF5 version ..7 must not be used with med-fichier4.1.0. > The HDF5 library version used by med-fichier4.y.z MUST NOT be > 1.10 and have > to be at least HDF5-1.10.2. > DO NOT TRY TO COMPILE med-fichier4.1.0 version with an HDF5 library which > would generate an hdf5 file not compliant with HDF5-1.10.z library. > This would BREAK med-fichier compatibility between files with the same > revision number ! > > cd build.python3.9 && tail -v -n \+0 config.log The full build log is available from: http://qa-logs.debian.net/2021/10/23/med-fichier_4.1.0+repack-2_unstable.log 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 marking 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: med-fichier Source-Version: 4.1.0+repack-3 Done: Gilles Filippini We believe that the bug you reported is fixed in the latest version of med-fichier, 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 997...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Gilles Filippini (supplier of updated med-fichier package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 26 Oct 2021 00:03:04 +0200 Source: med-fichier Architecture: source Version: 4.1.0+repack-3 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Gilles Filippini Closes: 997351 Changes: med-fichier (4.1.0+repack-3) unstable; urgency=medium . * New patch check_hdf5.patch to fix HDF5 version checking (Closes: #997351) Checksums-Sha1: 3f016cb1ca105a4829a8518d0a85f9648c7f1ab0 2514 med-fichier_4.1.0+repack-3.dsc d9cf97bde19d7e8dc4a2faef2161b0c2ca13f04a 14356 med-fichier_4.1.0+repack-3.debian.tar.xz 88b62598a4eced6486da149bd0a63b6e1e43c028 14873 med-fichier_4.1.0+repack-3_amd64.buildinfo Checksums-Sha256: 7765986049147e965a05042e2105f72276c95817539ddd3d4a3f21a46c0175f0 2514 med-fichier_4.1.0+repack-3.dsc d49d7934f51b8f555c0cbb57363701af46f95cd4b19892cfac9854de5beb5d36 14356 med-fichier_4.1.0+repack-3.debian.tar.xz d67393f94f151626f0fa6c48e8655e1ac9d65aa2b1f516722bfc5a4b4d7a09d9 14873 med-fichier_4.1.0+repack-3_amd64.buildinfo Files: 370d2902649f66c5399d2610ced2aee3 2514 libs optional med-fichier_4.1.0+repack-3.dsc e11ce85534542014cdc38cfb00c2dbbf 14356 libs optional med-fichier_4.1.0+repack-3.debian.tar.xz af7409141d6f12f77c8a4aa4ef4be0b8 14873 libs optional med-fichier_4.1.0+repack-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQFEBAEBCgAuFiEEoJObzArDE05WtIyR7+hsbH/+z4MFAmF3LiQQHHBpbmlAZGVi aWFuLm9yZwAKCRDv6Gxsf/7Pg+8cB/4oBVAxO6AfNJRTF2R31GpWHW8EmNo8JZsW crtGGdykbX5EHSPtzaR+Lj0kkq77d4/N9let8E1kLNuX9NE4osAdEdhdbLVcU9h4 01qoAAD2mjr7CP6dw2H0EiKjGAX8i5HvxYGh2aGe1NLmVIyXgoDuzHkxMxHsWXDv 0oAYy5Llt+CTXapCAtB7jpj69IGGz6ZIzXMFmWOyjIjA0wTTnOhP60WwkNzE43uW
Bug#997758: nose: FTBFS: There is a syntax error in your configuration file: invalid syntax (conf.py, line 220)
On 10/25/21 8:18 PM, Dmitry Shachnev wrote: > However, it would be still nice to remove nose at some future point, maybe > before Bookworm release. Will do, probably for the next version of OpenStack (last one made me update 220 packages: that's a good way to review everything). > I'm impressed by the number of packages you have depending on nose, but if > they all come from the same upstream, maybe you can convince this upstream > to not rely on dead software. I believe most dependencies on Nose could be removed (for example, all of the OpenStack dashboard stuff...), but just right after a release isn't the best time to start the work... Cheers, Thomas Goirand (zigo)
Bug#983229: proj transition has started
On Fri, Oct 22, 2021 at 06:36:53AM +0200, Sebastiaan Couwenberg wrote: > The proj transition has started, raising the severity accordingly. As I noted in the upstream ticket (which I know you are subscribed to) Survex requires a fix to make proj_factors() actually usable in the "new PROJ" world. According to the doc change in the patch and the milestone set, this will be in PROJ 8.2.0: https://github.com/OSGeo/PROJ/pull/2868 There isn't a sensible workaround I can see, so if you want to push through the transition before 8.2.0 is out, please apply the above patch to the proj package. Cheers, Olly
Bug#997559: marked as done (golang-github-smallstep-cli: FTBFS: dh_auto_test: error: cd _build && go test -vet=off -v -p 4 github.com/smallstep/cli/crypto/x509util returned exit code 1)
Your message dated Mon, 25 Oct 2021 22:18:40 + with message-id and subject line Bug#997559: fixed in golang-github-smallstep-cli 0.15.16+ds-2 has caused the Debian Bug report #997559, regarding golang-github-smallstep-cli: FTBFS: dh_auto_test: error: cd _build && go test -vet=off -v -p 4 github.com/smallstep/cli/crypto/x509util returned exit code 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.) -- 997559: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997559 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: golang-github-smallstep-cli Version: 0.15.16+ds-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > dpkg-buildpackage > - > > Command: dpkg-buildpackage -us -uc -sa -rfakeroot > dpkg-buildpackage: info: source package golang-github-smallstep-cli > dpkg-buildpackage: info: source version 0.15.16+ds-1 > dpkg-buildpackage: info: source distribution unstable > dpkg-buildpackage: info: source changed by Nilesh Patra > dpkg-source --before-build . > dpkg-buildpackage: info: host architecture amd64 > debian/rules clean > dh clean --builddirectory=_build --buildsystem=golang --with=golang >dh_auto_clean -O--builddirectory=_build -O--buildsystem=golang >dh_autoreconf_clean -O--builddirectory=_build -O--buildsystem=golang >dh_clean -O--builddirectory=_build -O--buildsystem=golang > dpkg-source -b . > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-source: info: building golang-github-smallstep-cli using existing > ./golang-github-smallstep-cli_0.15.16+ds.orig.tar.xz > dpkg-source: info: using patch list from debian/patches/series > dpkg-source: info: building golang-github-smallstep-cli in > golang-github-smallstep-cli_0.15.16+ds-1.debian.tar.xz > dpkg-source: info: building golang-github-smallstep-cli in > golang-github-smallstep-cli_0.15.16+ds-1.dsc > 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 4 > github.com/smallstep/cli/crypto/x509util > internal/unsafeheader > internal/goexperiment > internal/abi > internal/cpu > runtime/internal/sys > runtime/internal/atomic > runtime/internal/math > internal/race > sync/atomic > math/bits > internal/bytealg > unicode/utf8 > math > unicode > crypto/internal/subtle > crypto/subtle > internal/itoa > container/list > runtime > unicode/utf16 > vendor/golang.org/x/crypto/cryptobyte/asn1 > internal/nettrace > vendor/golang.org/x/crypto/internal/subtle > golang.org/x/crypto/internal/subtle > github.com/shurcooL/sanitized_anchor_name > golang.org/x/sys/internal/unsafeheader > encoding > golang.org/x/net/html/atom > internal/reflectlite > sync > internal/testlog > internal/singleflight > math/rand > runtime/cgo > errors > sort > io > strconv > internal/oserror > syscall > hash > bytes > crypto > strings > reflect > bufio > internal/syscall/unix > path > time > internal/syscall/execenv > crypto/internal/randutil > crypto/elliptic/internal/fiat > crypto/hmac > io/fs > internal/poll > context > crypto/rc4 > vendor/golang.org/x/net/dns/dnsmessage > encoding/binary > internal/fmtsort > os > vendor/golang.org/x/crypto/hkdf > golang.org/x/crypto/blowfish > crypto/cipher > crypto/sha1 > crypto/aes > crypto/sha256 > fmt > crypto/des > crypto/sha512 > crypto/ed25519/internal/edwards25519/field > crypto/md5 > encoding/base64 > math/big > net > crypto/ed25519/internal/edwards25519 > encoding/hex > encoding/pem > net/url > path/filepath > vendor/golang.org/x/crypto/chacha20 > vendor/golang.org/x/crypto/poly1305 > io/ioutil > vendor/golang.org/x/sys/cpu > vendor/golang.org/x/crypto/curve25519 > vendor/golang.org/x/crypto/chacha20poly1305 > crypto/rand > crypto/elliptic > encoding/asn1 > crypto/rsa > crypto/ed25519 > crypto/dsa > github.com/pkg/errors > vendor/golang.org/x/crypto/cryptobyte > crypto/x509/pkix > golang.org/x/crypto/chacha20 > golang.org/x/crypto/curve25519/internal/field > golang.org/x/crypto/ed25519 > golang.org/x/crypto/poly1305 > crypto/ecdsa > golang.org/x/crypto/curve25519 > golang.org/x/crypto/ssh/internal/bcrypt_pbkdf >
Processed: block 996757 with 997832
Processing commands for cont...@bugs.debian.org: > block 996757 with 997832 Bug #996757 [src:golang-github-lucas-clemente-quic-go] golang-github-lucas-clemente-quic-go: FTBFS with golang/1.17: panic: qtls.ClientHelloInfo doesn't match 996757 was not blocked by any bugs. 996757 was not blocking any bugs. Added blocking bug(s) of 996757: 997832 > thanks Stopping processing here. Please contact me if you need assistance. -- 996757: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996757 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#997551: marked as done (golang-github-biogo-biogo: FTBFS: dh_auto_test: error: cd _build && go test -vet=off -v -p 4 github.com/biogo/biogo github.com/biogo/biogo/align ... returned exit code 1)
Your message dated Mon, 25 Oct 2021 21:21:41 + with message-id and subject line Bug#997551: fixed in golang-github-biogo-biogo 1.0.3-2 has caused the Debian Bug report #997551, regarding golang-github-biogo-biogo: FTBFS: dh_auto_test: error: cd _build && go test -vet=off -v -p 4 github.com/biogo/biogo github.com/biogo/biogo/align ... returned exit code 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.) -- 997551: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997551 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: golang-github-biogo-biogo Version: 1.0.3-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > dpkg-buildpackage > - > > Command: dpkg-buildpackage -us -uc -sa -rfakeroot > dpkg-buildpackage: info: source package golang-github-biogo-biogo > dpkg-buildpackage: info: source version 1.0.3-1 > dpkg-buildpackage: info: source distribution unstable > dpkg-buildpackage: info: source changed by Nilesh Patra > dpkg-source --before-build . > dpkg-buildpackage: info: host architecture amd64 > debian/rules clean > dh clean --builddirectory=_build --buildsystem=golang --with=golang >dh_auto_clean -O--builddirectory=_build -O--buildsystem=golang >dh_autoreconf_clean -O--builddirectory=_build -O--buildsystem=golang >dh_clean -O--builddirectory=_build -O--buildsystem=golang > dpkg-source -b . > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-source: info: building golang-github-biogo-biogo using existing > ./golang-github-biogo-biogo_1.0.3.orig.tar.gz > dpkg-source: info: building golang-github-biogo-biogo in > golang-github-biogo-biogo_1.0.3-1.debian.tar.xz > dpkg-source: info: building golang-github-biogo-biogo in > golang-github-biogo-biogo_1.0.3-1.dsc > 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 4 github.com/biogo/biogo > github.com/biogo/biogo/align github.com/biogo/biogo/align/matrix > github.com/biogo/biogo/align/pals github.com/biogo/biogo/align/pals/dp > github.com/biogo/biogo/align/pals/filter github.com/biogo/biogo/alphabet > github.com/biogo/biogo/complexity github.com/biogo/biogo/concurrent > github.com/biogo/biogo/errors github.com/biogo/biogo/feat > github.com/biogo/biogo/feat/gene github.com/biogo/biogo/feat/genome > github.com/biogo/biogo/feat/genome/cow/bt7 > github.com/biogo/biogo/feat/genome/drosophila/dm3 > github.com/biogo/biogo/feat/genome/human/hg19 > github.com/biogo/biogo/feat/genome/mouse/mm10 > github.com/biogo/biogo/index/kmerindex github.com/biogo/biogo/io/featio > github.com/biogo/biogo/io/featio/bed github.com/biogo/biogo/io/featio/gff > github.com/biogo/biogo/io/seqio github.com/biogo/biogo/io/seqio/alignio > github.com/biogo/biogo/io/seqio/fai github.com/biogo/biogo/io/seqio/fasta > github.com/biogo/biogo/io/seqio/fastq github.com/biogo/biogo/morass > github.com/biogo/biogo/pwm github.com/biogo/biogo/seq > github.com/biogo/biogo/seq/alignment github.com/biogo/biogo/seq/linear > github.com/biogo/biogo/seq/multi github.com/biogo/biogo/seq/quality > github.com/biogo/biogo/seq/sequtils github.com/biogo/biogo/util > github.com/biogo/biogo > internal/unsafeheader > internal/cpu > internal/abi > internal/goexperiment > runtime/internal/atomic > runtime/internal/sys > internal/itoa > runtime/internal/math > math/bits > unicode/utf8 > internal/bytealg > internal/race > sync/atomic > unicode > math > encoding > github.com/biogo/store/llrb > runtime > image/color > internal/reflectlite > sync > internal/testlog > math/rand > errors > sort > strconv > io > internal/oserror > syscall > path > container/heap > strings > text/tabwriter > hash > reflect > bytes > github.com/biogo/biogo/feat > github.com/biogo/biogo/io/featio > bufio > github.com/biogo/store/interval > internal/syscall/unix > time > internal/syscall/execenv > hash/adler32 > github.com/biogo/biogo/feat/gene > io/fs > internal/poll > encoding/binary > internal/fmtsort > os > io/ioutil > fmt > github.com/biogo/biogo/alphabet > encoding/csv >
Bug#997200: marked as done (edk2: FTBFS: cc1: error: ‘-mfloat-abi=hard’: selected architecture lacks an FPU)
Your message dated Mon, 25 Oct 2021 20:49:34 + with message-id and subject line Bug#997200: fixed in edk2 2021.08-3 has caused the Debian Bug report #997200, regarding edk2: FTBFS: cc1: error: ‘-mfloat-abi=hard’: selected architecture lacks an FPU 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.) -- 997200: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997200 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: edk2 Version: 2021.08-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[3]: Entering directory > '/<>/Build/ArmVirtQemu-ARM/RELEASE_GCC5/ARM/MdePkg/Library/UefiDevicePathLibDevicePathProtocol/UefiDevicePathLibDevicePathProtocol' > "arm-linux-gnueabihf-gcc" -MMD -MF > /<>/Build/ArmVirtQemu-ARM/RELEASE_GCC5/ARM/MdePkg/Library/UefiDevicePathLibDevicePathProtocol/UefiDevicePathLibDevicePathProtocol/OUTPUT/UefiDevicePathLib.obj.deps > -mthumb -march=armv7-a -g -Os -fshort-wchar -fno-builtin > -fno-strict-aliasing -Wall -Werror -Wno-array-bounds -include AutoGen.h > -fno-common -mlittle-endian -mabi=aapcs -fno-short-enums -funsigned-char > -ffunction-sections -fdata-sections -fomit-frame-pointer -Wno-address -mthumb > -mfloat-abi=soft -fno-pic -fno-pie -fstack-protector -mword-relocations -flto > -Wno-unused-but-set-variable -Wno-unused-const-variable -DMDEPKG_NDEBUG > -DDISABLE_NEW_DEPRECATED_INTERFACES -D ENABLE_MD5_DEPRECATED_INTERFACES -c -o > /<>/Build/ArmVirtQemu-ARM/RELEASE_GCC5/ARM/MdePkg/Library/UefiDevicePathLibDevicePathProtocol/UefiDevicePathLibDevicePathProtocol/OUTPUT/./UefiDevicePathLib.obj > -I/<>/MdePkg/Library/UefiDevicePathLibDevicePathProtocol > -I/<>/Build/ArmVirtQemu-ARM/RELEASE_GCC5/ARM/MdePkg/Library/UefiDevicePathLibDevicePathProtocol/UefiDevicePathLibDevicePathProtocol/DEBUG > -I/<>/MdePkg -I/<>/MdePkg/Include > -I/<>/MdePkg/Test/UnitTest/Include > -I/<>/MdePkg/Include/Arm > /<>/MdePkg/Library/UefiDevicePathLibDevicePathProtocol/UefiDevicePathLib.c > rm -f > /<>/Build/ArmVirtQemu-ARM/RELEASE_GCC5/ARM/MdePkg/Library/UefiDriverEntryPoint/UefiDriverEntryPoint/OUTPUT/UefiDriverEntryPoint.lib > "arm-linux-gnueabihf-gcc-ar" cr > /<>/Build/ArmVirtQemu-ARM/RELEASE_GCC5/ARM/MdePkg/Library/UefiDriverEntryPoint/UefiDriverEntryPoint/OUTPUT/UefiDriverEntryPoint.lib > > @/<>/Build/ArmVirtQemu-ARM/RELEASE_GCC5/ARM/MdePkg/Library/UefiDriverEntryPoint/UefiDriverEntryPoint/OUTPUT/object_files.lst > "arm-linux-gnueabihf-gcc" -MMD -MF > /<>/Build/ArmVirtQemu-ARM/RELEASE_GCC5/ARM/ArmPkg/Library/CompilerIntrinsicsLib/CompilerIntrinsicsLib/OUTPUT/Arm/ashldi3.obj.deps > -mthumb -march=armv7-a -E -x assembler-with-cpp -include AutoGen.h > -DOPENSBI_EXTERNAL_SBI_TYPES=OpensbiTypes.h > -I/<>/ArmPkg/Library/CompilerIntrinsicsLib/Arm > -I/<>/ArmPkg/Library/CompilerIntrinsicsLib > -I/<>/Build/ArmVirtQemu-ARM/RELEASE_GCC5/ARM/ArmPkg/Library/CompilerIntrinsicsLib/CompilerIntrinsicsLib/DEBUG > -I/<>/MdePkg -I/<>/MdePkg/Include > -I/<>/MdePkg/Test/UnitTest/Include > -I/<>/MdePkg/Include/Arm -I/<>/ArmPkg > -I/<>/ArmPkg/Include > /<>/ArmPkg/Library/CompilerIntrinsicsLib/Arm/ashldi3.S > > /<>/Build/ArmVirtQemu-ARM/RELEASE_GCC5/ARM/ArmPkg/Library/CompilerIntrinsicsLib/CompilerIntrinsicsLib/OUTPUT/Arm/ashldi3.ii > make[3]: Leaving directory > '/<>/Build/ArmVirtQemu-ARM/RELEASE_GCC5/ARM/MdePkg/Library/UefiDriverEntryPoint/UefiDriverEntryPoint' > Building ... /<>/MdePkg/Library/BasePrintLib/BasePrintLib.inf > [ARM] > cc1: error: ‘-mfloat-abi=hard’: selected architecture lacks an FPU > make[3]: *** [GNUmakefile:456: > /<>/Build/ArmVirtQemu-ARM/RELEASE_GCC5/ARM/ArmPkg/Library/CompilerIntrinsicsLib/CompilerIntrinsicsLib/OUTPUT/Arm/ashldi3.obj] > Error 1 The full build log is available from: http://qa-logs.debian.net/2021/10/23/edk2_2021.08-2_unstable.log 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 marking 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: edk2 Source-Version: 2021.08-3 Done: dann frazier We believe that the bug you reported is fixed in the latest version of edk2, which is due to be installed in the Debian FTP
Bug#997757: kxd: FTBFS: go: go.mod file not found in current directory or any parent directory; see 'go help modules'
On Sun, Oct 24, 2021 at 01:37:43PM +0200, Lucas Nussbaum wrote: Source: kxd Version: 0.15-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): make[1]: Entering directory '/<>' go build -o ./out/kxd ./kxd go build --tags netgo -a -o ./out/kxc ./kxc go build -o ./out/kxgencert ./kxgencert go: go.mod file not found in current directory or any parent directory; see 'go help modules' make[1]: *** [Makefile:17: kxc] Error 1 This is because kxd has no go.mod file (it wasn't needed before). I've added one upstream: Browse: https://blitiri.com.ar/git/r/kxd/c/e5b1abe3b5dc235b083953e8fba01a0acf53e484/ Raw patch: https://blitiri.com.ar/git/r/kxd/c/e5b1abe3b5dc235b083953e8fba01a0acf53e484.patch I'll add it to the Debian package later, unless someone else gets to it first :) Thanks! Alberto
Bug#997847: golang-github-hashicorp-go-slug: autopkgtest regression: testdata/archive-dir: no such file or directory
Source: golang-github-hashicorp-go-slug Version: 0.7.0-1 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of golang-github-hashicorp-go-slug the autopkgtest of golang-github-hashicorp-go-slug fails in testing when that autopkgtest is run with the binary packages of golang-github-hashicorp-go-slug from unstable. It passes when run with only packages from testing. In tabular form: passfail golang-github-hashicorp-go-slug from testing0.7.0-1 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration to testing [1]. Can you please investigate the situation and fix it? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=golang-github-hashicorp-go-slug https://ci.debian.net/data/autopkgtest/testing/amd64/g/golang-github-hashicorp-go-slug/16196086/log.gz [info] Testing github.com/hashicorp/go-slug... [info] Source code installed by binary package, overriding dh_auto_configure... dh build --buildsystem=golang --with=golang dh_update_autotools_config -O--buildsystem=golang dh_autoreconf -O--buildsystem=golang debian/rules override_dh_auto_configure make[1]: Entering directory '/tmp/autopkgtest-lxc.3snypp0h/downtmp/autopkgtest_tmp' mkdir -p "obj-x86_64-linux-gnu" cp -a /usr/share/gocode/src "obj-x86_64-linux-gnu" make[1]: Leaving directory '/tmp/autopkgtest-lxc.3snypp0h/downtmp/autopkgtest_tmp' dh_auto_build -O--buildsystem=golang cd obj-x86_64-linux-gnu && go install -trimpath -v -p 48 github.com/hashicorp/go-slug internal/unsafeheader runtime/internal/sys internal/goexperiment internal/abi unicode/utf8 sync/atomic internal/race internal/itoa internal/cpu math/bits runtime/internal/atomic unicode runtime/internal/math internal/bytealg math runtime internal/reflectlite sync internal/testlog runtime/cgo errors sort internal/oserror io path strconv syscall hash bytes strings hash/crc32 reflect bufio regexp/syntax internal/syscall/execenv internal/syscall/unix time regexp io/fs internal/poll os internal/fmtsort encoding/binary fmt path/filepath os/user text/scanner compress/flate compress/gzip archive/tar github.com/hashicorp/go-slug dh_auto_test -O--buildsystem=golang cd obj-x86_64-linux-gnu && go test -vet=off -v -p 48 github.com/hashicorp/go-slug === RUN TestPackWithoutIgnoring slug_test.go:255: err: lstat testdata/archive-dir: no such file or directory --- FAIL: TestPackWithoutIgnoring (0.00s) === RUN TestUnpack slug_test.go:321: err: lstat testdata/archive-dir: no such file or directory --- FAIL: TestUnpack (0.00s) === RUN TestUnpackDuplicateNoWritePerm --- PASS: TestUnpackDuplicateNoWritePerm (0.00s) === RUN TestUnpackErrorOnUnhandledType --- PASS: TestUnpackErrorOnUnhandledType (0.00s) === RUN TestUnpackMaliciousSymlinks === RUN TestUnpackMaliciousSymlinks/symlink_with_absolute_path === RUN TestUnpackMaliciousSymlinks/symlink_with_external_target === RUN TestUnpackMaliciousSymlinks/symlink_with_nested_external_target === RUN TestUnpackMaliciousSymlinks/zipslip_vulnerability === RUN TestUnpackMaliciousSymlinks/nested_symlinks_within_symlinked_dir === RUN TestUnpackMaliciousSymlinks/regular_file_through_symlink === RUN TestUnpackMaliciousSymlinks/directory_through_symlink --- PASS: TestUnpackMaliciousSymlinks (0.01s) --- PASS: TestUnpackMaliciousSymlinks/symlink_with_absolute_path (0.00s) --- PASS: TestUnpackMaliciousSymlinks/symlink_with_external_target (0.00s) --- PASS: TestUnpackMaliciousSymlinks/symlink_with_nested_external_target (0.00s) --- PASS: TestUnpackMaliciousSymlinks/zipslip_vulnerability (0.00s) --- PASS: TestUnpackMaliciousSymlinks/nested_symlinks_within_symlinked_dir (0.00s) --- PASS: TestUnpackMaliciousSymlinks/regular_file_through_symlink (0.00s) --- PASS: TestUnpackMaliciousSymlinks/directory_through_symlink (0.00s) === RUN TestUnpackMaliciousFiles === RUN TestUnpackMaliciousFiles/filename_containing_path_traversal === RUN TestUnpackMaliciousFiles/should_fail_before_attempting_to_create_directories --- PASS: TestUnpackMaliciousFiles (0.00s) --- PASS: TestUnpackMaliciousFiles/filename_containing_path_traversal (0.00s) --- PASS: TestUnpackMaliciousFiles/should_fail_before_attempting_to_create_directories (0.00s) === RUN TestCheckFileMode === RUN TestCheckFileMode/includes_regular_files === RUN TestCheckFileMode/includes_directories === RUN TestCheckFileMode/includes_symlinks === RUN TestCheckFileMode/excludes_unrecognized_modes --- PASS: TestCheckFileMode (0.00s) --- PASS: TestCheckFileMode/includes_regular_files (0.00s) --- PASS:
Bug#997846: httpbin: autopkgtest regression: KeyError: 'Content-Length'
Source: httpbin Version: 0.7.0+dfsg-1 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of httpbin the autopkgtest of httpbin fails in testing when that autopkgtest is run with the binary packages of httpbin from unstable. It passes when run with only packages from testing. In tabular form: passfail httpbinfrom testing0.7.0+dfsg-1 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration to testing [1]. Can you please investigate the situation and fix it? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=httpbin https://ci.debian.net/data/autopkgtest/testing/amd64/h/httpbin/15762030/log.gz ../usr/lib/python3/dist-packages/flask/json/__init__.py:211: DeprecationWarning: Importing 'itsdangerous.json' is deprecated and will be removed in ItsDangerous 2.1. Use Python's 'json' module instead. rv = _json.dumps(obj, **kwargs) E.E.. == ERROR: test_anything (__main__.HttpbinTestCase) -- Traceback (most recent call last): File "/tmp/autopkgtest-lxc.nx05yeyf/downtmp/autopkgtest_tmp/test_httpbin.py", line 161, in test_anything self.assertEqual(data['headers']['Content-Length'], '0') KeyError: 'Content-Length' == ERROR: test_get (__main__.HttpbinTestCase) -- Traceback (most recent call last): File "/tmp/autopkgtest-lxc.nx05yeyf/downtmp/autopkgtest_tmp/test_httpbin.py", line 147, in test_get self.assertEqual(data['headers']['Content-Length'], '0') KeyError: 'Content-Length' -- Ran 63 tests in 5.996s FAILED (errors=2) autopkgtest [03:23:23]: test command1 OpenPGP_signature Description: OpenPGP digital signature
Bug#997845: growlight: autopkgtest regression: log repeats until it times out
Source: growlight Version: 1.2.37-2 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression timesout Dear maintainer(s), With a recent upload of growlight the autopkgtest of growlight fails in testing when that autopkgtest is run with the binary packages of growlight from unstable. It passes when run with only packages from testing. In tabular form: passfail growlight from testing1.2.37-2 all others from testingfrom testing I copied some of the output at the bottom of this report. The message is repeated over and over again until autopkgtest timesout. Currently this regression is blocking the migration to testing [1]. Can you please investigate the situation and fix it? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=growlight https://ci.debian.net/data/autopkgtest/testing/amd64/g/growlight/16172667/log.gz growlight 1.2.37 libblkid 2.37.2, libpci 0x30700, libdm 1.02.175 (2021-01-08) No ZFS support in this build. Watching /sys/class/block/ on fd 1 scanning /sys/class/block/ on 8... nvme0n1 -> ../../devices/pci:00/:00:04.0/nvme/nvme0/nvme0n1 Numa node 0 (/sys/devices/pci:00/:00:04.0//numa_node) /sys/class/block/ blocks on 4 devices for up to 1s Controller: Amazon.com, Inc. NVMe EBS Controller nvme0n1p15 -> ../../devices/pci:00/:00:04.0/nvme/nvme0/nvme0n1/nvme0n1p15 nvme0n1p1 -> ../../devices/pci:00/:00:04.0/nvme/nvme0/nvme0n1/nvme0n1p1 Controller: Amazon.com, Inc. NVMe EBS Controller Not recursing on partition nvme0n1p15 Couldn't get a revision for nvme0n1 (No such file or directory) Model: Amazon Elastic Block Store revision n/a S/N n/a type 0 Controller: Amazon.com, Inc. NVMe EBS Controller nvme0n1p14 -> ../../devices/pci:00/:00:04.0/nvme/nvme0/nvme0n1/nvme0n1p14 Not recursing on partition nvme0n1p1 Controller: Amazon.com, Inc. NVMe EBS Controller Not recursing on partition nvme0n1p14 Partition 1 at nvme0n1p1 Partition 14 at nvme0n1p14 Partition 15 at nvme0n1p15 Couldn't open /dev/nvme0n1 (No such file or directory) Couldn't inotify on /dev/md/ (No such file or directory) Couldn't inotify on /dev/disk/by-path/ (No such file or directory) Couldn't inotify on /dev/disk/by-id/ (No such file or directory) virtual filesystem support: sysfs virtual filesystem support: tmpfs virtual filesystem support: bdev virtual filesystem support: proc virtual filesystem support: cgroup virtual filesystem support: cgroup2 virtual filesystem support: cpuset virtual filesystem support: devtmpfs virtual filesystem support: debugfs virtual filesystem support: tracefs virtual filesystem support: securityfs virtual filesystem support: sockfs virtual filesystem support: bpf virtual filesystem support: pipefs virtual filesystem support: ramfs virtual filesystem support: hugetlbfs virtual filesystem support: devpts filesystem support: ext3 filesystem support: ext2 filesystem support: ext4 virtual filesystem support: mqueue virtual filesystem support: pstore virtual filesystem support: autofs virtual filesystem support: configfs filesystem support: fuseblk virtual filesystem support: fuse virtual filesystem support: fusectl filesystem support: vfat virtual filesystem support: binfmt_misc virtual filesystem support: overlay virtual filesystem support: rpc_pipefs virtual filesystem support: nfsd nvme0n1p1 -> ../../devices/pci:00/:00:04.0/nvme/nvme0/nvme0n1/nvme0n1p1 Controller: Amazon.com, Inc. NVMe EBS Controller Not recursing on partition nvme0n1p1 nvme0n1p1 -> ../../devices/pci:00/:00:04.0/nvme/nvme0/nvme0n1/nvme0n1p1 Controller: Amazon.com, Inc. NVMe EBS Controller Not recursing on partition nvme0n1p1 Couldn't read link at /sys/class/block/cgroup (No such file or directory) virtfs cgroup2 at /sys/fs/cgroup Couldn't read link at /sys/class/block/lxcfs (No such file or directory) virtfs fuse.lxcfs at /proc/cpuinfo Couldn't read link at /sys/class/block/lxcfs (No such file or directory) virtfs fuse.lxcfs at /proc/diskstats Couldn't read link at /sys/class/block/lxcfs (No such file or directory) virtfs fuse.lxcfs at /proc/loadavg Couldn't read link at /sys/class/block/lxcfs (No such file or directory) virtfs fuse.lxcfs at /proc/meminfo Couldn't read link at /sys/class/block/lxcfs (No such file or directory) virtfs fuse.lxcfs at /proc/stat Couldn't read link at /sys/class/block/lxcfs (No such file or directory) virtfs fuse.lxcfs at /proc/swaps Couldn't read link at /sys/class/block/lxcfs (No such file or directory) virtfs fuse.lxcfs at /proc/uptime Couldn't read link at /sys/class/block/lxcfs (No such file or directory) virtfs fuse.lxcfs at /sys/devices/system/cpu/online Couldn't read link at /sys/class/block/hugetlbfs
Bug#997201: Fio ftbfs should be fixed in 3.28 or later
Hi, already had some private mail exchange with Martin, so just for public reference: Looks like https://github.com/axboe/fio/commit/382975557e632efb506836bc1709789e615c9094 is the solution to this issue. This is part of the 3.28 release. I guess we work on packaging a new upstream release soon. Sven
Bug#996118: marked as done (pry: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: NoMethodError:)
Your message dated Mon, 25 Oct 2021 19:50:54 +
with message-id
and subject line Bug#996118: fixed in pry 0.13.1-2
has caused the Debian Bug report #996118,
regarding pry: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed:
NoMethodError:
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.)
--
996118: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996118
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pry
Version: 0.13.1-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.0
Hi,
We are about to enable building against ruby3.0 on unstable. During a test
rebuild, pry was found to fail to build in that situation.
To reproduce this locally, you need to install ruby-all-dev from experimental
on an unstable system or build chroot.
Relevant part (hopefully):
> NoMethodError:
>undefined method `to_json' for nil:NilClass
> # (eval):1:in `block (3 levels) in '
> # ./spec/syntax_checking_spec.rb:52:in `eval'
> # ./spec/syntax_checking_spec.rb:52:in `block (3 levels) in (required)>'
>
> Finished in 8.88 seconds (files took 0.60044 seconds to load)
> 1431 examples, 2 failures, 6 pending
>
> Failed examples:
>
> rspec './spec/syntax_checking_spec.rb[1:20]' # Pry should raise an error on
> invalid syntax like ["puts {'key'=>'val'}.to_json"]
> rspec './spec/syntax_checking_spec.rb[1:21]' # Pry should display correct
> number of errors on invalid syntax like ["puts {'key'=>'val'}.to_json"]
>
> Randomized with seed 7166
>
> /usr/bin/ruby3.0
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib
> /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/exe/rspec
> --pattern ./spec/\*\*/\*_spec.rb --format documentation failed
> ERROR: Test "ruby3.0" failed:
The build full is available at
https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/pry/pry_0.13.1-1+rebuild1633374393_amd64.build.txt
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: pry
Source-Version: 0.13.1-2
Done: Lucas Kanashiro
We believe that the bug you reported is fixed in the latest version of
pry, 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 996...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Lucas Kanashiro (supplier of updated pry 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: Mon, 25 Oct 2021 16:19:19 -0300
Source: pry
Architecture: source
Version: 0.13.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team
Changed-By: Lucas Kanashiro
Closes: 996118
Changes:
pry (0.13.1-2) unstable; urgency=medium
.
* Team upload.
.
[ Cédric Boutillier ]
* Update team name
.
[ Debian Janitor ]
* Update watch file format version to 4.
* Update standards version to 4.5.1, no changes needed.
.
[ Lucas Kanashiro ]
* Add patch to allow test execution with ruby3.0 (Closes: #996118)
* Declare compliance with Debian Policy 4.6.0
Checksums-Sha1:
f1fd324aad3d9d8423f68a07312653c3e0113141 2070 pry_0.13.1-2.dsc
3df1f50b1197b7a3c2fd6b6af6e56bac7cbf5eee 10604 pry_0.13.1-2.debian.tar.xz
Checksums-Sha256:
2e7d8463c1603bffdb59184580da9d10129fb6d870eceaf323acbc4118e5a601 2070
pry_0.13.1-2.dsc
60ce2922faf037340b0dd25bcc1a40602b2ffdb247efdb4a1030bb8d3d6aa6e8 10604
pry_0.13.1-2.debian.tar.xz
Files:
e38b63c63e2708a93bfa1b70ab1ee212 2070 ruby optional pry_0.13.1-2.dsc
240614771c99e37d781002f9c9e6282c 10604 ruby optional pry_0.13.1-2.debian.tar.xz
-BEGIN PGP SIGNATURE-
iQJJBAEBCAAzFiEEjtbD+LrJ23/BMKhw+COicpiDyXwFAmF3BJIVHGthbmFzaGly
b0BkZWJpYW4ub3JnAAoJEPgjonKYg8l8aEsP/1LygoGs+/yn/Ak8K2XShzGc/ws0
OIbu2tofkQwitI1uNmGgIYcrGVlm4fm1XxKpraOMyBw8lN7Ru5Spsyvujz8qnx3M
I6h7WBUGV3rSjiSYHFRJzYdpcCxMCP+/5AoTdc37x7eDh30KzcCEOPD2tSKGrbz9
0PFzG2bZ4GCGJjwShyYWDnazaiPfcb5Lg80UMJQ/C7q/tdZpJ9djdoAfw8TY33ST
TmVO6wai46STqg1RhXU9HnmK1KIa8sFX5d2M4cCk4wnPBxZ+zFFmDUAOgkGaWMcD
GXoHk/hdFzskbDzelEj2cRXh9h71S9vApJmQiTzwT3Y7ci9TESF9J2tO4jO/oKQP
Bug#984232: Diagnosis
Looks like this is because of a dynamic exception specification, which is forbidden by C++17. I'll see if upstream has fixed this, and if not, I'll just modify the packaging to build in C++14 mode. Ryan OpenPGP_signature Description: OpenPGP digital signature
Bug#997530: marked as done (mrpt: FTBFS: make[4]: *** No rule to make target '/usr/lib/x86_64-linux-gnu/libopencv_calib3d.so.4.5.3', needed by 'lib/libmrpt-ros1bridge.so.2.2.0'. Stop.)
Your message dated Mon, 25 Oct 2021 19:37:15 + with message-id and subject line Bug#997519: fixed in ros-catkin 0.8.10-6 has caused the Debian Bug report #997519, regarding mrpt: FTBFS: make[4]: *** No rule to make target '/usr/lib/x86_64-linux-gnu/libopencv_calib3d.so.4.5.3', needed by 'lib/libmrpt-ros1bridge.so.2.2.0'. Stop. 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.) -- 997519: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997519 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mrpt Version: 1:2.2.0-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[4]: Entering directory '/<>/obj-x86_64-linux-gnu' > [ 66%] Building CXX object > apps/rawlog-edit/CMakeFiles/rawlog-edit.dir/rawlog-edit_main.cpp.o > cd /<>/obj-x86_64-linux-gnu/apps/rawlog-edit && /usr/bin/c++ > -I/usr/include/suitesparse -I/<>/libs/obs/include > -I/<>/libs/opengl/include -I/<>/libs/poses/include > -I/<>/libs/bayes/include -I/<>/libs/math/include > -I/<>/libs/core/include > -I/<>/obj-x86_64-linux-gnu/include/mrpt-configuration > -I/<>/libs/containers/include > -I/<>/libs/typemeta/include > -I/<>/libs/serialization/include > -I/<>/libs/rtti/include -I/<>/libs/random/include > -I/<>/libs/system/include -I/<>/libs/config/include > -I/<>/libs/expr/include -I/<>/libs/img/include > -I/<>/libs/io/include -I/<>/libs/tfest/include > -I/<>/libs/topography/include > -I/<>/libs/maps/include -I/<>/libs/graphs/include > -I/<>/libs/vision/include -I/<>/libs/tclap/include > -isystem /usr/include/eigen3 -g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > -D_FORTIFY_SOURCE=2 -O3 -DNDEBUG -Wall -Wabi=11 -Wno-long-long > -Wno-variadic-macros -Wshadow -Wreturn-local-addr -Werror=return-local-addr > -Wno-ignored-attributes -Wno-int-in-bool-context -Wno-write-strings > -Wreturn-type -Werror=return-type -Wformat -Werror=format-security -Wextra > -Wtype-limits -Wcast-align -Wparentheses -Wno-unused-parameter -mtune=native > -O3 -msse2 -pthread -MD -MT > apps/rawlog-edit/CMakeFiles/rawlog-edit.dir/rawlog-edit_main.cpp.o -MF > CMakeFiles/rawlog-edit.dir/rawlog-edit_main.cpp.o.d -o > CMakeFiles/rawlog-edit.dir/rawlog-edit_main.cpp.o -c > /<>/apps/rawlog-edit/rawlog-edit_main.cpp > [ 66%] Building CXX object > apps/SceneViewer3D/CMakeFiles/SceneViewer3D.dir/CDialogOptions.cpp.o > cd /<>/obj-x86_64-linux-gnu/apps/SceneViewer3D && /usr/bin/c++ > -DWXUSINGDLL -D_FILE_OFFSET_BITS=64 -D__WXGTK__ -I/usr/include/suitesparse > -I/<>/3rdparty/wxThings -I/<>/libs/opengl/include > -I/<>/libs/poses/include -I/<>/libs/bayes/include > -I/<>/libs/math/include -I/<>/libs/core/include > -I/<>/obj-x86_64-linux-gnu/include/mrpt-configuration > -I/<>/libs/containers/include > -I/<>/libs/typemeta/include > -I/<>/libs/serialization/include > -I/<>/libs/rtti/include -I/<>/libs/random/include > -I/<>/libs/system/include -I/<>/libs/config/include > -I/<>/libs/expr/include -I/<>/libs/img/include > -I/<>/libs/io/include -I/<>/libs/gui/include > -I/<>/3rdparty/nanogui/ext/nanovg/src > -I/<>/3rdparty/nanogui/include > -I/<>/obj-x86_64-linux-gnu/3rdparty/nanogui > -I/<>/libs/maps/include -I/<>/libs/obs/include > -I/<>/libs/tfest/include -I/<>/libs/graphs/include > -isystem /usr/lib/x86_64-linux-gnu/wx/include/gtk3-unicode-3.0 -isystem > /usr/include/wx-3.0 -isystem /usr/include/eigen3 -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -O3 -DNDEBUG -Wall > -Wabi=11 -Wno-long-long -Wno-variadic-macros -Wshadow -Wreturn-local-addr > -Werror=return-local-addr -Wno-ignored-attributes -Wno-int-in-bool-context > -Wno-write-strings -Wreturn-type -Werror=return-type -Wformat > -Werror=format-security -Wextra -Wtype-limits -Wcast-align -Wparentheses > -Wno-unused-parameter -mtune=native -O3 -msse2 -pthread -MD -MT > apps/SceneViewer3D/CMakeFiles/SceneViewer3D.dir/CDialogOptions.cpp.o -MF > CMakeFiles/SceneViewer3D.dir/CDialogOptions.cpp.o.d -o > CMakeFiles/SceneViewer3D.dir/CDialogOptions.cpp.o -c > /<>/apps/SceneViewer3D/CDialogOptions.cpp > [ 66%] Building CXX object > libs/ros1bridge/CMakeFiles/ros1bridge.dir/src/pose.cpp.o > cd /<>/obj-x86_64-linux-gnu/libs/ros1bridge && /usr/bin/c++ > -DMRPT_HAVE_PCL_CONVERSIONS=0 -DROSCONSOLE_BACKEND_LOG4CXX > -DROS_PACKAGE_NAME=\"MRPT\"
Bug#997527: marked as done (ros-opencv-apps: FTBFS: make[3]: *** No rule to make target '/usr/lib/x86_64-linux-gnu/libopencv_calib3d.so.4.5.3', needed by 'devel/lib/opencv_apps/fback_flow'. Stop.)
Your message dated Mon, 25 Oct 2021 19:37:15 + with message-id and subject line Bug#997519: fixed in ros-catkin 0.8.10-6 has caused the Debian Bug report #997519, regarding ros-opencv-apps: FTBFS: make[3]: *** No rule to make target '/usr/lib/x86_64-linux-gnu/libopencv_calib3d.so.4.5.3', needed by 'devel/lib/opencv_apps/fback_flow'. Stop. 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.) -- 997519: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997519 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ros-opencv-apps Version: 2.0.2-4 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 ftbfs-bookworm 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]: *** No rule to make target > '/usr/lib/x86_64-linux-gnu/libopencv_calib3d.so.4.5.3', needed by > 'devel/lib/opencv_apps/lk_flow'. Stop. > make[3]: *** Waiting for unfinished jobs > make[3]: *** No rule to make target > '/usr/lib/x86_64-linux-gnu/libopencv_calib3d.so.4.5.3', needed by > 'devel/lib/opencv_apps/fback_flow'. Stop. > make[3]: *** Waiting for unfinished jobs > [ 1%] Building CXX object CMakeFiles/phase_corr_exe.dir/phase_corr.cpp.o > [ 1%] Building CXX object > CMakeFiles/watershed_segmentation_exe.dir/watershed_segmentation.cpp.o > [ 1%] Building CXX object CMakeFiles/lk_flow_exe.dir/lk_flow.cpp.o > /usr/bin/c++ -DROSCONSOLE_BACKEND_LOG4CXX -DROS_BUILD_SHARED_LIBS=1 > -DROS_PACKAGE_NAME=\"opencv_apps\" -I/<>/include > -I/usr/include/xmlrpcpp -isystem > /<>/obj-x86_64-linux-gnu/devel/include -isystem > /usr/include/opencv4 -g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > -D_FORTIFY_SOURCE=2 -std=gnu++11 -MD -MT > CMakeFiles/phase_corr_exe.dir/phase_corr.cpp.o -MF > CMakeFiles/phase_corr_exe.dir/phase_corr.cpp.o.d -o > CMakeFiles/phase_corr_exe.dir/phase_corr.cpp.o -c > /<>/obj-x86_64-linux-gnu/phase_corr.cpp > [ 1%] Building CXX object CMakeFiles/fback_flow_exe.dir/fback_flow.cpp.o > /usr/bin/c++ -DROSCONSOLE_BACKEND_LOG4CXX -DROS_BUILD_SHARED_LIBS=1 > -DROS_PACKAGE_NAME=\"opencv_apps\" -I/<>/include > -I/usr/include/xmlrpcpp -isystem > /<>/obj-x86_64-linux-gnu/devel/include -isystem > /usr/include/opencv4 -g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > -D_FORTIFY_SOURCE=2 -std=gnu++11 -MD -MT > CMakeFiles/watershed_segmentation_exe.dir/watershed_segmentation.cpp.o -MF > CMakeFiles/watershed_segmentation_exe.dir/watershed_segmentation.cpp.o.d -o > CMakeFiles/watershed_segmentation_exe.dir/watershed_segmentation.cpp.o -c > /<>/obj-x86_64-linux-gnu/watershed_segmentation.cpp > /usr/bin/c++ -DROSCONSOLE_BACKEND_LOG4CXX -DROS_BUILD_SHARED_LIBS=1 > -DROS_PACKAGE_NAME=\"opencv_apps\" -I/<>/include > -I/usr/include/xmlrpcpp -isystem > /<>/obj-x86_64-linux-gnu/devel/include -isystem > /usr/include/opencv4 -g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > -D_FORTIFY_SOURCE=2 -std=gnu++11 -MD -MT > CMakeFiles/lk_flow_exe.dir/lk_flow.cpp.o -MF > CMakeFiles/lk_flow_exe.dir/lk_flow.cpp.o.d -o > CMakeFiles/lk_flow_exe.dir/lk_flow.cpp.o -c > /<>/obj-x86_64-linux-gnu/lk_flow.cpp > /usr/bin/c++ -DROSCONSOLE_BACKEND_LOG4CXX -DROS_BUILD_SHARED_LIBS=1 > -DROS_PACKAGE_NAME=\"opencv_apps\" -I/<>/include > -I/usr/include/xmlrpcpp -isystem > /<>/obj-x86_64-linux-gnu/devel/include -isystem > /usr/include/opencv4 -g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > -D_FORTIFY_SOURCE=2 -std=gnu++11 -MD -MT > CMakeFiles/fback_flow_exe.dir/fback_flow.cpp.o -MF > CMakeFiles/fback_flow_exe.dir/fback_flow.cpp.o.d -o > CMakeFiles/fback_flow_exe.dir/fback_flow.cpp.o -c > /<>/obj-x86_64-linux-gnu/fback_flow.cpp > make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu' > make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu' > make[2]: *** [CMakeFiles/Makefile2:242: CMakeFiles/phase_corr_exe.dir/all] > Error 2 The full build log is available from: http://qa-logs.debian.net/2021/10/23/ros-opencv-apps_2.0.2-4_unstable.log 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 marking it as 'affects'-ing this package. See
Bug#997519: marked as done (ros-image-pipeline: FTBFS: make[3]: *** No rule to make target '/usr/lib/x86_64-linux-gnu/libopencv_calib3d.so.4.5.3', needed by 'devel/lib/image_view/video_recorder'. Sto
Your message dated Mon, 25 Oct 2021 19:37:15 + with message-id and subject line Bug#997519: fixed in ros-catkin 0.8.10-6 has caused the Debian Bug report #997519, regarding ros-image-pipeline: FTBFS: make[3]: *** No rule to make target '/usr/lib/x86_64-linux-gnu/libopencv_calib3d.so.4.5.3', needed by 'devel/lib/image_view/video_recorder'. Stop. 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.) -- 997519: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997519 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ros-image-pipeline Version: 1.15.3-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 ftbfs-bookworm 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]: *** No rule to make target > '/usr/lib/x86_64-linux-gnu/libopencv_calib3d.so.4.5.3', needed by > 'devel/lib/image_view/video_recorder'. Stop. > make[3]: *** Waiting for unfinished jobs > [ 18%] Building CXX object > image_view/CMakeFiles/video_recorder.dir/src/nodes/video_recorder.cpp.o > cd /<>/obj-x86_64-linux-gnu/image_view && /usr/bin/c++ > -DROSCONSOLE_BACKEND_LOG4CXX -DROS_BUILD_SHARED_LIBS=1 > -DROS_PACKAGE_NAME=\"image_view\" -I/usr/include/xmlrpcpp > -I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 > -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 > -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/gio-unix-2.0 > -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/harfbuzz > -I/usr/include/fribidi -I/usr/include/atk-1.0 -I/usr/include/pixman-1 > -I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 > -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libmount -I/usr/include/blkid > -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -isystem > /<>/obj-x86_64-linux-gnu/devel/include -isystem > /usr/include/opencv4 -g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > -D_FORTIFY_SOURCE=2 -MD -MT > image_view/CMakeFiles/video_recorder.dir/src/nodes/video_recorder.cpp.o -MF > CMakeFiles/video_recorder.dir/src/nodes/video_recorder.cpp.o.d -o > CMakeFiles/video_recorder.dir/src/nodes/video_recorder.cpp.o -c > /<>/image_view/src/nodes/video_recorder.cpp > make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu' > make[2]: *** [CMakeFiles/Makefile2:1452: > image_rotate/CMakeFiles/image_rotate_exe.dir/all] Error 2 The full build log is available from: http://qa-logs.debian.net/2021/10/23/ros-image-pipeline_1.15.3-1_unstable.log 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 marking 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: ros-catkin Source-Version: 0.8.10-6 Done: Jochen Sprickerhof We believe that the bug you reported is fixed in the latest version of ros-catkin, 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 997...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jochen Sprickerhof (supplier of updated ros-catkin 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: Mon, 25 Oct 2021 21:26:08 +0200 Source: ros-catkin Architecture: source Version: 0.8.10-6 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Jochen Sprickerhof Closes: 997519 Changes: ros-catkin (0.8.10-6) unstable; urgency=medium . [ Timo Röhling ] * Add myself to uploaders * Prefer prebuilt Googletest libraries * Remove libgtest-dev from dependencies . [ Jochen Sprickerhof ] * Reduce diff size * Recover full path patch (Closes: #997519) Checksums-Sha1:
Bug#997164: marked as done (tty-solitaire: FTBFS: src/gui.c:16:3: error: format not a string literal and no format arguments [-Werror=format-security])
Your message dated Mon, 25 Oct 2021 19:37:22 + with message-id and subject line Bug#997164: fixed in tty-solitaire 1.3.1-1 has caused the Debian Bug report #997164, regarding tty-solitaire: FTBFS: src/gui.c:16:3: error: format not a string literal and no format arguments [-Werror=format-security] 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.) -- 997164: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997164 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: tty-solitaire Version: 1.3.0-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > cc -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong > -Wformat -Werror=format-security -W -Wall -pedantic -ansi -std=c99 > -DVERSION=\"1.3.0\" -fcommon -Wdate-time -D_FORTIFY_SOURCE=2 -c -o src/gui.o > src/gui.c > src/gui.c: In function ‘draw_value’: > src/gui.c:16:3: error: format not a string literal and no format arguments > [-Werror=format-security] >16 | mvwprintw(card->frame->window, 0, 0, card_values[card->value]); > | ^ > src/gui.c:18:13: error: format not a string literal and no format arguments > [-Werror=format-security] >18 | card_values[card->value]); > | ^~~ > src/gui.c: In function ‘draw_suit’: > src/gui.c:46:13: error: format not a string literal and no format arguments > [-Werror=format-security] >46 | card_suits[card->suit]); > | ^~ > src/gui.c:48:13: error: format not a string literal and no format arguments > [-Werror=format-security] >48 | card_suits[card->suit]); > | ^~ > cc1: some warnings being treated as errors > make[2]: *** [: src/gui.o] Error 1 The full build log is available from: http://qa-logs.debian.net/2021/10/23/tty-solitaire_1.3.0-2_unstable.log 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 marking 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: tty-solitaire Source-Version: 1.3.1-1 Done: Sven Wick We believe that the bug you reported is fixed in the latest version of tty-solitaire, 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 997...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sven Wick (supplier of updated tty-solitaire 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: Sat, 23 Oct 2021 23:16:14 +0200 Source: tty-solitaire Architecture: source Version: 1.3.1-1 Distribution: unstable Urgency: medium Maintainer: Sven Wick Changed-By: Sven Wick Closes: 997164 Changes: tty-solitaire (1.3.1-1) unstable; urgency=medium . * New upstream release * Drop d/patches/0001-reproducible-build.patch * d/rules: change hardening=+all to hardening=+all,-format (Closes: #997164) Checksums-Sha1: 6b752c6c9b54ca9d2680d67e7b5e12e828e81275 1729 tty-solitaire_1.3.1-1.dsc 89628d5985741e27229bd2615367b2f8cc22b2ab 280381 tty-solitaire_1.3.1.orig.tar.gz bc54feeb01687248ba64627a0fa6773a7dd489b8 2132 tty-solitaire_1.3.1-1.debian.tar.xz 396841a6d54a4103ab88a2c6772a1aecef874873 5467 tty-solitaire_1.3.1-1_source.buildinfo Checksums-Sha256: f1125130d81a876e8c5f3e7ed791a7fc2338495b515bf514ef86e55428b57adb 1729 tty-solitaire_1.3.1-1.dsc f2b80c8d5317e67db43c1dbf3b0f5f3dfea5e826c18744562615f1b1536ae433 280381 tty-solitaire_1.3.1.orig.tar.gz 794d0b6b1f949e7c22199c07c57255c817f0ce3adb9629daf4d9460dd3e08868 2132 tty-solitaire_1.3.1-1.debian.tar.xz 9cccb916e99427b04040bfa99d951a9d7feca8f8ab7014237a9224ac35829078 5467 tty-solitaire_1.3.1-1_source.buildinfo Files: 12304eda93f60806260164e0cd3fb696 1729 games optional
Bug#997834: marked as done (samtools: binary-any FTBFS)
Your message dated Mon, 25 Oct 2021 19:25:05 +
with message-id
and subject line Bug#997834: fixed in samtools 1.13-4
has caused the Debian Bug report #997834,
regarding samtools: binary-any FTBFS
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.)
--
997834: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997834
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: samtools
Version: 1.13-3
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/logs.php?pkg=samtools=1.13-3
...
dh_install
install -d debian/samtools//usr
cp --reflink=auto -a debian/tmp/usr/bin debian/samtools//usr/
install -d debian/samtools//usr/share/man
cp --reflink=auto -a debian/tmp/usr/share/man/man1
debian/samtools//usr/share/man/
install -d debian/samtools/usr/share/commonwl/
cp --reflink=auto -a ./debian/samtools-faidx.cwl
./debian/samtools-index.cwl ./debian/samtools-rmdup.cwl
./debian/samtools-sort.cwl ./debian/samtools-view.cwl
debian/samtools/usr/share/commonwl//
cp --reflink=auto -a ./debian/mans/ace2sam.1
./debian/mans/samtools.pl.1 ./debian/mans/wgsim.1
debian/samtools/usr/share/man/man1/
install -d debian/.debhelper/generated/samtools
install -d debian/.debhelper/generated/samtools-test
# Fix Perl interpreter PATH
for pscript in `grep -Rl '#!/usr/bin/env \+perl' debian/*` ; do \
sed -i '1s?#!/usr/bin/env \+perl?#!/usr/bin/perl?' ${pscript} ; \
done
# Disable the executable bit on a dataset.
chmod 0644 debian/samtools-test/usr/share/samtools/test/ampliconclip/ac_test.bed
chmod: cannot access
'debian/samtools-test/usr/share/samtools/test/ampliconclip/ac_test.bed': No
such file or directory
make[1]: *** [debian/rules:59: override_dh_install] Error 1
--- End Message ---
--- Begin Message ---
Source: samtools
Source-Version: 1.13-4
Done: Étienne Mollier
We believe that the bug you reported is fixed in the latest version of
samtools, 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 997...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Étienne Mollier (supplier of updated samtools 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: Mon, 25 Oct 2021 20:53:03 +0200
Source: samtools
Architecture: source
Version: 1.13-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team
Changed-By: Étienne Mollier
Closes: 997834
Changes:
samtools (1.13-4) unstable; urgency=medium
.
* [650b7a7] d/rules: only disable executable bit if test package is built.
(Closes: #997834)
Checksums-Sha1:
4e105039ebeaa420c52d98a88593b0f306abe028 2294 samtools_1.13-4.dsc
38e1fbacbafa420c6e8ca754f72e3ed60904c548 21636 samtools_1.13-4.debian.tar.xz
ae90e31f25c884e7b4cd28bbab4217e0273a60e0 7146 samtools_1.13-4_amd64.buildinfo
Checksums-Sha256:
21c268267337ea61f54e9d6577b3b926ee1f41a82bbad5eda2fe6f454b29370e 2294
samtools_1.13-4.dsc
6c2b240459a0d9a6798cdcc2eea06b11f039966600bbc79fe452a3115c106f24 21636
samtools_1.13-4.debian.tar.xz
108f63e8c227805310ca06a6ef48d7ade8b62c0d0aa35659e9749dec248ceeaf 7146
samtools_1.13-4_amd64.buildinfo
Files:
185312491c73d54da8b6b43f7c131345 2294 science optional samtools_1.13-4.dsc
2122d95a5770cd9d4e98d40d7356c683 21636 science optional
samtools_1.13-4.debian.tar.xz
bf360d466bca9f3699b7dfdb33c3b26a 7146 science optional
samtools_1.13-4_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQJIBAEBCgAyFiEEj5GyJ8fW8rGUjII2eTz2fo8NEdoFAmF2/qEUHGVtb2xsaWVy
QGRlYmlhbi5vcmcACgkQeTz2fo8NEdoegw/+K/Urzp6eym6fUJkFT7ZdGUXgQi8m
yk1FFuCAzLNSIK17ovKTP5M4C8qi/HUaeW9hHWWYzPz7d39wZb+fpZdyopmnHjPW
6jSvJV8iFRRV5J+D88pCyPODwaTaV5VXmA377JiCkE8hHRyVfwAAaplGUf+AupDi
+skTvRjtba7QSv0Z7xzMEMkz+OSNcF5gUyySs12fKaFNLlTEw8LD1YSYbrs1Wnep
+zbbKiyhjbvDpYlxWxmwprSJnQzZITAL9VZ3Z3UKiV0juPp83sWWGigILy+MIJMm
Rbrv1AXvgoMGvSSvfgCRlxZP5iHoc9ddqj66EWCAafTT1Is1LgNxjbaWyCOlmqq7
0uVlUqdb1Jgtxwo8il9FqtCdg6GPY0oike7b4hdyi9NqX3z9IB+jzC3OSnuToW6V
hlK/WfuWIHuO33l4y0k3PryZj4zhFNCl1ieEBVapaPVxLXHDuvbcaNaQ2+bkl0Jj
Pkbj8i8DF4MpumSpWkrHEMcQeIV34yTgFVxQjeNYkasYyaszSYw9rWzTTB279x+d
8AbrHVgAp7hgqk0F/1OJ2y7ALTnC+glCme8wMvqV6peelNlDmjEwfuJvjFIG6t6q
Processed: Re: Bug#997530: mrpt: FTBFS
Processing control commands: > reassign 997519 catkin Bug #997519 [src:ros-image-pipeline] ros-image-pipeline: FTBFS: make[3]: *** No rule to make target '/usr/lib/x86_64-linux-gnu/libopencv_calib3d.so.4.5.3', needed by 'devel/lib/image_view/video_recorder'. Stop. Bug reassigned from package 'src:ros-image-pipeline' to 'catkin'. No longer marked as found in versions ros-image-pipeline/1.15.3-1. Ignoring request to alter fixed versions of bug #997519 to the same values previously set > reassign 997527 catkin Bug #997527 [src:ros-opencv-apps] ros-opencv-apps: FTBFS: make[3]: *** No rule to make target '/usr/lib/x86_64-linux-gnu/libopencv_calib3d.so.4.5.3', needed by 'devel/lib/opencv_apps/fback_flow'. Stop. Bug reassigned from package 'src:ros-opencv-apps' to 'catkin'. No longer marked as found in versions ros-opencv-apps/2.0.2-4. Ignoring request to alter fixed versions of bug #997527 to the same values previously set > reassign 997530 catkin Bug #997530 [src:mrpt] mrpt: FTBFS: make[4]: *** No rule to make target '/usr/lib/x86_64-linux-gnu/libopencv_calib3d.so.4.5.3', needed by 'lib/libmrpt-ros1bridge.so.2.2.0'. Stop. Bug reassigned from package 'src:mrpt' to 'catkin'. No longer marked as found in versions mrpt/1:2.2.0-2. Ignoring request to alter fixed versions of bug #997530 to the same values previously set > forcemerge 997519 997527 997530 Bug #997519 [catkin] ros-image-pipeline: FTBFS: make[3]: *** No rule to make target '/usr/lib/x86_64-linux-gnu/libopencv_calib3d.so.4.5.3', needed by 'devel/lib/image_view/video_recorder'. Stop. Bug #997527 [catkin] ros-opencv-apps: FTBFS: make[3]: *** No rule to make target '/usr/lib/x86_64-linux-gnu/libopencv_calib3d.so.4.5.3', needed by 'devel/lib/opencv_apps/fback_flow'. Stop. Bug #997530 [catkin] mrpt: FTBFS: make[4]: *** No rule to make target '/usr/lib/x86_64-linux-gnu/libopencv_calib3d.so.4.5.3', needed by 'lib/libmrpt-ros1bridge.so.2.2.0'. Stop. Merged 997519 997527 997530 > affects 997519 src:ros-image-pipeline src:ros-opencv-apps src:mrpt Bug #997519 [catkin] ros-image-pipeline: FTBFS: make[3]: *** No rule to make target '/usr/lib/x86_64-linux-gnu/libopencv_calib3d.so.4.5.3', needed by 'devel/lib/image_view/video_recorder'. Stop. Bug #997527 [catkin] ros-opencv-apps: FTBFS: make[3]: *** No rule to make target '/usr/lib/x86_64-linux-gnu/libopencv_calib3d.so.4.5.3', needed by 'devel/lib/opencv_apps/fback_flow'. Stop. Bug #997530 [catkin] mrpt: FTBFS: make[4]: *** No rule to make target '/usr/lib/x86_64-linux-gnu/libopencv_calib3d.so.4.5.3', needed by 'lib/libmrpt-ros1bridge.so.2.2.0'. Stop. Added indication that 997519 affects src:ros-image-pipeline, src:ros-opencv-apps, and src:mrpt Added indication that 997527 affects src:ros-image-pipeline, src:ros-opencv-apps, and src:mrpt Added indication that 997530 affects src:ros-image-pipeline, src:ros-opencv-apps, and src:mrpt -- 997519: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997519 997527: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997527 997530: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997530 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#997530: mrpt: FTBFS
Control: reassign 997519 catkin Control: reassign 997527 catkin Control: reassign 997530 catkin Control: forcemerge 997519 997527 997530 Control: affects 997519 src:ros-image-pipeline src:ros-opencv-apps src:mrpt Hi José, * José Luis Blanco-Claraco [2021-10-24 05:20]: I've investigated this and found that the error comes from building against a version of the package "cv_bridge" (libcv-bridge-dev) which wasn't yet rebuilt against the latest opencv 4.5.4, but for the older 4.5.3. It is actually a regression in catkin, a patch was dropped by accident. I will upload a fixed version soon and also give libcv-bridge-dev a rebuild. Does this still qualify as a FTBFS error in mrpt? "libcv-bridge-dev" is already listed in d/control... (?). Well, mrpt currently dos not build in in unstable, so FTBFS is correct. I've reassigned the bug and added affects according to my comment above. Cheers Jochen signature.asc Description: PGP signature
Bug#997393: marked as done (fenicsx-performance-tests: FTBFS: dh_auto_configure: error: cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=
Your message dated Mon, 25 Oct 2021 20:56:31 +0200 with message-id <5c5d61eb5db3ef5c29ebfc9f0c65d...@debian.org> and subject line fenicsx-performance-tests: FTBFS has caused the Debian Bug report #997393, regarding fenicsx-performance-tests: FTBFS: dh_auto_configure: error: 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 -DCMAKE_INSTALL_RUNSTATEDIR=/run -DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=ON "-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu ../src returned exit code 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.) -- 997393: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997393 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: fenicsx-performance-tests Version: 0.0~git20210119.80e82ac-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > dpkg-buildpackage > - > > Command: dpkg-buildpackage -us -uc -sa -rfakeroot > dpkg-buildpackage: info: source package fenicsx-performance-tests > dpkg-buildpackage: info: source version 0.0~git20210119.80e82ac-1 > dpkg-buildpackage: info: source distribution unstable > dpkg-buildpackage: info: source changed by Drew Parsons > dpkg-source --before-build . > dpkg-buildpackage: info: host architecture amd64 > debian/rules clean > dh clean --buildsystem=cmake --sourcedirectory=src >dh_auto_clean -O--buildsystem=cmake -O--sourcedirectory=src >dh_autoreconf_clean -O--buildsystem=cmake -O--sourcedirectory=src >dh_clean -O--buildsystem=cmake -O--sourcedirectory=src > dpkg-source -b . > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-source: info: building fenicsx-performance-tests using existing > ./fenicsx-performance-tests_0.0~git20210119.80e82ac.orig.tar.gz > dpkg-source: info: building fenicsx-performance-tests in > fenicsx-performance-tests_0.0~git20210119.80e82ac-1.debian.tar.xz > dpkg-source: info: building fenicsx-performance-tests in > fenicsx-performance-tests_0.0~git20210119.80e82ac-1.dsc > debian/rules binary > dh binary --buildsystem=cmake --sourcedirectory=src >dh_update_autotools_config -O--buildsystem=cmake -O--sourcedirectory=src >dh_autoreconf -O--buildsystem=cmake -O--sourcedirectory=src >dh_auto_configure -O--buildsystem=cmake -O--sourcedirectory=src > 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 -DCMAKE_INSTALL_RUNSTATEDIR=/run > -DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=ON "-GUnix Makefiles" > -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu ../src > -- The C compiler identification is GNU 11.2.0 > -- The CXX compiler identification is GNU 11.2.0 > -- Detecting C compiler ABI info > -- Detecting C compiler ABI info - done > -- Check for working C compiler: /usr/bin/cc - skipped > -- Detecting C compile features > -- Detecting C compile features - done > -- Detecting CXX compiler ABI info > -- Detecting CXX compiler ABI info - done > -- Check for working CXX compiler: /usr/bin/c++ - skipped > -- Detecting CXX compile features > -- Detecting CXX compile features - done > CMake Warning (dev) at > /usr/share/cmake-3.21/Modules/FindPackageHandleStandardArgs.cmake:438 > (message): > The package name passed to `find_package_handle_standard_args` (PkgConfig) > does not match the name of the calling package (MPI). This can lead to > problems in calling code that expects `find_package` result variables > (e.g., `_FOUND`) to follow a certain pattern. > Call Stack (most recent call first): > /usr/share/cmake-3.21/Modules/FindPkgConfig.cmake:70 > (find_package_handle_standard_args) > /usr/share/cmake-3.21/Modules/FindMPI.cmake:270 (include) > /usr/share/cmake-3.21/Modules/CMakeFindDependencyMacro.cmake:47 > (find_package) > /usr/share/dolfinx/cmake/DOLFINXConfig.cmake:46 (find_dependency) > CMakeLists.txt:13 (find_package) > This warning is for project developers. Use -Wno-dev to suppress it. > > -- Found PkgConfig: /usr/bin/pkg-config (found
Bug#997732: marked as done (libcxx-serial: FTBFS: dh_missing: error: missing files, aborting)
Your message dated Mon, 25 Oct 2021 18:49:18 +
with message-id
and subject line Bug#997732: fixed in libcxx-serial 1.2.1-5
has caused the Debian Bug report #997732,
regarding libcxx-serial: FTBFS: dh_missing: 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.)
--
997732: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997732
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libcxx-serial
Version: 1.2.1-4.1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_missing --fail-missing
> dh_missing: warning:
> usr/lib/x86_64-linux-gnu/cmake/cxx-serial/cxx-serialConfig-version.cmake
> exists in debian/tmp but is not installed to anywhere
> dh_missing: warning:
> usr/lib/x86_64-linux-gnu/cmake/cxx-serial/cxx-serialConfig.cmake exists in
> debian/tmp but is not installed to anywhere
> dh_missing: warning: usr/lib/x86_64-linux-gnu/pkgconfig/cxx-serial.pc 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: libcxx-serial-dev (3), libcxx-serial1 (2)
>* dh_installdocs: libcxx-serial-dev (3), libcxx-serial1 (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[1]: *** [debian/rules:20: override_dh_missing] Error 25
The full build log is available from:
http://qa-logs.debian.net/2021/10/23/libcxx-serial_1.2.1-4.1_unstable.log
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 marking 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: libcxx-serial
Source-Version: 1.2.1-5
Done: Alec Leamas
We believe that the bug you reported is fixed in the latest version of
libcxx-serial, 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 997...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Alec Leamas (supplier of updated libcxx-serial 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, 24 Oct 2021 15:01:30 +0200
Source: libcxx-serial
Architecture: source
Version: 1.2.1-5
Distribution: unstable
Urgency: medium
Maintainer: Alec Leamas
Changed-By: Alec Leamas
Closes: 997732
Changes:
libcxx-serial (1.2.1-5) unstable; urgency=medium
.
* Handle uninstalled cmake configuration files. Closes: #997732
Checksums-Sha1:
ba11e8fc08c4e81e6d8bad44571b4896ed98d85c 1819 libcxx-serial_1.2.1-5.dsc
2843577180a7dab0d575e487006fcccb6dbb6f1b 8524
libcxx-serial_1.2.1-5.debian.tar.xz
b74baa536c7889c566b4c2b4896abbfdf7b4be01 9008
libcxx-serial_1.2.1-5_source.buildinfo
Checksums-Sha256:
a8143df6390f40ebbc2151b36e9f5d3940b36967ae545c705e6e92e367b519d2 1819
Bug#997758: nose: FTBFS: There is a syntax error in your configuration file: invalid syntax (conf.py, line 220)
Hi Thomas and all! On Sun, Oct 24, 2021 at 11:53:19PM +0200, Thomas Goirand wrote: > Hi, > > I'm referenced for 55 packages. Please don't force me to do this right > away, that's too much work. I very much would prefer if we could have a > smoother transition. > > Note that it's possible that for many packages mentioned, only removing > the dependency should be enough. Still, that's some work to do... :/ > > Other alternative would be: help with NMU fixes (or I can add any of you > in the OpenStack team if you need...). Thanks to Jakub Wilk, we have a patch which fixes the FTBFS and I will apply it for the time being. However, it would be still nice to remove nose at some future point, maybe before Bookworm release. Last release was in June 2015 (six years ago!) and the project is dead and unmaintained. As you can see, it was not even ported to Python 3 properly. There is absolutely no rush, and I am going to follow the usual procedure: discuss on debian-devel, do MBF with severity: normal, then bump severities to important and finally to RC. There will be a few months before each stage. I'm impressed by the number of packages you have depending on nose, but if they all come from the same upstream, maybe you can convince this upstream to not rely on dead software. -- Dmitry Shachnev signature.asc Description: PGP signature
Bug#997829: libipc-shareable-perl: autopkgtest regression on armhf and i386
Control: tags -1 + ftbfs sid bookworm On Mon, 25 Oct 2021 16:51:00 +0200, Paul Gevers wrote: > With a recent upload of libipc-shareable-perl the autopkgtest of > libipc-shareable-perl fails in testing when that autopkgtest is run with > the binary packages of libipc-shareable-perl from unstable. It passes > when run with only packages from testing. In tabular form: Thanks for noticing. It also fails to build on the same architectures: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/i386/libipc-shareable-perl.html https://tests.reproducible-builds.org/debian/rb-pkg/unstable/armhf/libipc-shareable-perl.html with the same error. CPAN smoke testers also look suspicious: http://matrix.cpantesters.org/?dist=IPC-Shareable%201.06;os=linux;perl=5.32.0;reports=1 I'm going the forward the bug upstream. Cheers, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- signature.asc Description: Digital Signature
Processed: Re: Bug#997829: libipc-shareable-perl: autopkgtest regression on armhf and i386
Processing control commands: > tags -1 + ftbfs sid bookworm Bug #997829 [src:libipc-shareable-perl] libipc-shareable-perl: autopkgtest regression on armhf and i386 Added tag(s) ftbfs, sid, and bookworm. -- 997829: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997829 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bug 997829 is forwarded to https://github.com/stevieb9/ipc-shareable/issues/14
Processing commands for cont...@bugs.debian.org: > forwarded 997829 https://github.com/stevieb9/ipc-shareable/issues/14 Bug #997829 [src:libipc-shareable-perl] libipc-shareable-perl: autopkgtest regression on armhf and i386 Set Bug forwarded-to-address to 'https://github.com/stevieb9/ipc-shareable/issues/14'. > thanks Stopping processing here. Please contact me if you need assistance. -- 997829: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997829 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#984278: Fix discovered
I have figured out a fix (the issue was in detecting what flags were needed to use std::filesystem, my conclusion is: with gcc11+, tell CMake C++17 or it will misbehave), and an updated package will be available soon pending sponsorship. OpenPGP_signature Description: OpenPGP digital signature
Processed: bug 984384 is forwarded to https://github.com/worldforge/varconf/commit/9e2626355fa82b5375578f41caf5c20bc994a444
Processing commands for cont...@bugs.debian.org: > forwarded 984384 > https://github.com/worldforge/varconf/commit/9e2626355fa82b5375578f41caf5c20bc994a444 Bug #984384 [src:varconf] varconf: ftbfs with GCC-11 Set Bug forwarded-to-address to 'https://github.com/worldforge/varconf/commit/9e2626355fa82b5375578f41caf5c20bc994a444'. > thanks Stopping processing here. Please contact me if you need assistance. -- 984384: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984384 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#997758: nose: FTBFS: There is a syntax error in your configuration file: invalid syntax (conf.py, line 220)
Control: tags -1 + patch
* Dmitry Shachnev , 2021-10-24, 16:24:
setuptools v58.0.0 removed support for 2to3 during builds,
which nose relied on (because it has a Python 2 codebase).
You can convert the source to be compatible with Python 3 with these
commands:
patch -p1 unit_tests/test_issue_100.rst <
unit_tests/test_issue_100.rst.py3.patch
2to3 -wn .
find -name '*.rst' | xargs 2to3 -dwn
Then you need a few small changes (see the attached patches) to stop
the build system from trying to run 2to3 stuff again at build time.
--
Jakub Wilk
--- a/selftest.py
+++ b/selftest.py
@@ -32,7 +32,7 @@ if __name__ == "__main__":
this_dir = os.path.normpath(os.path.abspath(os.path.dirname(__file__)))
lib_dirs = [this_dir]
test_dir = this_dir
-if sys.version_info >= (3,):
+if False:
# Under Python 3.x, we need to 'build' the source (using 2to3, etc)
# first. 'python3 setup.py build_tests' will put everything under
# build/tests (including nose itself, since some tests are inside the
--- a/setup.py
+++ b/setup.py
@@ -6,7 +6,7 @@ py_vers_tag = '-%s.%s' % sys.version_inf
test_dirs = ['functional_tests', 'unit_tests', os.path.join('doc','doc_tests'), 'nose']
-if sys.version_info >= (3,):
+if False:
import setuptools
extra = {'use_2to3': True,
--- a/setup3lib.py
+++ b/setup3lib.py
@@ -3,7 +3,7 @@ from setuptools import setup as _setup
py3_args = ['use_2to3', 'convert_2to3_doctests', 'use_2to3_fixers', 'test_dirs', 'test_build_dir', 'doctest_exts', 'pyversion_patching']
-if sys.version_info < (3,):
+if True:
# Remove any Python-3.x-only arguments (so they don't generate complaints
# from 2.x setuptools) and then just pass through to the regular setup
# routine.
--- a/setup.cfg
+++ b/setup.cfg
@@ -2,7 +2,6 @@
with-doctest = 1
doctest-extension = .rst
doctest-fixtures = _fixtures
-py3where = build/tests
[bdist_rpm]
doc_files = README.txt
diff -Nru nose-1.3.7/debian/clean nose-1.3.7/debian/clean
--- nose-1.3.7/debian/clean 2020-07-17 22:44:16.0 +0200
+++ nose-1.3.7/debian/clean 2021-10-25 18:14:56.0 +0200
@@ -6,3 +6,4 @@
functional_tests/support/xunit.xml
nose.egg-info/
unit_tests/support/doctest/noname_wrapped.not_pyc
+functional_tests/support/issue408/.coverage
diff -Nru nose-1.3.7/debian/rules nose-1.3.7/debian/rules
--- nose-1.3.7/debian/rules 2020-07-17 22:44:16.0 +0200
+++ nose-1.3.7/debian/rules 2021-10-25 18:14:56.0 +0200
@@ -3,7 +3,7 @@
DESTDIR3 := $(CURDIR)/debian/python3-nose
export PYBUILD_NAME = nose
-export PYBUILD_TEST_ARGS_python3 = {interpreter} setup.py build_tests && {interpreter} selftest.py -v
+export PYBUILD_TEST_ARGS_python3 = {interpreter} setup.py egg_info && {interpreter} selftest.py -v
BUILDDIR3 := $(shell pybuild --print build_dir --interpreter python3)
Processed: Re: Bug#997758: nose: FTBFS: There is a syntax error in your configuration file: invalid syntax (conf.py, line 220)
Processing control commands: > tags -1 + patch Bug #997758 [src:nose] nose: FTBFS: There is a syntax error in your configuration file: invalid syntax (conf.py, line 220) Added tag(s) patch. -- 997758: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997758 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#997226: marked as done (font-manager: FTBFS: FontManager-0.8.7.gir:6351.7-6351.84: error: `FontManager.fsType' already contains a definition for `to_string')
Your message dated Mon, 25 Oct 2021 16:48:51 + with message-id and subject line Bug#997226: fixed in font-manager 0.8.7-2 has caused the Debian Bug report #997226, regarding font-manager: FTBFS: FontManager-0.8.7.gir:6351.7-6351.84: error: `FontManager.fsType' already contains a definition for `to_string' 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.) -- 997226: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997226 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: font-manager Version: 0.8.7-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs 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 -- \ > -Dnautilus=True \ > -Dnemo=True \ > -Dthunar=True \ > -Dreproducible=True > install -d /<>/debian/.debhelper/generated/_source/home > install -d obj-x86_64-linux-gnu > cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. > --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc > --localstatedir=/var --libdir=lib/x86_64-linux-gnu -Dnautilus=True > -Dnemo=True -Dthunar=True -Dreproducible=True > The Meson build system > Version: 0.59.2 > Source dir: /<> > Build dir: /<>/obj-x86_64-linux-gnu > Build type: native build > Project name: font-manager > Project version: 0.8.7 > C compiler for the host machine: cc (gcc 11.2.0 "cc (Debian 11.2.0-10) > 11.2.0") > C linker for the host machine: cc ld.bfd 2.37 > Vala compiler for the host machine: valac (valac 0.54.2) > Host machine cpu family: x86_64 > Host machine cpu: x86_64 > Library m found: YES > Found pkg-config: /usr/bin/pkg-config (0.29.2) > Run-time dependency fontconfig found: YES 2.13.1 > Run-time dependency freetype2 found: YES 24.0.18 > Run-time dependency json-glib-1.0 found: YES 1.6.6 > Run-time dependency gio-2.0 found: YES 2.70.0 > Run-time dependency gio-unix-2.0 found: YES 2.70.0 > Run-time dependency glib-2.0 found: YES 2.70.0 > Run-time dependency gmodule-2.0 found: YES 2.70.0 > Run-time dependency gobject-2.0 found: YES 2.70.0 > Run-time dependency gtk+-3.0 found: YES 3.24.30 > Run-time dependency pango found: YES 1.48.10 > Run-time dependency pangoft2 found: YES 1.48.10 > Run-time dependency sqlite3 found: YES 3.36.0 > Run-time dependency libxml-2.0 found: YES 2.9.12 > Run-time dependency libsoup-2.4 found: YES 2.74.0 > Run-time dependency webkit2gtk-4.0 found: YES 2.34.1 > Program python3 found: YES (/usr/bin/python3) > WARNING: Broken python installation detected. Python files installed by Meson > might not be found by python interpreter. > Configuring config.h using configuration > Program msgfmt found: YES (/usr/bin/msgfmt) > Configuring POTFILES with command > Configuring font-manager.1 using configuration > Program yelp-build found: YES (/usr/bin/yelp-build) > Found pkg-config: /usr/bin/pkg-config (0.29.2) > Program glib-compile-resources found: YES (/usr/bin/glib-compile-resources) > Run-time dependency gobject-introspection-1.0 found: YES 1.70.0 > Dependency gobject-introspection-1.0 found: YES 1.70.0 (cached) > Program g-ir-scanner found: YES (/usr/bin/g-ir-scanner) > Dependency gobject-introspection-1.0 found: YES 1.70.0 (cached) > Program g-ir-compiler found: YES (/usr/bin/g-ir-compiler) > Program vapigen found: YES (/usr/bin/vapigen) > Program glib-compile-resources found: YES (/usr/bin/glib-compile-resources) > Configuring font-manager-utils.c using configuration > Configuring font-manager.h with command > Program vapigen found: YES (/usr/bin/vapigen) > Program glib-compile-resources found: YES (/usr/bin/glib-compile-resources) > Program glib-compile-resources found: YES (/usr/bin/glib-compile-resources) > Configuring gschema.compiled with command > Configuring org.gnome.FontManager.desktop.in using configuration > Configuring org.gnome.FontManager.appdata.xml.in using configuration > Configuring org.gnome.FontViewer.desktop.in using configuration > Configuring org.gnome.FontViewer.appdata.xml.in using configuration > Run-time dependency libnautilus-extension found: YES 41.0 > Run-time dependency libnemo-extension found: YES 5.0.3 > Run-time dependency thunarx-3 found: YES 4.16.8 > Program meson_post_install.py found: YES (/usr/bin/python3 > /<>/meson_post_install.py) > Program meson_dist.py found: YES (/usr/bin/python3 > /<>/meson_dist.py) > Build targets in project: 35 > > font-manager 0.8.7 > > Project options > > Font Manager: YES > Font Viewer : YES > Help Documents
Bug#995832: marked as done (libhealpix-cxx3: missing Breaks+Replaces: libhealpix-cxx2 (>= 3.80))
Your message dated Mon, 25 Oct 2021 16:34:29 + with message-id and subject line Bug#995832: fixed in healpix-cxx 3.80.0-3 has caused the Debian Bug report #995832, regarding libhealpix-cxx3: missing Breaks+Replaces: libhealpix-cxx2 (>= 3.80) 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.) -- 995832: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995832 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libhealpix-cxx3 Version: 3.80.0-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. This error may also be triggered by having a predecessor package from 'sid 'installed while installing the package from 'experimental'. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Preparing to unpack .../libhealpix-cxx3_3.80.0-2_amd64.deb ... Unpacking libhealpix-cxx3:amd64 (3.80.0-2) ... dpkg: error processing archive /var/cache/apt/archives/libhealpix-cxx3_3.80.0-2_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libhealpix_cxx.so.3.0.2', which is also in package libhealpix-cxx2:amd64 3.80.0-1 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/libhealpix-cxx3_3.80.0-2_amd64.deb The unusal >= relation is intended in this case, since the package is co-installable with libhealpix-cxx2 in stable and testing, only the version in sid which shipped the wrong soname is to be broken. cheers, Andreas libhealpix-cxx2=3.80.0-1_libhealpix-cxx3=3.80.0-2.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: healpix-cxx Source-Version: 3.80.0-3 Done: Leo Singer We believe that the bug you reported is fixed in the latest version of healpix-cxx, 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 995...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Leo Singer (supplier of updated healpix-cxx 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: Mon, 25 Oct 2021 11:58:18 -0400 Source: healpix-cxx Architecture: source Version: 3.80.0-3 Distribution: experimental Urgency: medium Maintainer: Debian Astro Team Changed-By: Leo Singer Closes: 995832 Changes: healpix-cxx (3.80.0-3) experimental; urgency=medium . * Fix "missing Breaks+Replaces: libhealpix-cxx2 (>= 3.80)": Declare that libhealpix-cxx3 Breaks: and Replaces: libhealpix-cxx2 due to libhealpix-cxx2 shipping with the wrong SONAME. (Closes: #995832) Checksums-Sha1: 8ccdc88969befc38c3612b11ae85808c19747923 2134 healpix-cxx_3.80.0-3.dsc a53ff14a5c2b5498ad3807c0c6cf009663ccce0a 5724 healpix-cxx_3.80.0-3.debian.tar.xz 2f92e18bdea1402d278718fa2a82d0c813c07f73 7014 healpix-cxx_3.80.0-3_amd64.buildinfo Checksums-Sha256: 31e356ba7eaa03e27b4acbd1ffdace3a09eab3c2cb2284c4e749ebbf9f83852e 2134 healpix-cxx_3.80.0-3.dsc b955b9de5593f1805372003a66eab050883d9b934064bac945d94312e89327f7 5724 healpix-cxx_3.80.0-3.debian.tar.xz dcb6c910c065ebd4e4445be79e9cf6189198f70f6f5075bc07579ad777c5633d 7014 healpix-cxx_3.80.0-3_amd64.buildinfo Files: d993a89b8462d59c860e9c5365840e72 2134 libs optional healpix-cxx_3.80.0-3.dsc 1b4fbb089717ff2c19bfc32fa1b304d6 5724 libs optional healpix-cxx_3.80.0-3.debian.tar.xz 6df174e5382e34a2c6a8df4d15b03f77 7014 libs optional healpix-cxx_3.80.0-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEETlIW+xCXmEEMK3UhbGdTGlqCeZ4FAmF21aEACgkQbGdTGlqC eZ5k4w//ehUtCoDmneyyx/mBnNUC7EqiaCKs4s8BVah+8YWruWzHg9RJhIAxqbAA INdoQ6v+xL4nNQl+5+xt/5ebqDr3H8FgFTUiK4yqliDpMcfDyXRt5ezGytPtH2rp Pno95y4l8H10wZgQJBgzWvMC4+Ih2zSHSqf4b2IS0Zwr/g0pTARFp4jyeDSLoGgV 7UOItQ12AguJJDpNu5pqUaHo0KgWpZiSa6C98Vi6I+ZaL6HU7buTin/SKhltDbOI
Processed: set fwd addr for bug 997226
Processing commands for cont...@bugs.debian.org: > forwarded 997226 https://github.com/FontManager/font-manager/issues/240 Bug #997226 [src:font-manager] font-manager: FTBFS: FontManager-0.8.7.gir:6351.7-6351.84: error: `FontManager.fsType' already contains a definition for `to_string' Set Bug forwarded-to-address to 'https://github.com/FontManager/font-manager/issues/240'. > tags 997226 +fixed-upstream Bug #997226 [src:font-manager] font-manager: FTBFS: FontManager-0.8.7.gir:6351.7-6351.84: error: `FontManager.fsType' already contains a definition for `to_string' Added tag(s) fixed-upstream. > End of message, stopping processing here. Please contact me if you need assistance. -- 997226: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997226 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#997834: samtools: binary-any FTBFS
Source: samtools
Version: 1.13-3
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/logs.php?pkg=samtools=1.13-3
...
dh_install
install -d debian/samtools//usr
cp --reflink=auto -a debian/tmp/usr/bin debian/samtools//usr/
install -d debian/samtools//usr/share/man
cp --reflink=auto -a debian/tmp/usr/share/man/man1
debian/samtools//usr/share/man/
install -d debian/samtools/usr/share/commonwl/
cp --reflink=auto -a ./debian/samtools-faidx.cwl
./debian/samtools-index.cwl ./debian/samtools-rmdup.cwl
./debian/samtools-sort.cwl ./debian/samtools-view.cwl
debian/samtools/usr/share/commonwl//
cp --reflink=auto -a ./debian/mans/ace2sam.1
./debian/mans/samtools.pl.1 ./debian/mans/wgsim.1
debian/samtools/usr/share/man/man1/
install -d debian/.debhelper/generated/samtools
install -d debian/.debhelper/generated/samtools-test
# Fix Perl interpreter PATH
for pscript in `grep -Rl '#!/usr/bin/env \+perl' debian/*` ; do \
sed -i '1s?#!/usr/bin/env \+perl?#!/usr/bin/perl?' ${pscript} ; \
done
# Disable the executable bit on a dataset.
chmod 0644 debian/samtools-test/usr/share/samtools/test/ampliconclip/ac_test.bed
chmod: cannot access
'debian/samtools-test/usr/share/samtools/test/ampliconclip/ac_test.bed': No
such file or directory
make[1]: *** [debian/rules:59: override_dh_install] Error 1
Bug#997658: marked as done (botan: FTBFS: tests failed)
Your message dated Mon, 25 Oct 2021 16:03:27 + with message-id and subject line Bug#997658: fixed in botan 2.18.2+dfsg-1 has caused the Debian Bug report #997658, regarding botan: FTBFS: tests failed 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.) -- 997658: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997658 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: botan Version: 2.18.1+dfsg-3 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > LD_LIBRARY_PATH=. /<>/botan-test > Testing Botan 2.18.1 (unreleased, revision unknown, distribution Debian) > CPU flags: sse2 ssse3 sse41 sse42 avx2 avx512f avx512dq avx512bw rdtsc bmi1 > bmi2 adx aes_ni clmul rdrand rdseed > Starting tests drbg_seed:16B097975A637739 > block: > AES-128 ran 34470 tests in 53.80 msec all ok > AES-192 ran 40500 tests in 63.88 msec all ok > AES-256 ran 46260 tests in 74.17 msec all ok > ARIA-128 ran 30 tests in 0.06 msec all ok > ARIA-192 ran 30 tests in 0.06 msec all ok > ARIA-256 ran 30 tests in 0.06 msec all ok > Blowfish ran 1860 tests in 21.24 msec all ok > CAST-128 ran 1440 tests in 2.10 msec all ok > CAST-256 ran 195 tests in 0.34 msec all ok > Camellia-128 ran 180 tests in 0.27 msec all ok > Camellia-192 ran 90 tests in 0.13 msec all ok > Camellia-256 ran 150 tests in 0.23 msec all ok > Cascade(Serpent,AES-256) ran 30 tests in 0.08 msec all ok > Cascade(Serpent,CAST-128) ran 15 tests in 0.04 msec all ok > Cascade(Serpent,Twofish) ran 45 tests in 0.17 msec all ok > DES ran 9630 tests in 13.49 msec all ok > DESX ran 135 tests in 0.20 msec all ok > GOST-28147-89(R3411_94_TestParam) ran 270 tests in 0.52 msec all ok > GOST-28147-89(R3411_CryptoPro) ran 150 tests in 0.28 msec all ok > IDEA ran 16260 tests in 33.14 msec all ok > KASUMI ran 45 tests in 0.07 msec all ok > Lion(SHA-160,RC4,64) ran 15 tests in 0.10 msec all ok > MISTY1 ran 465 tests in 0.65 msec all ok > Noekeon ran 15450 tests in 21.44 msec all ok > SEED ran 120 tests in 0.19 msec all ok > SHACAL2 ran 46035 tests in 79.69 msec all ok > SM4 ran 45 tests in 0.09 msec all ok > Serpent ran 47070 tests in 76.78 msec all ok > Threefish-512 ran 150 tests in 0.29 msec all ok > TripleDES ran 1680 tests in 2.70 msec all ok > Twofish ran 16545 tests in 31.26 msec all ok > XTEA ran 1020 tests in 1.67 msec all ok > stream: > CTR-BE(AES-128) ran 648 tests in 1.91 msec all ok > CTR-BE(AES-128,4) ran 12 tests in 0.05 msec all ok > CTR-BE(AES-128,5) ran 12 tests in 0.03 msec all ok > CTR-BE(AES-128,6) ran 12 tests in 0.03 msec all ok > CTR-BE(AES-128,8) ran 12 tests in 0.04 msec all ok > CTR-BE(AES-192) ran 768 tests in 1.90 msec all ok > CTR-BE(AES-256) ran 804 tests in 2.00 msec all ok > CTR-BE(Blowfish) ran 12 tests in 0.17 msec all ok > CTR-BE(DES) ran 588 tests in 1.57 msec all ok > CTR-BE(Noekeon) ran 2304 tests in 6.18 msec all ok > CTR-BE(Serpent) ran 2100 tests in 5.73 msec all ok > CTR-BE(TripleDES) ran 2556 tests in 11.61 msec all ok > CTR-BE(XTEA) ran 1452 tests in 3.72 msec all ok > ChaCha(12) ran 72 tests in 0.17 msec all ok > ChaCha(20) ran 3096 tests in 8.30 msec all ok > ChaCha(8) ran 717 tests in 1.90 msec all ok > MARK-4 ran 120 tests in 0.25 msec all ok > OFB(AES-128) ran 132 tests in 0.34 msec all ok > OFB(AES-192) ran 12 tests in 0.03 msec all ok > OFB(AES-256) ran 12 tests in 0.03 msec all ok > OFB(DES) ran 48 tests in 0.14 msec all ok > RC4 ran 1656 tests in 4.55 msec all ok > RC4(3) ran 24 tests in 0.05 msec all ok > SHAKE-128 ran 13740 tests in 25.10 msec all ok > Salsa20 ran 143 tests in 0.34 msec all ok > hash: > Adler32 ran 266 tests in 0.19 msec all ok > BLAKE2b(224) ran 2547 tests in 2.44 msec all ok > BLAKE2b(256) ran 2547 tests in 2.42 msec all ok > BLAKE2b(384) ran 2547 tests in 2.56 msec all ok > BLAKE2b(512) ran 2675 tests in 3.25 msec all ok > CRC24 ran 284 tests in 0.14 msec all ok > CRC32 ran 266 tests in 0.14 msec all ok > Comb4P(MD4,MD5) ran 10 tests in 0.05 msec all ok > Comb4P(SHA-160,RIPEMD-160) ran 10 tests in 0.03 msec all ok > GOST-R-34.11-94 ran 95 tests in 0.55 msec all ok > Keccak-1600(224) ran 2667 tests in 3.88 msec all ok > Keccak-1600(256) ran 2667 tests in 3.95 msec all ok > Keccak-1600(384) ran 2667 tests in 4.38 msec all ok > Keccak-1600(512) ran 2667 tests in 5.00 msec all ok > MD4 ran 1500 tests in 0.74 msec all ok > MD5 ran 1520 tests in 0.85 msec all ok >
Bug#997003: workaround
Hi,
It seems to me a workaround for this bug is to run the systemd unit of
the PHP-FPM process as `www-data`. This should mitigate the privilege
escalation because the process would escalate from `www-data`
to... well, `www-data`.
Obviously that doesn't work if you have multiple pools running as
different users.
Three files need to be changed for this to take effect:
# cat /etc/systemd/system/php7.3-fpm.service.d/override.conf
[Service]
# mitigation for possible privilege escalations in php-fpm
# (e.g. CVE-2021-21703): do not run the master as root
User=www-data
# cat /etc/php/7.3/fpm/pool.d/00-rootless-logs.conf
[global]
; default value from Debian: /var/log/php7.3-fpm.log
error_log = /var/log/php/fpm.log
# cat /etc/logrotate.d/php7.3-fpm
/var/log/php/fpm.log {
rotate 12
weekly
missingok
notifempty
compress
delaycompress
postrotate
/usr/lib/php/php7.3-fpm-reopenlogs
endscript
}
php-fpm and systemd needs to be reloaded as well:
systemctl daemon-reload
systemctl restart php7.3-fpm
This should also be possible in the `init.d` sysvinit script, I leave
that as an exercise for the reader.
a.
--
My passionate sense of social justice and social responsibility has
always contrasted oddly with my pronounced lack of need for direct
contact with other human beings and communities. I am truly a "lone
traveler" and have never belonged to my country, my home, my friends,
or even my immediate family, with my whole heart; in the face of all
these ties, I have never lost a sense of distance and a need for
solitude.
- Albert Einstein
signature.asc
Description: PGP signature
Processed: Re: spyne: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13
Processing control commands:
> retitle -1 spyne: unit test fail with sqlalchemy 1.4
Bug #997492 [src:spyne] spyne: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p 3.9 returned exit code 13
Changed Bug title to 'spyne: unit test fail with sqlalchemy 1.4' from 'spyne:
FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p
3.9 returned exit code 13'.
> severity -1 important
Bug #997492 [src:spyne] spyne: unit test fail with sqlalchemy 1.4
Severity set to 'important' from 'serious'
> notfound -1 spyne/2.13.16-1
Bug #997492 [src:spyne] spyne: unit test fail with sqlalchemy 1.4
No longer marked as found in versions spyne/2.13.16-1.
> found -1 spyne/2.13.16-2
Bug #997492 [src:spyne] spyne: unit test fail with sqlalchemy 1.4
The source spyne and version 2.13.16-2 do not appear to match any binary
packages
Marked as found in versions spyne/2.13.16-2.
--
997492: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997492
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#997492: spyne: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13
Control: retitle -1 spyne: unit test fail with sqlalchemy 1.4 Control: severity -1 important Control: notfound -1 spyne/2.13.16-1 Control: found -1 spyne/2.13.16-2 The FTBFS is fixed but the root cause is not (see forwarded upstream issue).
Processed: affects 994276
Processing commands for cont...@bugs.debian.org: > affects 994276 + koules Bug #994276 [xutils-dev] xutils-dev: imake shouldn't pass l to ar Bug #997615 [xutils-dev] troffcvt: FTBFS: ar: libdeps specified more than once Bug #997636 [xutils-dev] koules: FTBFS: ar: libdeps specified more than once Bug #997641 [xutils-dev] knews: FTBFS: ar: libdeps specified more than once Bug #997650 [xutils-dev] xtel: FTBFS: ar: libdeps specified more than once Added indication that 994276 affects koules Added indication that 997615 affects koules Added indication that 997636 affects koules Added indication that 997641 affects koules Added indication that 997650 affects koules > thanks Stopping processing here. Please contact me if you need assistance. -- 994276: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994276 997615: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997615 997636: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997636 997641: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997641 997650: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997650 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: forcibly merging 994276 997636
Processing commands for cont...@bugs.debian.org: > forcemerge 994276 997636 Bug #994276 [xutils-dev] xutils-dev: imake shouldn't pass l to ar Bug #997615 [xutils-dev] troffcvt: FTBFS: ar: libdeps specified more than once Bug #997641 [xutils-dev] knews: FTBFS: ar: libdeps specified more than once Bug #997650 [xutils-dev] xtel: FTBFS: ar: libdeps specified more than once Bug #997641 [xutils-dev] knews: FTBFS: ar: libdeps specified more than once Removed indication that 997641 affects troffcvt, knews, and xtel Added indication that 997641 affects xtel,knews,troffcvt Removed indication that 994276 affects troffcvt, knews, and xtel Added indication that 994276 affects xtel,knews,troffcvt Removed indication that 997615 affects troffcvt, knews, and xtel Added indication that 997615 affects xtel,knews,troffcvt Removed indication that 997650 affects xtel, troffcvt, and knews Added indication that 997650 affects xtel,knews,troffcvt Bug #997636 [xutils-dev] koules: FTBFS: ar: libdeps specified more than once Removed indication that 997636 affects koules Added indication that 997636 affects xtel,knews,troffcvt Marked as found in versions xutils-dev/1:7.7+5. Added tag(s) patch. Bug #997615 [xutils-dev] troffcvt: FTBFS: ar: libdeps specified more than once Bug #997650 [xutils-dev] xtel: FTBFS: ar: libdeps specified more than once Merged 994276 997615 997636 997641 997650 > thanks Stopping processing here. Please contact me if you need assistance. -- 994276: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994276 997615: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997615 997636: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997636 997641: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997641 997650: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997650 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed (with 1 error): reassign 997636 to xutils-dev, affects 997636, merging 994276 997636
Processing commands for cont...@bugs.debian.org: > reassign 997636 xutils-dev Bug #997636 [src:koules] koules: FTBFS: ar: libdeps specified more than once Bug reassigned from package 'src:koules' to 'xutils-dev'. No longer marked as found in versions koules/1.4-27. Ignoring request to alter fixed versions of bug #997636 to the same values previously set > affects 997636 koules Bug #997636 [xutils-dev] koules: FTBFS: ar: libdeps specified more than once Added indication that 997636 affects koules > merge 994276 997636 Bug #994276 [xutils-dev] xutils-dev: imake shouldn't pass l to ar Bug #997615 [xutils-dev] troffcvt: FTBFS: ar: libdeps specified more than once Bug #997641 [xutils-dev] knews: FTBFS: ar: libdeps specified more than once Bug #997650 [xutils-dev] xtel: FTBFS: ar: libdeps specified more than once Unable to merge bugs because: affects of #997650 is 'troffcvt,knews,xtel' not 'xtel,knews,troffcvt' affects of #997615 is 'knews,troffcvt,xtel' not 'xtel,knews,troffcvt' affects of #997641 is 'knews,troffcvt,xtel' not 'xtel,knews,troffcvt' affects of #997636 is 'koules' not 'xtel,knews,troffcvt' Failed to merge 994276: Did not alter merged bugs. > thanks Stopping processing here. Please contact me if you need assistance. -- 994276: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994276 997615: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997615 997636: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997636 997641: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997641 997650: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997650 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#997239: (no subject)
This has been fixed upstream, and I'm cherry-picking that patch to the package in lieu of a new upstream release, which we should do sometime soon here. OpenPGP_signature Description: OpenPGP digital signature
Bug#997829: libipc-shareable-perl: autopkgtest regression on armhf and i386
Source: libipc-shareable-perl Version: 1.06-1 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of libipc-shareable-perl the autopkgtest of libipc-shareable-perl fails in testing when that autopkgtest is run with the binary packages of libipc-shareable-perl from unstable. It passes when run with only packages from testing. In tabular form: passfail libipc-shareable-perl from testing1.06-1 all others from testingfrom testing I copied some of the output at the bottom of this report. The issue seems to be related to 32 bit archs. Currently this regression is blocking the migration to testing [1]. Can you please investigate the situation and fix it? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=libipc-shareable-perl https://ci.debian.net/data/autopkgtest/testing/armhf/libi/libipc-shareable-perl/16170185/log.gz t/65-seg_size.t .. ok 1 - size larger than MAX croaks ok ok 2 - ...and error is sane IPC_MEM env var not set, skipping the exhaust memory test not ok 3 - We croak if size is greater than max RAM # Failed test 'We croak if size is greater than max RAM' # at t/65-seg_size.t line 52. # got: '1' # expected: undef not ok 4 - ...and error is sane # Failed test '...and error is sane' # at t/65-seg_size.t line 54. # '' # doesn't match '(?^:Cannot allocate memory|Out of memory|Invalid argument)' ok 5 - size param is the same as the segment size ok 6 - actual size in bytes ok if sending in custom size 1..6 # Looks like you failed 2 tests of 6. Dubious, test returned 2 (wstat 512, 0x200) Failed 2/6 subtests [...] t/85-spawn_object_contains_data.t skipped: IPC_SPAWN_TEST env var not set t/86-unspawn_object_contains_data.t .. skipped: IPC_SPAWN_TEST env var not set t/91-pod_linkcheck.t . skipped: Author test: RELEASE_TESTING not set t/93-manifest.t .. skipped: Author test: RELEASE_TESTING not set Test Summary Report --- t/65-seg_size.t(Wstat: 512 Tests: 6 Failed: 2) Failed tests: 3-4 Non-zero exit status: 2 Files=36, Tests=412, 16 wallclock secs ( 0.20 usr 0.36 sys + 4.66 cusr 4.92 csys = 10.14 CPU) Result: FAIL autopkgtest [10:47:54]: test autodep8-perl-build-deps OpenPGP_signature Description: OpenPGP digital signature
Bug#994790: marked as done (hcxtools: CVE-2021-32286)
Your message dated Mon, 25 Oct 2021 14:48:39 + with message-id and subject line Bug#994790: fixed in hcxtools 6.2.4-1 has caused the Debian Bug report #994790, regarding hcxtools: CVE-2021-32286 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.) -- 994790: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994790 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: hcxtools X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerability was published for hcxtools. CVE-2021-32286[0]: | An issue was discovered in hcxtools through 6.1.6. A global-buffer- | overflow exists in the function pcapngoptionwalk located in | hcxpcapngtool.c. It allows an attacker to cause code Execution. https://github.com/ZerBea/hcxtools/issues/155 https://github.com/ZerBea/hcxtools/commit/e6505ddc262bc3254b39844895ebac70861001d2 If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2021-32286 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-32286 Please adjust the affected versions in the BTS as needed. --- End Message --- --- Begin Message --- Source: hcxtools Source-Version: 6.2.4-1 Done: Paulo Roberto Alves de Oliveira (aka kretcheu) We believe that the bug you reported is fixed in the latest version of hcxtools, 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 994...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Paulo Roberto Alves de Oliveira (aka kretcheu) (supplier of updated hcxtools package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 15 Oct 2021 16:09:00 -0300 Source: hcxtools Architecture: source Version: 6.2.4-1 Distribution: unstable Urgency: medium Maintainer: Debian Security Tools Changed-By: Paulo Roberto Alves de Oliveira (aka kretcheu) Closes: 974484 994790 Changes: hcxtools (6.2.4-1) unstable; urgency=medium . [ Ulises Vitulli ] * Use Salsa-CI template . [ Paulo Roberto Alves de Oliveira (aka kretcheu) ] * New upstream version 6.2.4. * Fixed CVE-2021-32286 global-buffer-overflow (Closes: #994790) * Using new DH level format. Consequently: - debian/compat: removed. - debian/control: changed from 'debhelper' to 'debhelper-compat' in Build-Depends field and bumped level to 13. * debian/control: - Added 'Rules-Requires-Root: no' to source stanza. - Bumped Standards-Version to 4.6.0.1. - Fixed uploader name. - Added new build dependencies (openssl, pkg-config). - Changed ieee-data arch dependency to all. - Changed maintainer to team+pkg-security and put myself and Ulises as uploader. * debian/copyright: - Updated packaging copyright years. - Included kretcheu. * debian/hcxtools.lintian-overrides: updated and fixed spell errors. * debian/patches/: - Added 01-fix-spell-errors.patch: fix spell errors. - Added 02-fix-cross-build.patch to solve cross build error. * debian/rules: - Removed '-Wl,--as-needed' not required now. - Fixed string that generate manpage. * debian/watch: updated watch file. * debian/tests/: - Added superficial restriction. (Closes: #974484). - Included tests for all binaries. * Added upstream metadata file. * Added upstream signing key. Checksums-Sha1: d64171690da7aea66258e6617ce23a00f6063622 2101 hcxtools_6.2.4-1.dsc 2548f5078133cf150e1e2d6237e2600992f8b868 147077 hcxtools_6.2.4.orig.tar.gz b2b3fcab0ef13b5f0d7a62b72ba4d55d697d7bd3 5676 hcxtools_6.2.4-1.debian.tar.xz c234e7857bbf4088a4a951b5377abb1249a32155 6853 hcxtools_6.2.4-1_amd64.buildinfo Checksums-Sha256: 28fa8b2eefc41eab36af9f5d0f7df40ebb75374f02dc209b7cd560c3c5a16ad0 2101 hcxtools_6.2.4-1.dsc 74299313dd15ed38f07b42201903ab85ebbc3ad220a01fff1bd5c967cfea817d 147077 hcxtools_6.2.4.orig.tar.gz 952262adb321f81dd3b2f6c1fc690a39382ee1145e98aa3f359c10af2bf8e203 5676 hcxtools_6.2.4-1.debian.tar.xz
Bug#984243: Help: mothur: ftbfs with GCC-11
Am Fri, Oct 22, 2021 at 07:46:35AM -0400 schrieb Aaron M. Ucko: > > # Get the list of all .cpp files, rename to .o files > > # > > OBJECTS=$(patsubst %.cpp,%.o,$(wildcard $(addsuffix *.cpp,$(subdirs > > OBJECTS+=$(patsubst %.c,%.o,$(wildcard $(addsuffix *.c,$(subdirs > > OBJECTS+=$(patsubst %.cpp,%.o,$(wildcard *.cpp)) > > OBJECTS+=$(patsubst %.c,%.o,$(wildcard *.c)) > > > > the right way to get the path correctly? Or what do you mean? > > Please try changing the last two lines to > > OBJECTS+=$(patsubst %.cpp,%.o,$(wildcard source/*.cpp)) > OBJECTS+=$(patsubst %.c,%.o,$(wildcard source/*.c)) > > to match the relevant sources' actual location; sorry if that was unclear. > (The existing setup only covers subdirectories of source, missing that > directory's immediate contents.) OK, did so but left me with cd source/uchime_src && export CXX=g++ && make clean && make && mv uchime ../../ && cd .. make[3]: Entering directory '/build/mothur-1.46.1/source/uchime_src' make[3]: warning: jobserver unavailable: using -j1. Add '+' to parent make rule. make[3]: Leaving directory '/build/mothur-1.46.1/source/uchime_src' make[3]: Entering directory '/build/mothur-1.46.1/source/uchime_src' make[3]: warning: jobserver unavailable: using -j1. Add '+' to parent make rule. g++ -g -o uchime g++: fatal error: no input files compilation terminated. I'm wondering why the makefile stopped working just because a new compiler version is used. :-( Kind regards Andreas. -- http://fam-tille.de
Bug#993967: License incompatible with current Qt
Control: severity -1 important On 25/10/2021 16:32, Andrej Shadura wrote: I just wanted to post a not-really-up-to-date update on this. The discussion continues on the mailing list here: https://groups.google.com/g/thg-dev/c/i3MChuOMWvw Also: I’m going to downgrade the severity for now, giving the upstream more time to try and resolve it. -- Cheers, Andrej
Processed: Re: License incompatible with current Qt
Processing control commands: > severity -1 important Bug #993967 [tortoisehg] License incompatible with PyQt5 Severity set to 'important' from 'serious' -- 993967: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993967 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#993967: License incompatible with current Qt
On Thu, 16 Sep 2021 15:12:42 +0100 Andrej Shadura wrote: Hi Bastian, On Wed, 8 Sep 2021 20:32:18 +0200 Bastian Germann wrote: > Package: tortoisehg > Severity: serious > > At https://groups.google.com/g/thg-dev/c/AYFxHk5aLKg/ I started a conversation about TortoiseHg > (GPLv2-only) having an incompatible license with the currently packaged PyQt5 version (GPLv3). In > almost a year, upstream did not do anything to handle the issue, so I file this bug. It should be > possible to convert the source to PySide2 or QtPy (handles PyQt and PySide versions). Thanks for this bug and initiating the discussion upstream. Could you please remind them of this issue? It would be really disappointing to lose thg for a reason this silly. I just wanted to post a not-really-up-to-date update on this. The discussion continues on the mailing list here: https://groups.google.com/g/thg-dev/c/i3MChuOMWvw -- Cheers, Andrej
Bug#997139: bacula: FTBFS: configure: error: cannot find required auxiliary files: config.rpath mkinstalldirs config.guess config.sub ltmain.sh install-sh
Um 21:04 Uhr am 23.10.21 schrieb Lucas Nussbaum:
> Relevant part (hopefully):
> > touch src/qt-console/tray-monitor/.libs/bacula-tray-monitor
> > chmod 755 src/qt-console/tray-monitor/.libs/bacula-tray-monitor
> > dh_auto_configure -- --enable-smartalloc --with-tcp-wrappers --with-openssl
> > --with-libiconv-prefix=/usr/include --with-readline=/usr/include/readline
> > --disable-conio --with-libintl-prefix=/usr/include
> > --docdir=\${prefix}/share/doc/bacula-common
> > --htmldir=\${prefix}/share/doc/bacula-common/html
> > --libdir=\${prefix}/lib/bacula --enable-batch-insert --enable-ipv6
> > --with-dir-password=XXX_DIRPASSWORD_XXX
> > --with-fd-password=XXX_FDPASSWORD_XXX --with-sd-password=XXX_SDPASSWORD_XXX
> > --with-mon-dir-password=XXX_MONDIRPASSWORD_XXX
> > --with-mon-fd-password=XXX_MONFDPASSWORD_XXX
> > --with-mon-sd-password=XXX_MONSDPASSWORD_XXX --with-db-name=XXX_DBNAME_XXX
> > --with-db-user=XXX_DBUSER_XXX --with-db-password=XXX_DBPASSWORD_XXX
> > --with-hostname=localhost --config-cache
> > --with-archivedir=/nonexistant/path/to/file/archive/dir
> > --sysconfdir=/etc/bacula --with-scriptdir=/etc/bacula/scripts
> > --sharedstatedir=/var/lib/bacula --localstatedir=/var/lib/bacula
> > --with-logdir=/var/log/bacula --with-pid-dir=/run/bacula
--with-smtp-host=localhost --with-working-dir=/var/lib/bacula
--with-subsys-dir=/run/lock --with-dump-email=root --with-job-email=root
--with-mysql --with-postgresql --with-sqlite3 --enable-bat --with-x
--disable-s3 --with-systemd=/lib/systemd/system
> > ./configure --build=x86_64-linux-gnu --prefix=/usr
> > --includedir=\${prefix}/include --mandir=\${prefix}/share/man
> > --infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var
> > --disable-option-checking --disable-silent-rules
> > --libdir=\${prefix}/lib/x86_64-linux-gnu --runstatedir=/run
> > --disable-maintainer-mode --disable-dependency-tracking --enable-smartalloc
> > --with-tcp-wrappers --with-openssl --with-libiconv-prefix=/usr/include
> > --with-readline=/usr/include/readline --disable-conio
> > --with-libintl-prefix=/usr/include
> > --docdir=\${prefix}/share/doc/bacula-common
> > --htmldir=\${prefix}/share/doc/bacula-common/html
> > --libdir=\${prefix}/lib/bacula --enable-batch-insert --enable-ipv6
> > --with-dir-password=XXX_DIRPASSWORD_XXX
> > --with-fd-password=XXX_FDPASSWORD_XXX --with-sd-password=XXX_SDPASSWORD_XXX
> > --with-mon-dir-password=XXX_MONDIRPASSWORD_XXX
> > --with-mon-fd-password=XXX_MONFDPASSWORD_XXX
> > --with-mon-sd-password=XXX_MONSDPASSWORD_XXX --with-db-name=XXX_DBNAME_XXX
> > --with-db-user=XXX_D
BUSER_XXX --with-db-password=XXX_DBPASSWORD_XXX --with-hostname=localhost
--config-cache --with-archivedir=/nonexistant/path/to/file/archive/dir
--sysconfdir=/etc/bacula --with-scriptdir=/etc/bacula/scripts
--sharedstatedir=/var/lib/bacula --localstatedir=/var/lib/bacula
--with-logdir=/var/log/bacula --with-pid-dir=/run/bacula
--with-smtp-host=localhost --with-working-dir=/var/lib/bacula
--with-subsys-dir=/run/lock --with-dump-email=root --with-job-email=root
--with-mysql --with-postgresql --with-sqlite3 --enable-bat --with-x
--disable-s3 --with-systemd=/lib/systemd/system
> > configure: creating cache config.cache
> > configure: error: cannot find required auxiliary files: config.rpath
> > mkinstalldirs config.guess config.sub ltmain.sh install-sh
> > tail -v -n \+0 config.log
Interesting.
I think this may be an autoconf2.71 problem or a dh problem
Debugging the generated configure script, I see that it tries to look in
the wrong place for the "autoconf/" directory when searching for the
auxiliary files:
+ case $as_dir in
+ as_dir=/autoconf/
+ as_found=:
+ printf '%s\n' 'configure:3618: trying /autoconf/'
+ ac_aux_dir_found=yes
+ ac_install_sh=
+ for ac_aux in $ac_aux_files
+ test xconfig.rpath = xinstall-sh
+ test -f /autoconf/config.rpath
+ ac_aux_dir_found=no
+ :
Obviously, "/autoconf/config.rpath" cannot exist.
Looking at the code in the generated configure script:
3595 # Locations in which to look for auxiliary files.
3596 ac_aux_dir_candidates="${BUILD_DIR}/autoconf"
it looks like $BUILD_DIR is empty, and when looking at the trace again, it
sure is:
+ ac_aux_dir_candidates=/autoconf
Comparing the old (supplied with the source) configure script and the
newly autoreconf'd one, it looks like BUILD_DIR is defined too late.
The old one has this
3159 BUILD_DIR=`pwd`
3160 cd ..
3161 TOP_DIR=`pwd`
3162 cd ${BUILD_DIR}
and only after that is BUILD_DIR used.
The new one uses BUILD_DIR earlier
3595 # Locations in which to look for auxiliary files.
3596 ac_aux_dir_candidates="${BUILD_DIR}/autoconf"
and the defintion is later
3760 BUILD_DIR=`pwd`
3761 cd ..
3762 TOP_DIR=`pwd`
3763 cd ${BUILD_DIR}
When I manually copy that code block above line 3596 then the configure
script starts to work again.
BUILD_DIR comes from autoconf/configure.in:
13 BUILD_DIR=`pwd`
14 cd ..
15
Bug#995123: cyrus-sasl2 FTBFS: sphinx: AttributeError: 'CyrusManualPageBuilder' object has no attribute 'settings'
Hi Vagrant, On Sun, Sep 26, 2021 at 06:39:54PM -0700, Vagrant Cascadian wrote: > I tested the attached patch which seems to fix this. This FTBFS has been open for about a month - are you going to NMU it Vagrant? Otherwise, I will upload an NMU to DELAYED/$SOME-DAYS soonish to move this forward. Michael -- Michael Banck Team Lead PostgreSQL Project Manager Tel.: +49 2166 9901-171 Mail: michael.ba...@credativ.de credativ GmbH, HRB Mönchengladbach 12080 USt-ID-Nummer: DE204566209 Trompeterallee 108, 41189 Mönchengladbach Management: Dr. Michael Meskes, Geoff Richardson, Peter Lilley Our handling of personal data is subject to: https://www.credativ.de/en/contact/privacy/
Bug#997576: marked as done (node-rollup-plugin-inject: FTBFS: dh_auto_test: error: cd ./legacy && sh -ex ../debian/nodejs/legacy/test returned exit code 3)
Your message dated Mon, 25 Oct 2021 12:49:01 +
with message-id
and subject line Bug#997576: fixed in node-rollup-plugin-inject 4.0.3+~3.0.2-1
has caused the Debian Bug report #997576,
regarding node-rollup-plugin-inject: FTBFS: dh_auto_test: error: cd ./legacy &&
sh -ex ../debian/nodejs/legacy/test returned exit code 3
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.)
--
997576: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997576
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-rollup-plugin-inject
Version: 4.0.2+~3.0.2-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_build --buildsystem=nodejs
> Found debian/nodejs/legacy/build
> cd ./legacy && sh -ex ../debian/nodejs/legacy/build
> + rollup -c
>
> src/index.js → dist/rollup-plugin-inject.cjs.js,
> dist/rollup-plugin-inject.es6.js...
> (!) Entry module "src/index.js" is implicitly using "default" export mode,
> which means for CommonJS output that its default export is assigned to
> "module.exports". For many tools, such CommonJS output will not be
> interchangeable with the original ES module. If this is intended, explicitly
> set "output.exports" to either "auto" or "default", otherwise you might want
> to consider changing the signature of "src/index.js" to use named exports
> only.
> https://rollupjs.org/guide/en/#outputexports
> src/index.js
> created dist/rollup-plugin-inject.cjs.js, dist/rollup-plugin-inject.es6.js in
> 51ms
> cd packages/inject && rollup -c
>
> src/index.js → dist/index.js, dist/index.es.js...
> (!) Entry module "src/index.js" is implicitly using "default" export mode,
> which means for CommonJS output that its default export is assigned to
> "module.exports". For many tools, such CommonJS output will not be
> interchangeable with the original ES module. If this is intended, explicitly
> set "output.exports" to either "auto" or "default", otherwise you might want
> to consider changing the signature of "src/index.js" to use named exports
> only.
> https://rollupjs.org/guide/en/#outputexports
> src/index.js
> created dist/index.js, dist/index.es.js in 90ms
> make[1]: Leaving directory '/<>'
>dh_auto_test --buildsystem=nodejs
> mkdir -p node_modules/\@rollup
> ln -s ../../packages/inject node_modules/\@rollup/plugin-inject
> cd ./legacy && sh -ex ../debian/nodejs/legacy/test
> + mocha -R spec
>
>
> rollup-plugin-inject
> undefined inserts a default import statement
> undefined uses the modules property
> 1) inserts a named import statement
> undefined overwrites keypaths
> undefined ignores existing imports
> undefined handles shadowed variables
> 2) handles shorthand properties
> undefined handles redundant keys
> 3) generates * imports
> rollup-plugin-inject: failed to parse
> /<>/legacy/test/samples/non-js/styles.css. Consider restricting
> the plugin to particular files via options.include
> undefined transpiles non-JS files but handles failures to parse
>
>
> 7 passing (98ms)
> 3 failing
>
> 1) rollup-plugin-inject
>inserts a named import statement:
>
> AssertionError [ERR_ASSERTION]: import { Promise as Promise$1 } from
> 'es6-promise';
>
> Promise$1.all([ thisThing, thatThing ]).then( () => someOtherThing );
>
> + expected - actual
>
> -false
> +true
>
> at Context. (test/test.js:50:12)
>
> 2) rollup-plugin-inject
>handles shorthand properties:
>
> AssertionError [ERR_ASSERTION]: import { Promise as Promise$1 } from
> 'es6-promise';
>
> const polyfills = { Promise: Promise$1 };
> polyfills.Promise.resolve().then( () => 'it works' );
>
> + expected - actual
>
> -false
> +true
>
> at Context. (test/test.js:106:12)
>
> 3) rollup-plugin-inject
>generates * imports:
>
> AssertionError [ERR_ASSERTION]: import * as foo from 'foo';
>
> console.log( foo.bar );
> console.log( foo.baz );
>
> + expected - actual
>
> -false
> +true
>
> at Context. (test/test.js:138:12)
>
>
>
> dh_auto_test: error: cd ./legacy && sh -ex ../debian/nodejs/legacy/test
> returned exit code 3
The full build log is available from:
http://qa-logs.debian.net/2021/10/23/node-rollup-plugin-inject_4.0.2+~3.0.2-1_unstable.log
A list of
Bug#997576: marked as pending in node-rollup-plugin-inject
Control: tag -1 pending Hello, Bug #997576 in node-rollup-plugin-inject 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/js-team/node-rollup-plugin-inject/-/commit/164b1a0532aa1175904b48ce5a756b5cf9b644d2 Fix legacy test Closes: #997576 (this message was generated automatically) -- Greetings https://bugs.debian.org/997576
Processed: Bug#997576 marked as pending in node-rollup-plugin-inject
Processing control commands: > tag -1 pending Bug #997576 [src:node-rollup-plugin-inject] node-rollup-plugin-inject: FTBFS: dh_auto_test: error: cd ./legacy && sh -ex ../debian/nodejs/legacy/test returned exit code 3 Added tag(s) pending. -- 997576: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997576 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#997591: marked as done (node-mini-css-extract-plugin: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1)
Your message dated Mon, 25 Oct 2021 12:18:37 + with message-id and subject line Bug#997591: fixed in node-mini-css-extract-plugin 1.3.3-2 has caused the Debian Bug report #997591, regarding node-mini-css-extract-plugin: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 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.) -- 997591: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997591 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-mini-css-extract-plugin Version: 1.3.3-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > dpkg-buildpackage > - > > Command: dpkg-buildpackage -us -uc -sa -rfakeroot > dpkg-buildpackage: info: source package node-mini-css-extract-plugin > dpkg-buildpackage: info: source version 1.3.3-1 > dpkg-buildpackage: info: source distribution unstable > dpkg-buildpackage: info: source changed by Xavier Guimard > dpkg-source --before-build . > dpkg-buildpackage: info: host architecture amd64 > debian/rules clean > dh clean >dh_auto_clean --buildsystem=nodejs > rm -rf ./node_modules/.cache >dh_clean > dpkg-source -b . > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-source: info: building node-mini-css-extract-plugin using existing > ./node-mini-css-extract-plugin_1.3.3.orig.tar.gz > dpkg-source: info: building node-mini-css-extract-plugin in > node-mini-css-extract-plugin_1.3.3-1.debian.tar.xz > dpkg-source: info: building node-mini-css-extract-plugin in > node-mini-css-extract-plugin_1.3.3-1.dsc > debian/rules binary > dh binary >dh_update_autotools_config >dh_autoreconf >dh_auto_configure --buildsystem=nodejs >dh_auto_build --buildsystem=nodejs > Found debian/nodejs/./build > cd ./. && sh -ex debian/nodejs/./build > + NODE_ENV=production babeljs src -d dist --ignore src/**/*.test.js > --copy-files > Successfully compiled 11 files with Babel (809ms). >dh_auto_test --buildsystem=nodejs > mkdir -p node_modules > ln -s ../. node_modules/mini-css-extract-plugin > /bin/sh -ex debian/tests/pkg-js/test > + jest --ci -u test/HMR.test.js test/validate-plugin-options.test.js > test/normalize-url.test.js test/cjs.test.js test/TestCache.test.js > FAIL test/HMR.test.js > ● HMR › should works > > The error below may be caused by using the wrong test environment, see > https://jestjs.io/docs/configuration#testenvironment-string. > Consider using the "jsdom" test environment. > > ReferenceError: document is not defined > > 28 | jest.spyOn(Date, 'now').mockImplementation(() => > 147942720); > 29 | > > 30 | document.head.innerHTML = ' href="/dist/main.css" />'; > | ^ > 31 | document.body.innerHTML = ' src="/dist/main.js">'; > 32 | }); > 33 | > > at Object. (test/HMR.test.js:30:5) > > ● HMR › should works with multiple updates > > The error below may be caused by using the wrong test environment, see > https://jestjs.io/docs/configuration#testenvironment-string. > Consider using the "jsdom" test environment. > > ReferenceError: document is not defined > > 28 | jest.spyOn(Date, 'now').mockImplementation(() => > 147942720); > 29 | > > 30 | document.head.innerHTML = ' href="/dist/main.css" />'; > | ^ > 31 | document.body.innerHTML = ' src="/dist/main.js">'; > 32 | }); > 33 | > > at Object. (test/HMR.test.js:30:5) > > ● HMR › should reloads with locals > > The error below may be caused by using the wrong test environment, see > https://jestjs.io/docs/configuration#testenvironment-string. > Consider using the "jsdom" test environment. > > ReferenceError: document is not defined > > 28 | jest.spyOn(Date, 'now').mockImplementation(() => > 147942720); > 29 | > > 30 | document.head.innerHTML = ' href="/dist/main.css" />'; > | ^ > 31 | document.body.innerHTML = ' src="/dist/main.js">'; > 32 | }); > 33 | > > at Object. (test/HMR.test.js:30:5) > > ● HMR › should work reload all css > > The error below may be caused by using the wrong test environment, see > https://jestjs.io/docs/configuration#testenvironment-string. > Consider using the "jsdom" test environment. > >
Bug#997584: marked as done (node-iconv-lite: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1)
Your message dated Mon, 25 Oct 2021 12:03:38 + with message-id and subject line Bug#997584: fixed in node-iconv-lite 0.6.3-1 has caused the Debian Bug report #997584, regarding node-iconv-lite: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 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.) -- 997584: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997584 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-iconv-lite Version: 0.5.1-3 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > dpkg-buildpackage > - > > Command: dpkg-buildpackage -us -uc -sa -rfakeroot > dpkg-buildpackage: info: source package node-iconv-lite > dpkg-buildpackage: info: source version 0.5.1-3 > dpkg-buildpackage: info: source distribution unstable > dpkg-buildpackage: info: source changed by Xavier Guimard > dpkg-source --before-build . > dpkg-buildpackage: info: host architecture amd64 > debian/rules clean > dh clean --with nodejs >dh_auto_clean --buildsystem=nodejs > rm -rf ./node_modules/.cache > rm -rf safer-buffer/node_modules/.cache >dh_clean > dpkg-source -b . > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-source: info: building node-iconv-lite using existing > ./node-iconv-lite_0.5.1.orig-safer-buffer.tar.gz > dpkg-source: info: building node-iconv-lite using existing > ./node-iconv-lite_0.5.1.orig.tar.gz > dpkg-source: info: using patch list from debian/patches/series > dpkg-source: info: building node-iconv-lite in > node-iconv-lite_0.5.1-3.debian.tar.xz > dpkg-source: info: building node-iconv-lite in node-iconv-lite_0.5.1-3.dsc > debian/rules binary > dh binary --with nodejs >dh_update_autotools_config >dh_autoreconf >dh_auto_configure --buildsystem=nodejs > mkdir node_modules > ln -s ../safer-buffer node_modules/safer-buffer >dh_auto_build --buildsystem=nodejs > No build command found, searching known files > No build command found, searching known files >dh_auto_test --buildsystem=nodejs > ln -s ../. node_modules/iconv-lite > /bin/sh -ex debian/tests/pkg-js/test > + mocha --bail --reporter spec --grep . > > Error: Don't support --bail performance test. > at Object. (/<>/test/performance.js:19:11) > at Module._compile (internal/modules/cjs/loader.js:999:30) > at Object.Module._extensions..js (internal/modules/cjs/loader.js:1027:10) > at Module.load (internal/modules/cjs/loader.js:863:32) > at Function.Module._load (internal/modules/cjs/loader.js:708:14) > at ModuleWrap. (internal/modules/esm/translators.js:188:29) > at ModuleJob.run (internal/modules/esm/module_job.js:145:37) > at async Loader.import (internal/modules/esm/loader.js:182:24) > at async formattedImport > (/usr/share/nodejs/mocha/lib/nodejs/esm-utils.js:7:14) > at async Object.exports.requireOrImport > (/usr/share/nodejs/mocha/lib/nodejs/esm-utils.js:48:32) > at async Object.exports.loadFilesAsync > (/usr/share/nodejs/mocha/lib/nodejs/esm-utils.js:88:20) > at async singleRun (/usr/share/nodejs/mocha/lib/cli/run-helpers.js:125:3) > at async Object.exports.handler > (/usr/share/nodejs/mocha/lib/cli/run.js:374:5) > dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1 The full build log is available from: http://qa-logs.debian.net/2021/10/23/node-iconv-lite_0.5.1-3_unstable.log 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 marking 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: node-iconv-lite Source-Version: 0.6.3-1 Done: Yadd We believe that the bug you reported is fixed in the latest version of node-iconv-lite, 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 997...@bugs.debian.org, and the maintainer will reopen the bug
Processed: Bug#997591 marked as pending in node-mini-css-extract-plugin
Processing control commands: > tag -1 pending Bug #997591 [src:node-mini-css-extract-plugin] node-mini-css-extract-plugin: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1 Added tag(s) pending. -- 997591: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997591 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#997591: marked as pending in node-mini-css-extract-plugin
Control: tag -1 pending Hello, Bug #997591 in node-mini-css-extract-plugin 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/js-team/node-mini-css-extract-plugin/-/commit/692e835a76bd485cc56976ab719ba71224ce810c Fix test for jest ≥ 27 Closes: #997591 (this message was generated automatically) -- Greetings https://bugs.debian.org/997591
Bug#997584: marked as pending in node-iconv-lite
Control: tag -1 pending Hello, Bug #997584 in node-iconv-lite 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/js-team/node-iconv-lite/-/commit/4080e96e55250a40a6dfbb50046524adac6680d3 Fix test Closes: #997584 (this message was generated automatically) -- Greetings https://bugs.debian.org/997584
Processed: Bug#997584 marked as pending in node-iconv-lite
Processing control commands: > tag -1 pending Bug #997584 [src:node-iconv-lite] node-iconv-lite: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1 Added tag(s) pending. -- 997584: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997584 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#996642: csh: FTBFS with glibc 2.32
Hi Alastair, On Sat, 16 Oct 2021 18:47:48 +0200 Graham Inggs wrote: Source: csh Version: 20110502-6 Severity: serious Tags: ftbfs patch bookworm sid Hi Maintainer As can be seen in reproducible builds [1], csh FTBFS since glibc 2.32 was uploaded. I've attached a patch from Ubuntu where this was fixed already. Can you please upload this with Graham's patch? Since this is triggering a huge number of (warnings for) autoremovals Nilesh OpenPGP_signature Description: OpenPGP digital signature
Processed: Re: [debian-mysql] Bug#996028: InnoDB: corrupted TRX_NO after upgrading to 10.3.31
Processing control commands: > severity -1 normal Bug #996028 [mariadb-server] InnoDB: corrupted TRX_NO after upgrading to 10.3.31 Severity set to 'normal' from 'grave' -- 996028: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996028 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#996028: [debian-mysql] Bug#996028: InnoDB: corrupted TRX_NO after upgrading to 10.3.31
Control: severity -1 normal On Thu, Oct 21, 2021 at 9:24 PM Marc Gallet wrote: > I've been brought to this bug by apt-listbugs while doing upgrades > on my buster install, warning me of a grave bug. We have two users who have experienced a potentially corrupted database (out of hundreds of thousands or even potentially millions of users, depending how one wants to extrapolate the popcon data). A bug report has been filed and it is kept open in case somebody could provide a way to reproduce the bug or report something actionable. Otherwise neither the Debian packagers nor upstream developers (and upstream does not even know about this bug, since it is still vague and no bug report has been filed upstream) will do anything about the bug report. I am now downgrading this bug report severity to "normal" so that it will not raise false alarms for random users. > I have not attempted the upgrade yet, since, after reading this bug, I > see a risk of data corruption and I would like to avoid going into > recovery procedures (from backups) as a result of what should be a > stable upgrade. You should have a backup anyway, that is just good practice while maintaining database systems. When you want to upgrade, run 'apt upgrade'. If your database is already broken/corrupted, the upgrade will not fix it. You can easily test your database by restarting it (and see that it restarts), read the logs and related documentation. Official Debian package documentation is the README files in the packaging, and they contain more tips about best practices. I recommend you use them as the primary source of information and don't put too much weight on a single bug report.
Bug#997398: marked as done (xmoto: FTBFS: dh_auto_configure: CMake Error: Unknown argument --localedir=${prefix}/share/games/locale)
Your message dated Mon, 25 Oct 2021 11:34:11 +
with message-id
and subject line Bug#997398: fixed in xmoto 0.6.1+repack-5
has caused the Debian Bug report #997398,
regarding xmoto: FTBFS: dh_auto_configure: CMake Error: Unknown argument
--localedir=${prefix}/share/games/locale
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.)
--
997398: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997398
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xmoto
Version: 0.6.1+repack-4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> rm -rf src/ode
> dh_auto_configure -- \
> --prefix=/usr \
> --bindir=\${prefix}/games \
> --datadir=\${prefix}/share/games \
> --mandir=\${prefix}/share/man \
> --localedir=\${prefix}/share/games/locale
> 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 -DCMAKE_INSTALL_RUNSTATEDIR=/run
> -DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=ON "-GUnix Makefiles"
> -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu
> --prefix=/usr --bindir=\${prefix}/games --datadir=\${prefix}/share/games
> --mandir=\${prefix}/share/man --localedir=\${prefix}/share/games/locale ..
> CMake Error: Unknown argument --localedir=${prefix}/share/games/locale
> CMake Error: Run 'cmake --help' for all supported options.
> dh_auto_configure: error: 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 -DCMAKE_INSTALL_RUNSTATEDIR=/run
> -DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=ON "-GUnix Makefiles"
> -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu
> --prefix=/usr --bindir=\${prefix}/games --datadir=\${prefix}/share/games
> --mandir=\${prefix}/share/man --localedir=\${prefix}/share/games/locale ..
> returned exit code 1
> make[1]: *** [debian/rules:13: override_dh_auto_configure] Error 2
The full build log is available from:
http://qa-logs.debian.net/2021/10/23/xmoto_0.6.1+repack-4_unstable.log
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 marking 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: xmoto
Source-Version: 0.6.1+repack-5
Done: Stephen Kitt
We believe that the bug you reported is fixed in the latest version of
xmoto, 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 997...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Stephen Kitt (supplier of updated xmoto 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: Mon, 25 Oct 2021 13:20:47 +0200
Source: xmoto
Architecture: source
Version: 0.6.1+repack-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team
Changed-By: Stephen Kitt
Closes: 997398
Changes:
xmoto (0.6.1+repack-5) unstable; urgency=medium
.
[ John Scott ]
* Add a superficial DEP-8 test that serving an X-Moto server works.
.
[ Stephen Kitt ]
* Drop the dh_auto_configure override, it’s obsolete since the switch
to CMake. Closes: #997398.
* Standards-Version 4.6.0, no change required.
Checksums-Sha1:
183c929fc6ae63a97b0bff817a0de062a0af96b5 2416 xmoto_0.6.1+repack-5.dsc
Bug#997190: patch for building qrq on GCC-11
Hello Tony, On Sun, Oct 24, 2021 at 06:34:44PM -0700, tony mancill wrote: > I recently applied a patch to the Debian packaging of qrq to enable > compilation with GCC-11, which enables -Werror=format-security. > > You can see the details of the build failure in > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997190. > > I believe the patch is generally useful/applicable to other users, and > since I didn't see an way to generate a pull-request against > https://git.fkurz.net/dj1yfk/qrq, I am attaching the patch. It is also > available here: > > https://salsa.debian.org/debian-hamradio-team/qrq/-/blob/62e1199c9418a2be2525f1d6d0cf56f0d59da5cc/debian/patches/warnings-as-errors.patch > > Note that the patch addresses a few other format warnings, although not > all of them. Let me know if you'd like me to pare the patch down to > only the format-security warnings. thanks for your patch! I applied it (manually, since there were some intermediate commits) in my repository: https://git.fkurz.net/dj1yfk/qrq/commit/834e339ab387d5cab80ca259b4826719a240ccf2 tnx & 73 Fabian, DJ1YFK -- Fabian Kurz, DJ1YFK Munich, Germany fab...@fkurz.net +49(174)6926713 https://fkurz.net/ Go Vegan! ☮
Bug#997820: python3-trezor: Depends: python3-click (< 8) but 8.0.2-1 is to be installed
Package: python3-trezor Version: 0.12.2-2 Severity: serious Tags: bookworm sid The following packages have unmet dependencies: python3-trezor : Depends: python3-click (< 8) but 8.0.2-1 is to be installed
Processed: Bug#997398 marked as pending in xmoto
Processing control commands:
> tag -1 pending
Bug #997398 [src:xmoto] xmoto: FTBFS: dh_auto_configure: CMake Error: Unknown
argument --localedir=${prefix}/share/games/locale
Added tag(s) pending.
--
997398: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997398
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#997398: marked as pending in xmoto
Control: tag -1 pending Hello, Bug #997398 in xmoto 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/games-team/xmoto/-/commit/4f93cb6df36b4bbba5b4015d5a7543128c3aa76d Drop the dh_auto_configure override Closes: #997398 (this message was generated automatically) -- Greetings https://bugs.debian.org/997398
Bug#997819: mikutter: Depends: ruby-diva (< 1.1) but 1.1.0-1 is to be installed
Package: mikutter Version: 4.1.3+dfsg1-1 Severity: serious Tags: bookworm sid The following packages have unmet dependencies: mikutter : Depends: ruby-diva (< 1.1) but 1.1.0-1 is to be installed
Bug#617856: New version of apt-show-versions fixes 617856
Hi Paul, I will try to upload a new release. I could not do so in the last weeks, because my signature-key had expired and the new one did not yet make it into the keyring. Greeting Christoph Am 20.10.21 um 07:09 schrieb Paul Wise: > On Fri, 8 Oct 2021 11:31:39 +0200 Christoph Martin wrote: > >> tags 617856 + pending >> thanks >> >> Upload of new version is pending. > > Could you upload the package? > OpenPGP_signature Description: OpenPGP digital signature
Bug#997700: marked as done (node-proxyquire: FTBFS: tests fail)
Your message dated Mon, 25 Oct 2021 10:48:40 + with message-id and subject line Bug#997700: fixed in node-proxyquire 2.1.3+~1.0.1+~1.0.2-12 has caused the Debian Bug report #997700, regarding node-proxyquire: 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.) -- 997700: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997700 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-proxyquire Version: 2.1.3+~1.0.1+~1.0.2-11 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > eslint --format tap --no-eslintrc --env es6,node --no-inline-config '**/*.js' > TAP version 13 > 1..59 > ok 1 - /<>/examples/api/api-test.js > ok 2 - /<>/examples/api/samples/bar.js > ok 3 - /<>/examples/api/samples/foo.js > ok 4 - /<>/examples/api/samples/stats.js > ok 5 - /<>/examples/async/foo-tests.js > ok 6 - /<>/examples/async/foo.js > ok 7 - /<>/examples/example-utils.js > ok 8 - /<>/examples/simple/foo.inlineoverride.test.js > ok 9 - /<>/examples/simple/foo.js > ok 10 - /<>/examples/simple/foo.test.js > ok 11 - /<>/examples/sinon/foo-tests.js > ok 12 - /<>/examples/sinon/foo.js > ok 13 - /<>/index.js > ok 14 - /<>/lib/is.js > ok 15 - /<>/lib/proxyquire-error.js > ok 16 - /<>/lib/proxyquire.js > ok 17 - /<>/test/proxyquire-api.js > ok 18 - /<>/test/proxyquire-argumentvalidation.js > ok 19 - /<>/test/proxyquire-cache.js > ok 20 - /<>/test/proxyquire-compat.js > ok 21 - /<>/test/proxyquire-extensions.js > ok 22 - /<>/test/proxyquire-global.js > ok 23 - /<>/test/proxyquire-independence.js > ok 24 - /<>/test/proxyquire-non-object.js > ok 25 - /<>/test/proxyquire-notexisting.js > ok 26 - /<>/test/proxyquire-relative-paths.js > ok 27 - /<>/test/proxyquire-remove.js > ok 28 - /<>/test/proxyquire-sub-dependencies.js > ok 29 - /<>/test/proxyquire.js > ok 30 - /<>/test/samples/bar.js > ok 31 - /<>/test/samples/boof.js > ok 32 - /<>/test/samples/cache/bar.js > ok 33 - /<>/test/samples/cache/foo.js > ok 34 - /<>/test/samples/extensions.js > ok 35 - /<>/test/samples/foo-singleton.js > ok 36 - /<>/test/samples/foo.js > ok 37 - /<>/test/samples/fooarray.js > ok 38 - /<>/test/samples/foobool.js > ok 39 - /<>/test/samples/foonum.js > ok 40 - /<>/test/samples/global/bar.js > ok 41 - /<>/test/samples/global/baz.js > ok 42 - /<>/test/samples/global/foo-deferred.js > ok 43 - /<>/test/samples/global/foo.js > ok 44 - /<>/test/samples/no-call-thru-test/index.js > ok 45 - /<>/test/samples/no-call-thru-test/required.js > ok 46 - /<>/test/samples/notexisting/foo-relative.js > ok 47 - /<>/test/samples/notexisting/foo.js > ok 48 - /<>/test/samples/relative-paths/a/index.js > ok 49 - /<>/test/samples/relative-paths/a/util.js > ok 50 - /<>/test/samples/relative-paths/b/index.js > ok 51 - /<>/test/samples/relative-paths/b/util.js > ok 52 - /<>/test/samples/stats.js > ok 53 - /<>/test/samples/sub-dependencies/bar.js > ok 54 - /<>/test/samples/sub-dependencies/baz.js > ok 55 - /<>/test/samples/sub-dependencies/foo.js > ok 56 - /<>/Xerror/index.js > ok 57 - /<>/Xerror/test.js > ok 58 - /<>/Xkeys/index.js > ok 59 - /<>/Xkeys/test.js > > tape Xerror/test.js Xkeys/test.js | debian/tap-todo \ > 'should be equal' > TAP version 13 > # (anonymous) > not ok 1 should be strictly equal > # skipped 0 > # skip-patterns 1 > make[1]: *** [debian/rules:22: override_dh_auto_test] Error 1 The full build log is available from: http://qa-logs.debian.net/2021/10/23/node-proxyquire_2.1.3+~1.0.1+~1.0.2-11_unstable.log 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 marking 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: node-proxyquire Source-Version: 2.1.3+~1.0.1+~1.0.2-12 Done: Yadd We believe that the bug you reported is fixed in the latest version of node-proxyquire, 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
Bug#997723: marked as done (node-cosmiconfig: FTBFS: Object is of type 'unknown'.)
Your message dated Mon, 25 Oct 2021 10:34:09 +
with message-id
and subject line Bug#997723: fixed in node-cosmiconfig 7.0.0+ds1-2
has caused the Debian Bug report #997723,
regarding node-cosmiconfig: FTBFS: Object is of type 'unknown'.
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.)
--
997723: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997723
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-cosmiconfig
Version: 7.0.0+ds1-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> babeljs-7 src -d dist --verbose --extensions .js,.ts --ignore
> '**/**/*.test.js,**/**/*.test.ts' --source-maps
> src/Explorer.ts -> dist/Explorer.js
> src/ExplorerBase.ts -> dist/ExplorerBase.js
> src/ExplorerSync.ts -> dist/ExplorerSync.js
> src/cacheWrapper.ts -> dist/cacheWrapper.js
> src/getDirectory.ts -> dist/getDirectory.js
> src/getPropertyByPath.ts -> dist/getPropertyByPath.js
> src/index.ts -> dist/index.js
> src/loaders.ts -> dist/loaders.js
> src/readFile.ts -> dist/readFile.js
> src/types.ts -> dist/types.js
> Successfully compiled 10 files with Babel (676ms).
> tsc --project tsconfig.types.json
> [96msrc/loaders.ts[0m:[93m29[0m:[93m5[0m - [91merror[0m[90m TS2571:
> [0mObject is of type 'unknown'.
>
> [7m29[0m error.message = `JSON Error in ${filepath}:\n${error.message}`;
> [7m [0m [91m~[0m
>
> [96msrc/loaders.ts[0m:[93m29[0m:[93m52[0m - [91merror[0m[90m TS2571:
> [0mObject is of type 'unknown'.
>
> [7m29[0m error.message = `JSON Error in ${filepath}:\n${error.message}`;
> [7m [0m [91m ~[0m
>
> [96msrc/loaders.ts[0m:[93m44[0m:[93m5[0m - [91merror[0m[90m TS2571:
> [0mObject is of type 'unknown'.
>
> [7m44[0m error.message = `YAML Error in ${filepath}:\n${error.message}`;
> [7m [0m [91m~[0m
>
> [96msrc/loaders.ts[0m:[93m44[0m:[93m52[0m - [91merror[0m[90m TS2571:
> [0mObject is of type 'unknown'.
>
> [7m44[0m error.message = `YAML Error in ${filepath}:\n${error.message}`;
> [7m [0m [91m ~[0m
>
> [96msrc/readFile.ts[0m:[93m34[0m:[93m36[0m - [91merror[0m[90m
> TS2571: [0mObject is of type 'unknown'.
>
> [7m34[0m if (throwNotFound === false && error.code === 'ENOENT') {
> [7m [0m [91m ~[0m
>
> [96msrc/readFile.ts[0m:[93m50[0m:[93m36[0m - [91merror[0m[90m
> TS2571: [0mObject is of type 'unknown'.
>
> [7m50[0m if (throwNotFound === false && error.code === 'ENOENT') {
> [7m [0m [91m ~[0m
>
>
> Found 6 errors.
>
> make[1]: *** [debian/rules:14: override_dh_auto_build] Error 2
The full build log is available from:
http://qa-logs.debian.net/2021/10/23/node-cosmiconfig_7.0.0+ds1-1_unstable.log
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 marking 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: node-cosmiconfig
Source-Version: 7.0.0+ds1-2
Done: Yadd
We believe that the bug you reported is fixed in the latest version of
node-cosmiconfig, 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 997...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Yadd (supplier of updated node-cosmiconfig 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: Mon, 25 Oct 2021 12:12:46 +0200
Source: node-cosmiconfig
Architecture: source
Version: 7.0.0+ds1-2
Distribution:
Processed: Bug#997700 marked as pending in node-proxyquire
Processing control commands: > tag -1 pending Bug #997700 [src:node-proxyquire] node-proxyquire: FTBFS: tests fail Added tag(s) pending. -- 997700: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997700 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#997700: marked as pending in node-proxyquire
Control: tag -1 pending Hello, Bug #997700 in node-proxyquire 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/js-team/node-proxyquire/-/commit/e26a89e2bd3443518f45941eaf6db7e35733f6e1 Add fix for test (error message changed Closes: #997700 (this message was generated automatically) -- Greetings https://bugs.debian.org/997700
Processed: Bug#997723 marked as pending in node-cosmiconfig
Processing control commands: > tag -1 pending Bug #997723 [src:node-cosmiconfig] node-cosmiconfig: FTBFS: Object is of type 'unknown'. Added tag(s) pending. -- 997723: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997723 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#997723: marked as pending in node-cosmiconfig
Control: tag -1 pending Hello, Bug #997723 in node-cosmiconfig 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/js-team/node-cosmiconfig/-/commit/53799ab46568a7f435b853e8500374463bcccd4d Add patch to workaround tsc update Closes: #997723 (this message was generated automatically) -- Greetings https://bugs.debian.org/997723
Bug#996642: csh: FTBFS with glibc 2.32
(Resending with a different email, since my earlier mail bounced back, because of your DNS seeing it with invalid SPF) Hi Alastair, On Sat, 16 Oct 2021 18:47:48 +0200 Graham Inggs wrote: > Source: csh > Version: 20110502-6 > Severity: serious > Tags: ftbfs patch bookworm sid > > Hi Maintainer > > As can be seen in reproducible builds [1], csh FTBFS since glibc 2.32 > was uploaded. > I've attached a patch from Ubuntu where this was fixed already. Can you please upload this with Graham's patch? Since this is triggering a huge number of (warnings for) autoremovals Nilesh
Bug#997582: marked as done (node-rollup-plugin-alias: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1)
Your message dated Mon, 25 Oct 2021 10:04:10 +
with message-id
and subject line Bug#997582: fixed in node-rollup-plugin-alias 3.1.1.repack-3
has caused the Debian Bug report #997582,
regarding node-rollup-plugin-alias: FTBFS: dh_auto_test: error: /bin/sh -ex
debian/tests/pkg-js/test returned exit code 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.)
--
997582: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997582
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-rollup-plugin-alias
Version: 3.1.1.repack-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> # Build @rollup/plugin-alias
> cd packages/alias && rollup -c
>
> src/index.ts → dist/index.js, dist/index.es.js...
> (!) Entry module "src/index.ts" is implicitly using "default" export mode,
> which means for CommonJS output that its default export is assigned to
> "module.exports". For many tools, such CommonJS output will not be
> interchangeable with the original ES module. If this is intended, explicitly
> set "output.exports" to either "auto" or "default", otherwise you might want
> to consider changing the signature of "src/index.ts" to use named exports
> only.
> https://rollupjs.org/guide/en/#outputexports
> src/index.ts
> (!) Plugin typescript: @rollup/plugin-typescript TS2307: Cannot find module
> 'os' or its corresponding type declarations.
> src/index.ts: (1:26)
>
> [7m1[0m import { platform } from 'os';
> [7m [0m [91m [0m
>
> (!) Plugin typescript: @rollup/plugin-typescript TS2307: Cannot find module
> 'rollup' or its corresponding type declarations.
> src/index.ts: (3:43)
>
> [7m3[0m import { PartialResolvedId, Plugin } from 'rollup';
> [7m [0m [91m [0m
>
> (!) Plugin typescript: @rollup/plugin-typescript TS2307: Cannot find module
> 'slash' or its corresponding type declarations.
> src/index.ts: (4:19)
>
> [7m4[0m import slash from 'slash';
> [7m [0m [91m ~~~[0m
>
> (!) Plugin typescript: @rollup/plugin-typescript TS2550: Property 'entries'
> does not exist on type 'ObjectConstructor'. Do you need to change your target
> library? Try changing the 'lib' compiler option to 'es2017' or later.
> src/index.ts: (46:17)
>
> [7m46[0m return Object.entries(entries).map(([key, value]) => {
> [7m [0m [91m~~~[0m
>
> (!) Plugin typescript: @rollup/plugin-typescript TS7031: Binding element
> 'key' implicitly has an 'any' type.
> src/index.ts: (46:40)
>
> [7m46[0m return Object.entries(entries).map(([key, value]) => {
> [7m [0m [91m ~~~[0m
>
> (!) Plugin typescript: @rollup/plugin-typescript TS7031: Binding element
> 'value' implicitly has an 'any' type.
> src/index.ts: (46:45)
>
> [7m46[0m return Object.entries(entries).map(([key, value]) => {
> [7m [0m [91m~[0m
>
> (!) Plugin typescript: @rollup/plugin-typescript TS7006: Parameter
> 'inputOptions' implicitly has an 'any' type.
> src/index.ts: (82:16)
>
> [7m82[0m buildStart(inputOptions) {
> [7m [0m [91m [0m
>
> (!) Plugin typescript: @rollup/plugin-typescript TS7006: Parameter 'importee'
> implicitly has an 'any' type.
> src/index.ts: (95:15)
>
> [7m95[0m resolveId(importee, importer) {
> [7m [0m [91m [0m
>
> (!) Plugin typescript: @rollup/plugin-typescript TS7006: Parameter 'importer'
> implicitly has an 'any' type.
> src/index.ts: (95:25)
>
> [7m95[0m resolveId(importee, importer) {
> [7m [0m [91m[0m
>
> (!) Plugin typescript: @rollup/plugin-typescript TS7006: Parameter 'resolved'
> implicitly has an 'any' type.
> src/index.ts: (114:74)
>
> [7m114[0m return this.resolve(updatedId, importer, { skipSelf: true
> }).then((resolved) => {
> [7m [0m [91m
> [0m
>
> (!) Plugin typescript: @rollup/plugin-typescript: Rollup 'sourcemap' option
> must be set to generate source maps.
> created dist/index.js, dist/index.es.js in 510ms
> make[1]: Leaving directory '/<>'
>dh_auto_test --buildsystem=nodejs
> /!\ 1/package.json not found
> Use of uninitialized
Processed: Bug#997582 marked as pending in node-rollup-plugin-alias
Processing control commands: > tag -1 pending Bug #997582 [src:node-rollup-plugin-alias] node-rollup-plugin-alias: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1 Added tag(s) pending. -- 997582: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997582 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#997582: marked as pending in node-rollup-plugin-alias
Control: tag -1 pending Hello, Bug #997582 in node-rollup-plugin-alias 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/js-team/node-rollup-plugin-alias/-/commit/6cb18c3d10499e7674726fb285e1776d4b90a19d Fix test for tape ≥ 5 Closes: #997582 (this message was generated automatically) -- Greetings https://bugs.debian.org/997582
Bug#997577: marked as done (node-babel-loader: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1)
Your message dated Mon, 25 Oct 2021 09:20:19 + with message-id and subject line Bug#997577: fixed in node-babel-loader 8.2.3-1 has caused the Debian Bug report #997577, regarding node-babel-loader: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 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.) -- 997577: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997577 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-babel-loader Version: 8.2.2-5 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > babeljs src -d lib --no-babelrc --copy-files > Successfully compiled 5 files with Babel (576ms). > sed -i '1s/^/"use strict";\n\n/' lib/*.js > make[1]: Leaving directory '/<>' >dh_auto_test --buildsystem=nodejs > mkdir -p node_modules > ln -s ../debian/tests/test_modules/pnp-webpack-plugin > node_modules/pnp-webpack-plugin > ln -s ../debian/tests/test_modules/react-intl-webpack-plugin > node_modules/react-intl-webpack-plugin > ln -s ../debian/tests/test_modules/ts-pnp node_modules/ts-pnp > ln -s ../. node_modules/babel-loader > /bin/sh -ex debian/tests/pkg-js/test > + mkdir -p test/output/cache/cachefiles > + tape test/cache.test.js test/loader.test.js test/metadata.test.js > test/options.test.js test/sourcemaps.test.js > TAP version 13 > # should output files to cache directory > # should output json.gz files to standard cache dir by default > # should output non-compressed files to standard cache dir when > cacheCompression is set to false > # should output files to standard cache dir if set to true in query > # should read from cache directory if cached file exists > # should have one file per module > # should generate a new file if the identifier changes > # should allow to specify the .babelrc file > # should transpile the code snippet > # should not throw error on syntax error > # should not throw without config > # should return compilation errors with the message included in the stack > trace > # should load ESM config files > # should throw error > # should interpret options given to the loader > not ok 1 .end() already called: should be truthy > --- > operator: fail > at: (/<>/test/loader.test.js:73:11) > stack: |- > Error: .end() already called: should be truthy > at Test.assert [as _assert] > (/usr/share/nodejs/tape/lib/test.js:311:54) > at Test.bound [as _assert] > (/usr/share/nodejs/tape/lib/test.js:96:32) > at Test.fail (/usr/share/nodejs/tape/lib/test.js:405:10) > at Test.bound [as fail] (/usr/share/nodejs/tape/lib/test.js:96:32) > at Test.assert [as _assert] > (/usr/share/nodejs/tape/lib/test.js:289:14) > at Test.bound [as _assert] > (/usr/share/nodejs/tape/lib/test.js:96:32) > at Test.assert (/usr/share/nodejs/tape/lib/test.js:430:10) > at Test.bound [as true] (/usr/share/nodejs/tape/lib/test.js:96:32) > at /<>/test/loader.test.js:73:11 > at finalCallback (/usr/share/nodejs/webpack/lib/Compiler.js:257:39) > ... > not ok 2 .end() already called: should be truthy > --- > operator: fail > at: (/<>/test/loader.test.js:74:11) > stack: |- > Error: .end() already called: should be truthy > at Test.assert [as _assert] > (/usr/share/nodejs/tape/lib/test.js:311:54) > at Test.bound [as _assert] > (/usr/share/nodejs/tape/lib/test.js:96:32) > at Test.fail (/usr/share/nodejs/tape/lib/test.js:405:10) > at Test.bound [as fail] (/usr/share/nodejs/tape/lib/test.js:96:32) > at Test.assert [as _assert] > (/usr/share/nodejs/tape/lib/test.js:289:14) > at Test.bound [as _assert] > (/usr/share/nodejs/tape/lib/test.js:96:32) > at Test.assert (/usr/share/nodejs/tape/lib/test.js:430:10) > at Test.bound [as true] (/usr/share/nodejs/tape/lib/test.js:96:32) > at /<>/test/loader.test.js:74:11 > at finalCallback (/usr/share/nodejs/webpack/lib/Compiler.js:257:39) > ... > not ok 3 .end() already called: should be deeply equivalent > --- > operator: fail > at: (/<>/test/loader.test.js:75:7) > stack: |- > Error: .end() already called: should be deeply equivalent > at Test.assert [as _assert] >
Bug#997765: closing 997765
close 997765 thanks
Processed: closing 997765
Processing commands for cont...@bugs.debian.org: > close 997765 Bug #997765 [src:pglogical] pglogical: FTBFS: Error: debian/control needs updating from debian/control.in. Run 'pg_buildext updatecontrol'. Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 997765: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997765 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#997577 marked as pending in node-babel-loader
Processing control commands: > tag -1 pending Bug #997577 [src:node-babel-loader] node-babel-loader: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1 Added tag(s) pending. -- 997577: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997577 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#997577: marked as pending in node-babel-loader
Control: tag -1 pending Hello, Bug #997577 in node-babel-loader 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/js-team/node-babel-loader/-/commit/ff0f89b2886516127db85c06b3f147861607a7b0 Fix test patch for tape ≥ 5 Closes: #997577 (this message was generated automatically) -- Greetings https://bugs.debian.org/997577
Processed: found 997806 in 1.0.0.errata1.avif-1, notfound 997806 in 1.0.0-errata1.avif-1
Processing commands for cont...@bugs.debian.org: > found 997806 1.0.0.errata1.avif-1 Bug #997806 [src:aom] aom: possible ABI breakage; causes ffmpeg autopkgtests failures Marked as found in versions aom/1.0.0.errata1.avif-1. > notfound 997806 1.0.0-errata1.avif-1 Bug #997806 [src:aom] aom: possible ABI breakage; causes ffmpeg autopkgtests failures The source 'aom' and version '1.0.0-errata1.avif-1' do not appear to match any binary packages No longer marked as found in versions aom/1.0.0-errata1.avif-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 997806: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997806 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
