Bug#1041451: gmap: FTBFS on all !amd64 archs
Source: gmap Version: 2023-06-01+ds-1 Severity: serious Dear Maintainer, gmap fails to build on all architectures except amd64. It compiles, but seems to fail it's build time tests, in particular align.test > 138435 AACAGCTA > > 4617 AACAGCTA > > FAIL align.test (exit status: 1) Testsuite summary for gmap 2023-06-01 # TOTAL: 4 # PASS: 3 # SKIP: 0 # XFAIL: 0 # FAIL: 1 # XPASS: 0 # ERROR: 0 -- System Information: Debian Release: 12.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-9-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=en_IN, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8), LANGUAGE=en_US.UTF-8 Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#1040694: marked as done (Package has to go through a proper transition process)
Your message dated Wed, 19 Jul 2023 06:18:57 + with message-id and subject line Bug#1040694: fixed in coinor-cbc 2.10.10+really2.10.8+ds1-1 has caused the Debian Bug report #1040694, regarding Package has to go through a proper transition process 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.) -- 1040694: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040694 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: coinor-cbc Version: 2.10.10+ds1-1 Severity: important X-Debbugs-Cc: schuel...@phimeca.com Dear Maintainer, Starting from version 2.10.10+ds1-1 (2.10.8+ds1-1 was OK), one of the build-time tests of openturns started to fail: t_Bonmin_std. Running it with gdb I get: --->8 (gdb) run Starting program: /build/openturns-eQ5lBV/openturns-1.20/builddir/lib/test/t_Bonmin_std [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". class=Bonmin algorithm=B-BB options= mu_oracle=loqo Program received signal SIGSEGV, Segmentation fault. 0x71ce1347 in CbcModel::initialSolve() () from /usr/lib/x86_64-linux-gnu/libCbc.so.3 (gdb) bt #0 0x71ce1347 in CbcModel::initialSolve() () from /usr/lib/x86_64-linux-gnu/libCbc.so.3 #1 0x748a2705 in Bonmin::Bab::branchAndBound(Bonmin::BabSetupBase&) () from /usr/lib/x86_64-linux-gnu/libbonmin.so.4 #2 0x7755b48e in OT::Bonmin::run (this=this@entry=0x7fffe440) at ./lib/src/Base/Optim/Bonmin.cxx:174 #3 0xf285 in main () at ./lib/test/t_Bonmin_std.cxx:131 --->8 which indicates a problem in coinor-cbc. The above backtrace is somewhat reminiscent of the one of the issue https://github.com/coin-or/Cbc/issues/591 which has been fixed in upstream version 2.10.10. I suspect a close issue is showing up here. Thanks a lot for your help, -- Pierre --- End Message --- --- Begin Message --- Source: coinor-cbc Source-Version: 2.10.10+really2.10.8+ds1-1 Done: Pierre Gruet We believe that the bug you reported is fixed in the latest version of coinor-cbc, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1040...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Pierre Gruet (supplier of updated coinor-cbc package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 19 Jul 2023 07:43:09 +0200 Source: coinor-cbc Architecture: source Version: 2.10.10+really2.10.8+ds1-1 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Pierre Gruet Closes: 1040694 Changes: coinor-cbc (2.10.10+really2.10.8+ds1-1) unstable; urgency=medium . * Team upload * New upstream version 2.10.10+really2.10.8+ds1, to prepare the transition from 2.10.8 to 2.10.10 (Closes: #1040694) Checksums-Sha1: 59e5afddc486311be2fc5fd4b0c493d4f570d9ad 2478 coinor-cbc_2.10.10+really2.10.8+ds1-1.dsc e2c845784df439ed5c5e1a5272c8f5b9cdeba057 884404 coinor-cbc_2.10.10+really2.10.8+ds1.orig.tar.xz 88ea478b18c443e3cdf36fe4b77f2d3b89ec35db 12768 coinor-cbc_2.10.10+really2.10.8+ds1-1.debian.tar.xz 6d0806ef55579574d7ae2406c58eca54c8eac8ca 10541 coinor-cbc_2.10.10+really2.10.8+ds1-1_amd64.buildinfo Checksums-Sha256: 3b1d29836164ea3dba7e887420eec5948d7c64e27d454726bd7cb6f7731a75eb 2478 coinor-cbc_2.10.10+really2.10.8+ds1-1.dsc d59a04c342a0705245a7b82aba280d30f1c557f05bd1ba3ec3e5a9a7bd00b324 884404 coinor-cbc_2.10.10+really2.10.8+ds1.orig.tar.xz 250598917fd7e4be2a4aa22b3067f1fb1659e0d5f1f591fe91e7a52dfdd3392f 12768 coinor-cbc_2.10.10+really2.10.8+ds1-1.debian.tar.xz 1bcf0fbff985bb6624c4f56bb1ca8b9ffae6a338f46753d5b21ac72f9ef94623 10541 coinor-cbc_2.10.10+really2.10.8+ds1-1_amd64.buildinfo Files: e1e4cc6758ca90429b8642006db9f88c 2478 science optional coinor-cbc_2.10.10+really2.10.8+ds1-1.dsc cf5fb0921e5c03d0677329073df7f504 884404 science optional coinor-cbc_2.10.10+really2.10.8+ds1.orig.tar.xz 84b182670e3ed084b96babc6f63fc19a 12768 science optional coinor-cbc_2.10.10+really2.10.8+ds1-1.debian.tar.xz b95c5aaf807e16d02
Bug#1040566: let logol be removed
Le mer. 19 juil. 2023, 06:58, Andreas Tille a écrit : > Hi Olivier, > > Am Mon, Jul 17, 2023 at 12:13:30PM +0200 schrieb olivier sallou: > > logol is not maintained anymore for quite some time now > > > > effort to keep in line with swi-prolog updates (need to recompile on each > > ABI break of swi-prolog) AND biojava requires frequent work for an old > > software with low usage. > > > > I would let it be removed > > You introduced the package so you know its usage best. I think any > removal should be announced on debian-med@l.d.o which I'm doing hereby. > > IMHO if the fix would be "simple" (in terms of needs only less than > 10min) keeping it might be worth it. Otherwise its a good time in the > beginning of the release process to remove packages that just drain > developer resources and do not serve a mentionable amount of users. > It would require analysis and many updates, so quite some efforts for unmaintained software and targetting low number of users (sure of that), so i am for removal. Olivier > > Kind regards > Andreas. > > -- > http://fam-tille.de > >
Processed: tagging 1040853
Processing commands for cont...@bugs.debian.org: > tags 1040853 + confirmed pending Bug #1040853 [src:python-lockfile] python-lockfile autopkg test fail with setuptools 68 Ignoring request to alter tags of bug #1040853 to the same tags previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 1040853: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040853 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1037604: marked as done (chromium: ftbfs with GCC-13)
Your message dated Wed, 19 Jul 2023 05:37:15 + with message-id and subject line Bug#1037604: fixed in chromium 115.0.5790.98-1 has caused the Debian Bug report #1037604, regarding chromium: ftbfs with GCC-13 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1037604: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037604 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:chromium Version: 113.0.5672.126-1 Severity: normal Tags: sid trixie User: debian-...@lists.debian.org Usertags: ftbfs-gcc-13 [This bug is targeted to the upcoming trixie release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-13/g++-13, but succeeds to build with gcc-12/g++-12. The severity of this report will be raised before the trixie release. The full build log can be found at: http://qa-logs.debian.net/2023/05/22/logs/chromium_113.0.5672.126-1_unstable_gccexp.log The last lines of the build log are at the end of this report. To build with GCC 13, either set CC=gcc-13 CXX=g++-13 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-13/porting_to.html [...] [202/55973] COPY ../../chrome/browser/resources/bluetooth_internals/page_manager.js gen/chrome/browser/resources/bluetooth_internals/page_manager.js [203/55973] COPY ../../chrome/browser/resources/bluetooth_internals/page.js gen/chrome/browser/resources/bluetooth_internals/page.js [204/55973] COPY ../../chrome/browser/resources/bluetooth_internals/service_list.js gen/chrome/browser/resources/bluetooth_internals/service_list.js [205/55973] COPY ../../chrome/browser/resources/bluetooth_internals/service_list_item.js gen/chrome/browser/resources/bluetooth_internals/service_list_item.js [206/55973] COPY ../../chrome/browser/resources/bluetooth_internals/sidebar.js gen/chrome/browser/resources/bluetooth_internals/sidebar.js [207/55973] ACTION //chrome/browser/new_tab_page/modules/recipes:mojo_bindings__type_mappings__validator(//build/toolchain/linux/unbundle:default) [208/55973] COPY ../../chrome/browser/resources/bluetooth_internals/snackbar.js gen/chrome/browser/resources/bluetooth_internals/snackbar.js [209/55973] STAMP obj/chrome/browser/new_tab_page/modules/recipes/mojo_bindings__type_mappings__validator.stamp [210/55973] COPY ../../chrome/browser/resources/bluetooth_internals/value_control.js gen/chrome/browser/resources/bluetooth_internals/value_control.js [211/55973] STAMP obj/chrome/browser/resources/bluetooth_internals/copy_files.stamp [212/55973] COPY ../../chrome/browser/resources/media/mei_preload/manifest.json MEIPreload/manifest.json [213/55973] COPY ../../chrome/browser/resources/media/mei_preload/preloaded_data.pb MEIPreload/preloaded_data.pb [214/55973] STAMP obj/chrome/browser/resources/media/mei_preload/component.stamp [215/55973] COPY ../../third_party/fusejs/dist/fuse.basic.esm.min.js gen/chrome/browser/resources/tab_search/preprocessed/fuse.js [216/55973] STAMP obj/chrome/browser/resources/tab_search/copy_fuse.stamp [217/55973] COPY ../../third_party/fusejs/dist/fuse.d.ts gen/chrome/browser/resources/tab_search/preprocessed/fuse.d.ts [218/55973] STAMP obj/chrome/browser/resources/tab_search/copy_fuse_dts.stamp [219/55973] COPY ../../third_party/fusejs/dist/fuse.d.ts gen/chrome/browser/resources/tab_search/tsc/fuse.d.ts [220/55973] STAMP obj/chrome/browser/resources/tab_search/copy_fuse_dts_tsc.stamp [221/55973] STAMP obj/chrome/browser/ui/tabs/tab_enums.stamp [222/55973] STAMP obj/chrome/common/apps/platform_apps/api/generated_api_types_schema_generator.inputdeps.stamp [223/55973] STAMP obj/chrome/common/extensions/api/generated_api_types_schema_generator.inputdeps.stamp [224/55973] ACTION //chrome/browser/new_tab_page/modules/safe_browsing:mojo_bindings__type_mappings__validator(//build/toolchain/linux/unbundle:default) [225/55973] STAMP obj/chrome/browser/new_tab_page/modules/safe_browsing/mojo_bindings__type_mappings__validator.stamp [226/55973] CXX obj/chrome/installer/util/constants/initial_p
Bug#1040566: let logol be removed
Hi Olivier, Am Mon, Jul 17, 2023 at 12:13:30PM +0200 schrieb olivier sallou: > logol is not maintained anymore for quite some time now > > effort to keep in line with swi-prolog updates (need to recompile on each > ABI break of swi-prolog) AND biojava requires frequent work for an old > software with low usage. > > I would let it be removed You introduced the package so you know its usage best. I think any removal should be announced on debian-med@l.d.o which I'm doing hereby. IMHO if the fix would be "simple" (in terms of needs only less than 10min) keeping it might be worth it. Otherwise its a good time in the beginning of the release process to remove packages that just drain developer resources and do not serve a mentionable amount of users. Kind regards Andreas. -- http://fam-tille.de
Bug#1041387: marked as done (libpdfbox-java: missing Breaks+Replaces: libpdfbox-java-doc (<< 1:1.8.16-3))
Your message dated Wed, 19 Jul 2023 04:34:27 + with message-id and subject line Bug#1041387: fixed in libpdfbox-java 1:1.8.16-4 has caused the Debian Bug report #1041387, regarding libpdfbox-java: missing Breaks+Replaces: libpdfbox-java-doc (<< 1:1.8.16-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.) -- 1041387: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041387 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libpdfbox-java Version: 1:1.8.16-3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'testing'. It installed fine in 'testing', then the upgrade to 'sid' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. 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 .../libpdfbox-java_1%3a1.8.16-3_all.deb ... Unpacking libpdfbox-java (1:1.8.16-3) ... dpkg: error processing archive /var/cache/apt/archives/libpdfbox-java_1%3a1.8.16-3_all.deb (--unpack): trying to overwrite '/usr/share/doc/libpdfbox-java/examples/pom.xml', which is also in package libpdfbox-java-doc 1:1.8.16-2 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/libpdfbox-java_1%3a1.8.16-3_all.deb cheers, Andreas libpdfbox-java-doc=1:1.8.16-2_libpdfbox-java=1:1.8.16-3.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: libpdfbox-java Source-Version: 1:1.8.16-4 Done: tony mancill We believe that the bug you reported is fixed in the latest version of libpdfbox-java, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1041...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. tony mancill (supplier of updated libpdfbox-java 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, 18 Jul 2023 07:26:09 -0700 Source: libpdfbox-java Architecture: source Version: 1:1.8.16-4 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers Changed-By: tony mancill Closes: 1041387 Changes: libpdfbox-java (1:1.8.16-4) unstable; urgency=medium . * Drop examples from libpdfbox-java to avoid overwriting files in the deprecated libpdfbox-java-doc binary package (Closes: #1041387) Checksums-Sha1: e70c9ceb9bad4c4b5d4a6c425fb83ea3e15506e8 2415 libpdfbox-java_1.8.16-4.dsc ee7a9d984d7c600758f37daee1fbfd0a21505cd7 11548 libpdfbox-java_1.8.16-4.debian.tar.xz a20b701360768bd230a96e9a3a0648543dad049f 16994 libpdfbox-java_1.8.16-4_amd64.buildinfo Checksums-Sha256: 8ac744ec22706271e575f8ac49ab355e99392863125649c29131189ccfec5116 2415 libpdfbox-java_1.8.16-4.dsc 95b9f436618865d4d36ecb46edc57d0c2a23f96c5060d2a52816f27bcdb45a73 11548 libpdfbox-java_1.8.16-4.debian.tar.xz 847fe500dc3453355a2e223bbfaf9dd50dee907113e8701239f00de1bf331fd4 16994 libpdfbox-java_1.8.16-4_amd64.buildinfo Files: b73106a9c21395e9c90f0f6f3719e954 2415 java optional libpdfbox-java_1.8.16-4.dsc 7b54af2c88ef858c881c903b0ab67a23 11548 java optional libpdfbox-java_1.8.16-4.debian.tar.xz afcd6233623e811f274d6628eebec323 16994 java optional libpdfbox-java_1.8.16-4_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEE5Qr9Va3SequXFjqLIdIFiZdLPpYFAmS3YvQUHHRtYW5jaWxs QGRlYmlhbi5vcmcACgkQIdIFiZdLPpZdBg/+MSebwv3IF2+EpyArzg14l1YxxV7M 1adUHjl8D3paiT3TWhkxj/v8zHZ52X3MoynDReZckOBNw5ponz7lN1G1T04scuWq aDO05HxAQ1EZMtvShnMr4bLoDRVNgpKbQ1XVpdolCApL0BXfxtlh7BD4o6SAdzxF up/WwP/nAy7s3YMGfs4b+/u+n9sdCxkCZUpJaAkbSq2H75e0zC8roWVT0mmaAvI+ Wvb1zHb7mPU+GTSVrb+MrZh/gYBzwBue3/68BiM0cZWwrgRF2VGuATTBf7vB5y2t 2gPrI3M3zMliv/ReCDtDemA3MDZMVjI4UweP+mwNLLbOps4r0/xc6997TLU8x6VY z3pi0u4fP+mKg/cnuQNr2HepfHzIMS6ydXT5D0En1/CGwBL0lejCMusHmA4SXCyz y/j3CqHYya/YbWG5eeFGqYxJcxjWYw2rsTA83tsY4L5H2LYSETeb3LkxEZYh8p6D DvXBVvnO6R3kdh++SzUv1j2HDMyDe5ZdGDb4U7YwXOtdtGsq57oRPAQQCQ0aAFxP 1bo10bnEXz42v0JaKvf0xfv36xGN4RamyCHfo/YVzsQDcbDjC95GB4/fnPi8pFK
Bug#1041410: marked as done (libdogleg-dev: missing Breaks+Replaces: libdogleg-doc (<< 0.16-2))
Your message dated Wed, 19 Jul 2023 04:34:09 + with message-id and subject line Bug#1041410: fixed in libdogleg 0.16-3 has caused the Debian Bug report #1041410, regarding libdogleg-dev: missing Breaks+Replaces: libdogleg-doc (<< 0.16-2) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1041410: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041410 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libdogleg-dev Version: 0.16-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'testing'. It installed fine in 'testing', then the upgrade to 'sid' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. 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 .../libdogleg-dev_0.16-2_amd64.deb ... Unpacking libdogleg-dev:amd64 (0.16-2) ... dpkg: error processing archive /var/cache/apt/archives/libdogleg-dev_0.16-2_amd64.deb (--unpack): trying to overwrite '/usr/share/man/man3/libdogleg.3.gz', which is also in package libdogleg-doc 0.15.4-2 Errors were encountered while processing: /var/cache/apt/archives/libdogleg-dev_0.16-2_amd64.deb And you still have a Depends on the no longer built libdogleg-doc cheers, Andreas --- End Message --- --- Begin Message --- Source: libdogleg Source-Version: 0.16-3 Done: Dima Kogan We believe that the bug you reported is fixed in the latest version of libdogleg, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1041...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dima Kogan (supplier of updated libdogleg 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, 18 Jul 2023 21:16:31 -0700 Source: libdogleg Architecture: source Version: 0.16-3 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Dima Kogan Closes: 1041410 Changes: libdogleg (0.16-3) unstable; urgency=medium . * Added forgotten Breaks, Replaces tags (Closes: #1041410) Checksums-Sha1: a339bdd99b89517a1b06f23a8707b1fee866ed61 2042 libdogleg_0.16-3.dsc cc1e801a93744bfac2eeb412bba12d3d060e1433 3420 libdogleg_0.16-3.debian.tar.xz c8db6fd5171e34987119adfa4b447a2f989de8d8 8178 libdogleg_0.16-3_amd64.buildinfo Checksums-Sha256: e63eb1dde5eba4bdb208c0f6acb58b0f611c958af9adfc3c2fba6a1d2492d589 2042 libdogleg_0.16-3.dsc d2119527e5bf4f97c552b1474c2e6e06493f8de43fcc6567ffc6303b56342572 3420 libdogleg_0.16-3.debian.tar.xz ea8b378b3afcbc97262a8daa462dc9e4a5ee9620374385a6933cb89da3342b6e 8178 libdogleg_0.16-3_amd64.buildinfo Files: 26a9cf7fd3346e1b15a3a8f6659d5340 2042 science optional libdogleg_0.16-3.dsc 805cec4b3cc37769765e6b90438d800b 3420 science optional libdogleg_0.16-3.debian.tar.xz dd5885d31ed38818075486474bc51577 8178 science optional libdogleg_0.16-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEteL6GQ/fmv4hiInPrMfCzzCUEYgFAmS3ZJgACgkQrMfCzzCU EYjTVhAAop5jfRqVPsweOaGzxfkbIiKlPWXiQg8cha1TK+n33aNvQeRtA2UZXNb1 djMbmQ8RhHxt0bjycncK0d5Nnk6AlSeNSE6Tr5SrSnImA9v1t1fmSsaaRcc4Nmzw HNyve+YfVGEHWGxdVtt7wJWidEAZO81edZjyzkjTOGrJ65ORgOc8FyMZxfjl6E/k faP+ol4mcgsFdsE2lGylWUJl3uzcDRsgJOd1PslpLSYbldMCYup6JiiI8TroAzaB 0pbShb/HL3tT8A4SOHhBD16BpnOPQgytePw+UBmjBjHHdx/n+7O6GebMjdLjTWd3 /yEJdIEBBXU17FPiQ54YEFUEfFm8jS9nch/UA8SBk2iCBKTxU21TWmVOkEzO0Qw1 stQAd07bBny62TW2rrRKKKRx7enzk/hyG1ISaVvWt3qvmEISjRn+eos9KGWNO4B2 EnVvb9guwrUaL4U3H+uoBwF2Og31JZiHnIiT3Oh6Hoqx9wov/gtzZW1by1DPkvCG cqqQRkF8+QF9wTPIibJNjV0cT5SO6vuDvRvZIZ+dKsVwsMVDbRq6sOE6av6Ehtsp Zn2e6wot+5A2LbBLCyxYIiTDjofQxoQh42x2QP6+Vx07ymEyAV49Uj7PiDVnbOf+ vQh89rMHZG5lfyGeEj207Ul6/E41AOgns9H98JbX83+NSzLrxgc= =Qx6c -END PGP SIGNATURE End Message ---
Bug#1041410: libdogleg-dev: missing Breaks+Replaces: libdogleg-doc (<< 0.16-2)
Thank you very much for the report. I completely forgot about these. Fixed just now.
Bug#1041387: marked as pending in libpdfbox-java
Control: tag -1 pending Hello, Bug #1041387 in libpdfbox-java 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/java-team/libpdfbox-java/-/commit/5ff86861b8907e1ad4c8275f5b838e1ec1ed6acb Drop examples from libpdfbox-java (Closes: #1041387) (this message was generated automatically) -- Greetings https://bugs.debian.org/1041387
Processed: Bug#1041387 marked as pending in libpdfbox-java
Processing control commands: > tag -1 pending Bug #1041387 [libpdfbox-java] libpdfbox-java: missing Breaks+Replaces: libpdfbox-java-doc (<< 1:1.8.16-3) Added tag(s) pending. -- 1041387: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041387 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1040629: Additional information
I have encountered the same error when running tests locally, but only
seen it once and could not reproduce it.
But when running a test against against pillow 10.0.0-1 the following
error occurs[1]
==
FAIL: test_process_apk (__main__.UpdateTest.test_process_apk)
--
Traceback (most recent call last):
File "/tmp/autopkgtest.V6tBlg/build.2CL/real-tree/tests/update.TestCase",
line 949, in test_procesk
self.assertTrue(os.path.isfile(icon_path))
AssertionError: False is not true
It is already fixed upstream[2].
The attached patch contains the fix.
Thank you for considering the patch.
[1]
https://autopkgtest.ubuntu.com/results/autopkgtest-mantic/mantic/amd64/f/fdroidserver/20230707_143232_ec734@/log.gz
[2]
https://github.com/f-droid/fdroidserver/commit/132e953c8c9f7d709586442aee6ff474cfa8fa18
Description: do not use deprecated Image.ANTIALIAS attribute
The ANTIALIAS alias was removed in Pillow 10.0.0:
https://pillow.readthedocs.io/en/stable/deprecations.html
Author: Hans-Christoph Steiner
Origin: upstream
Bug: https://github.com/f-droid/fdroidserver/commit/132e953c8c9f7d709586442aee6ff474cfa8fa18
Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040629
Last-Update: 2023-07-19
--- a/fdroidserver/update.py
+++ b/fdroidserver/update.py
@@ -250,7 +250,7 @@
if any(length > size for length in im.size):
oldsize = im.size
-im.thumbnail((size, size), Image.ANTIALIAS)
+im.thumbnail((size, size), Image.Resampling.LANCZOS)
logging.debug("%s was too large at %s - new size is %s" % (
iconpath, oldsize, im.size))
im.save(iconpath, "PNG", optimize=True,
@@ -1757,7 +1757,7 @@
size = dpi_to_px(density)
-im.thumbnail((size, size), Image.ANTIALIAS)
+im.thumbnail((size, size), Image.Resampling.LANCZOS)
im.save(icon_path, "PNG", optimize=True,
pnginfo=BLANK_PNG_INFO, icc_profile=None)
empty_densities.remove(density)
Bug#1041447: comitup: fails to install, remove, distupgrade, and install again
Package: comitup Version: 1.38-1.1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install (in 'bullseye'), remove (but not purge), distupgrade to 'bookworm', and install again. Before the second installation the package is in config-files-remaining state. The configuration is remaining from the last version that was successfully configured - which is from the previous release. Like a plain failure on initial install this makes the package too buggy for a release, thus the severity. From the attached log (scroll to the bottom...): ... Setting up comitup (1.15-1) ... comitup-no-wifi - No wifi devices found Comitup is a wifi device manager. 'sudo iw list' indicates that there are no devices to manage. Created symlink /etc/systemd/system/multi-user.target.wants/comitup.service → /lib/systemd/system/comitup.service. ... Removing comitup (1.15-1) ... ... Setting up comitup (1.38-1.1) ... Installing new version of config file /etc/comitup.conf ... [ESC][0;1;31mFailed to enable unit, unit /etc/systemd/system/comitup.service is masked.[ESC][0m dpkg: error processing package comitup (--configure): installed comitup package post-installation script subprocess returned error exit status 1 Processing triggers for dbus (1.14.8-2~deb12u1) ... Errors were encountered while processing: comitup ... cheers, Andreas comitup_1.38-1.1.log.gz Description: application/gzip
Processed: your mail
Processing commands for cont...@bugs.debian.org: > found 1041242 1.16.2-2 Bug #1041242 [libheif1] libheif1: 1.16.2-1+b1 breaks displaying any pictures Marked as found in versions libheif/1.16.2-2. > End of message, stopping processing here. Please contact me if you need assistance. -- 1041242: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041242 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1037864: marked as done (spek: ftbfs with GCC-13)
Your message dated Tue, 18 Jul 2023 22:52:43 + with message-id and subject line Bug#1037864: fixed in spek 0.8.5+dfsg-3 has caused the Debian Bug report #1037864, regarding spek: ftbfs with GCC-13 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1037864: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037864 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:spek Version: 0.8.5+dfsg-2 Severity: normal Tags: sid trixie User: debian-...@lists.debian.org Usertags: ftbfs-gcc-13 [This bug is targeted to the upcoming trixie release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-13/g++-13, but succeeds to build with gcc-12/g++-12. The severity of this report will be raised before the trixie release. The full build log can be found at: http://qa-logs.debian.net/2023/05/22/logs/spek_0.8.5+dfsg-2_unstable_gccexp.log The last lines of the build log are at the end of this report. To build with GCC 13, either set CC=gcc-13 CXX=g++-13 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-13/porting_to.html [...] make[4]: Leaving directory '/<>/data/icons/24x24' Making check in 32x32 make[4]: Entering directory '/<>/data/icons/32x32' make[4]: Nothing to be done for 'check'. make[4]: Leaving directory '/<>/data/icons/32x32' Making check in 48x48 make[4]: Entering directory '/<>/data/icons/48x48' make[4]: Nothing to be done for 'check'. make[4]: Leaving directory '/<>/data/icons/48x48' Making check in scalable make[4]: Entering directory '/<>/data/icons/scalable' make[4]: Nothing to be done for 'check'. make[4]: Leaving directory '/<>/data/icons/scalable' make[4]: Entering directory '/<>/data/icons' make[4]: Nothing to be done for 'check-am'. make[4]: Leaving directory '/<>/data/icons' make[3]: Leaving directory '/<>/data/icons' make[3]: Entering directory '/<>/data' /usr/bin/msgfmt --desktop --template spek.desktop.in -d ../po -o spek.desktop make[3]: Leaving directory '/<>/data' make[2]: Leaving directory '/<>/data' Making check in man make[2]: Entering directory '/<>/man' make[2]: Nothing to be done for 'check'. make[2]: Leaving directory '/<>/man' Making check in po make[2]: Entering directory '/<>/po' make[2]: Nothing to be done for 'check'. make[2]: Leaving directory '/<>/po' Making check in src make[2]: Entering directory '/<>/src' make[2]: Nothing to be done for 'check'. make[2]: Leaving directory '/<>/src' Making check in tests make[2]: Entering directory '/<>/tests' make test perf make[3]: Entering directory '/<>/tests' g++ -DHAVE_CONFIG_H -I. -I.. -include config.h -I../src -DSAMPLES_DIR=\"./samples\" -pthread -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/x86_64-linux-gnu -I/usr/include/x86_64-linux-gnu -I/usr/include/x86_64-linux-gnu -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -std=gnu++11 -Wall -Wextra -c -o test-audio.o test-audio.cc g++ -DHAVE_CONFIG_H -I. -I.. -include config.h -I../src -DSAMPLES_DIR=\"./samples\" -pthread -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/x86_64-linux-gnu -I/usr/include/x86_64-linux-gnu -I/usr/include/x86_64-linux-gnu -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -std=gnu++11 -Wall -Wextra -c -o test-fft.o test-fft.cc g++ -DHAVE_CONFIG_H -I. -I.. -include config.h -I../src -DSAMPLES_DIR=\"./samples\" -pthread -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/x86_64-linux-gnu -I/usr/include/x86_64-linux-gnu -I/usr/include/x86_64-linux-gnu -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -std=gnu++11 -Wall -Wextra -c -o test-utils.o test-utils.cc g++ -DHAVE_CONFIG_H -I. -I.. -include config.h -I../src -DSAMPLES_DIR=\"./samples\" -pthread -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/x86_64-linux-gnu -I/usr/include/x86_64-linux-gnu -I/usr/include/x86_64-linux-gnu -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -std=gnu++11 -Wall -Wext
Bug#1041443: pyfai_2023.5.0+dfsg1-3_all-buildd.changes REJECTED
Source: pyfai Version: 2023.5.0+dfsg1-3 Severity: serious On 2023-07-18 11:09, Debian FTP Masters wrote: > pyfai_2023.5.0+dfsg1-3_all.deb: has 1 file(s) with a timestamp too far in the= > past: > usr/share/doc/pyfai/changelog.gz (Thu Jan 1 00:00:00 1970) > > > > =3D=3D=3D > > Please feel free to respond to this email if you don't understand why > your files were rejected, or if you upload new files which address our > concerns. > > >
Bug#1041442: python-fabio_2023.6.0-1_ppc64el-buildd.changes REJECTED
Source: python-fabio Version: 2023.6.0-1 Severity: serious On 2023-07-18 19:24, Debian FTP Masters wrote: > python3-fabio_2023.6.0-1_ppc64el.deb: has 1 file(s) with a timestamp too far = > in the past: > usr/share/doc/python3-fabio/changelog.gz (Thu Jan 1 00:00:00 1970) > > > > =3D=3D=3D > > Please feel free to respond to this email if you don't understand why > your files were rejected, or if you upload new files which address our > concerns. > > >
Bug#1037656: marked as done (filtergen: ftbfs with GCC-13)
Your message dated Tue, 18 Jul 2023 22:34:21 + with message-id and subject line Bug#1037656: fixed in filtergen 0.12.8-3 has caused the Debian Bug report #1037656, regarding filtergen: ftbfs with GCC-13 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1037656: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037656 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:filtergen Version: 0.12.8-1 Severity: normal Tags: sid trixie User: debian-...@lists.debian.org Usertags: ftbfs-gcc-13 [This bug is targeted to the upcoming trixie release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-13/g++-13, but succeeds to build with gcc-12/g++-12. The severity of this report will be raised before the trixie release. The full build log can be found at: http://qa-logs.debian.net/2023/05/22/logs/filtergen_0.12.8-1_unstable_gccexp.log The last lines of the build log are at the end of this report. To build with GCC 13, either set CC=gcc-13 CXX=g++-13 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-13/porting_to.html [...] checking for stdio.h... yes checking for stdlib.h... yes checking for string.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for strings.h... yes checking for sys/stat.h... yes checking for sys/types.h... yes checking for unistd.h... yes checking for getopt.h... yes checking for getopt in -lgetopt... no checking whether to enable profiler... no checking whether to enable debugging compiler options... no checking that generated files are newer than configure... done configure: creating ./config.status config.status: creating Makefile config.status: creating t/Makefile config.status: creating filtergen.spec config.status: creating fgadm config.status: creating fgadm.conf config.status: creating rules.filter config.status: creating config.h config.status: executing depfiles commands filtergen 0.12.8: automatic configuration OK. Type 'make' to compile filtergen. Type 'make install' to install filtergen. make[1]: Leaving directory '/<>' dh_auto_build dh_auto_build: warning: Compatibility levels before 10 are deprecated (level 9 in use) make -j1 make[1]: Entering directory '/<>' make all-recursive make[2]: Entering directory '/<>' Making all in . make[3]: Entering directory '/<>' gcc -DHAVE_CONFIG_H -I. -Wdate-time -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -pedantic -W -Wall -Werror -Waggregate-return -Wcast-align -Wcast-qual -Wnested-externs -Wshadow -Wbad-function-cast -Wwrite-strings -Winit-self -Wformat=2 -Wuninitialized -Wpointer-arith -Wstrict-aliasing -fstrict-aliasing -c -o filtergen.o filtergen.c filtergen.c: In function ‘main’: filtergen.c:239:5: error: pointer ‘ftn’ may be used after ‘free’ [-Werror=use-after-free] 239 | fprintf(stderr, "%s: target filter unrecognised: %s\n", progname, ftn); | ^~ filtergen.c:237:3: note: call to ‘free’ here 237 | free(ftn); | ^ In file included from /usr/include/stdio.h:906, from filtergen.c:25: In function ‘fprintf’, inlined from ‘main’ at filtergen.c:239:5: /usr/include/x86_64-linux-gnu/bits/stdio2.h:79:10: error: pointer ‘ftn’ may be used after ‘free’ [-Werror=use-after-free] 79 | return __fprintf_chk (__stream, __USE_FORTIFY_LEVEL - 1, __fmt, | ^~~~ 80 | __va_arg_pack ()); | ~ filtergen.c: In function ‘main’: filtergen.c:237:3: note: call to ‘free’ here 237 | free(ftn); | ^ cc1: all warnings being treated as errors make[3]: *** [Makefile:604: filtergen.o] Error 1 make[3]: Leaving directory '/<>' make[2]: *** [Makefile:818: all-recursive] Error 1 make[2]: Leaving directory '/<>' make[1]: ***
Bug#1041259: marked as done (freedv: FTBFS: lpcnet_freedv.h: No such file or directory)
Your message dated Tue, 18 Jul 2023 22:04:39 + with message-id and subject line Bug#1041259: fixed in codec2 1.1.1-6 has caused the Debian Bug report #1041259, regarding freedv: FTBFS: lpcnet_freedv.h: 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.) -- 1041259: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041259 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: freedv Version: 1.8.11-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) https://buildd.debian.org/status/fetch.php?pkg=freedv&arch=amd64&ver=1.8.11-1%2Bb2&stamp=1689518012&raw=0 [ 95%] Building CXX object src/CMakeFiles/freedv.dir/ongui.cpp.o cd /<>/Build/src && /usr/bin/c++ -DAUDIO_ENGINE_PULSEAUDIO_ENABLE -DGIT_HASH=\"None\" -DWXUSINGDLL -D_FILE_OFFSET_BITS=64 -D__WXGTK__ -I/<>/src -I/<>/Build/src -I/<>/Build -isystem /usr/lib/x86_64-linux-gnu/wx/include/gtk3-unicode-3.2 -isystem /usr/include/wx-3.2 -isystem /usr/include/codec2 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -pthread -O2 -g -DNDEBUG -std=c++14 -MD -MT src/CMakeFiles/freedv.dir/ongui.cpp.o -MF CMakeFiles/freedv.dir/ongui.cpp.o.d -o CMakeFiles/freedv.dir/ongui.cpp.o -c /<>/src/ongui.cpp /<>/src/ongui.cpp:8:10: fatal error: lpcnet_freedv.h: No such file or directory 8 | #include "lpcnet_freedv.h" | ^ compilation terminated. make[3]: *** [src/CMakeFiles/freedv.dir/build.make:345: src/CMakeFiles/freedv.dir/ongui.cpp.o] Error 1 Cheers -- Sebastian Ramacher --- End Message --- --- Begin Message --- Source: codec2 Source-Version: 1.1.1-6 Done: A. Maitland Bottoms We believe that the bug you reported is fixed in the latest version of codec2, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1041...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. A. Maitland Bottoms (supplier of updated codec2 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: Tue, 18 Jul 2023 16:01:14 -0400 Source: codec2 Architecture: source Version: 1.1.1-6 Distribution: unstable Urgency: medium Maintainer: A. Maitland Bottoms Changed-By: A. Maitland Bottoms Closes: 1041259 Changes: codec2 (1.1.1-6) unstable; urgency=medium . * install lpcnet_freedv.h header (Closes: #1041259) Checksums-Sha1: a62032ecb1151b3152ad5cc029e3d266924e4898 2953 codec2_1.1.1-6.dsc d0cc7ffaec55c34575f3a011cd1b085973d11833 48256 codec2_1.1.1-6.debian.tar.xz 10edd701c7c3478ac008de4f194bb288a3716f1a 18048 codec2_1.1.1-6_amd64.buildinfo Checksums-Sha256: 5eb78a824bdf5a0e28a09b6c9c105eb3d56eca2e9892ac4f6c1d1d761952c3b8 2953 codec2_1.1.1-6.dsc 32699fcffe8185c431ba547422094c7fdc76b0ac3325716946fd8c37d000f24d 48256 codec2_1.1.1-6.debian.tar.xz 0255a2db56a4d9e5195b032f392032a09d024bf6349e7b32803dc3919b4390f9 18048 codec2_1.1.1-6_amd64.buildinfo Files: abfad9dbb796418b82bbb31cb2d64103 2953 sound optional codec2_1.1.1-6.dsc 8551520162a2d8ab7b0fc231791f79eb 48256 sound optional codec2_1.1.1-6.debian.tar.xz 2ee711c1d6c29a0b3494bbe3f1318ee1 18048 sound optional codec2_1.1.1-6_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEB8qH3cTCsGJAtrF0UEHxiR9E4JAFAmS3A+IACgkQUEHxiR9E 4JCo1hAAoU1axtn1g7f7A5dI62oinOPhy3CtFS96b+Tamd+ko5pbPspaGNeUsRXw MOUr/U+2kiQB9ob6jvygZUHjx96DErGOabQCghiBRjsfHgeRXlvuGRmpecVKMBAP sqq78VO4Kr/ixAbnwfwzC+fWdD8avMjbbC1sAjB4wlXxAvRAH4jjS+ZPxvv0IbEE cNE7tX8q7oI1FN0fB/7KDklko8HGtsfp0hIR8UdIwYKP7g+AKbDe93/48pvbngEP DXj/T0XhrO2c6G7ugp0BJOFZ5gWurOBHV0zxLPcaWlKIXk72vrG+8+MJE6oI9CBj 7TVjl/6Eouktp/UMJWRnlbNLCRf/yxjLckfZi2VvWmXMXUEwf1Ifl5rpSJHCeqUW K+oXEnJFcK+66yGibcRB5DFHsfZy3x9TqylUp3ugLJ0YTcQwx/0ZgzHR88fDzivX mm29S7F45Tz+PfFz7KqPdheRNwyfTOiivqR++geZfg+bRM9e5LiRzu3hWYx4K/Zy 6DSKhSzCQr3pw+cGi892PvON2RBs2PkeViJDcuxJgeNJuxCTS2MBZy74vEwrcOvE 7Km3DZ5U/RmYfmzpUWJX7cwL6X86A51Fd9L+ZkqcUfNKkVmfJYMG6Ud2qJ4H9hbu 0SeUsuts3Ftc0Zo/3gLM3dx1/WynVHamx6e4ybW+dJrEl3X4Dn8= =QPMK -END PGP SIGNATURE End Message ---
Bug#1041225: marked as done (FTBFS against suitesparse 7)
Your message dated Tue, 18 Jul 2023 21:09:53 + with message-id and subject line Bug#1041225: fixed in siconos 4.4.0+dfsg-3 has caused the Debian Bug report #1041225, regarding FTBFS against suitesparse 7 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.) -- 1041225: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041225 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: siconos Version: 4.4.0+dfsg-2 Severity: important Tags: ftbfs sid trixie patch User: sebast...@debian.org Usertags: suitesparse7 Dear Maintainer, siconos fails to build against suitesparse 7, which is currently available in experimental. A patch is attached. Cheers, -- ⢀⣴⠾⠻⢶⣦⠀ Sébastien Villemot ⣾⠁⢠⠒⠀⣿⡁ Debian Developer ⢿⡄⠘⠷⠚⠋⠀ https://sebastien.villemot.name ⠈⠳⣄ https://www.debian.org Description: Fix FTBFS against suitesparse 7 In SuiteSparse 7.1.0, CXSparse now unconditionally enables the complex number support. In particular, cs.h now unconditonally includes . But "I" is a preprocessor macro when is included, and this conflicts with names used inside siconos and boost. So undefine that macro. Author: Sébastien Villemot Bug-Debian: https://bugs.debian.org/ Forwarded: no Last-Update: 2023-07-15 --- This patch header follows DEP-3: http://dep.debian.net/deps/dep3/ --- a/numerics/src/tools/CSparseMatrix_internal.h +++ b/numerics/src/tools/CSparseMatrix_internal.h @@ -45,6 +45,7 @@ #define NCOMPLEX #include "cs.h" +#undef I #include "CSparseMatrix.h" --- End Message --- --- Begin Message --- Source: siconos Source-Version: 4.4.0+dfsg-3 Done: Sébastien Villemot We believe that the bug you reported is fixed in the latest version of siconos, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1041...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sébastien Villemot (supplier of updated siconos 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, 18 Jul 2023 21:57:03 +0200 Source: siconos Architecture: source Version: 4.4.0+dfsg-3 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Sébastien Villemot Closes: 1041225 Changes: siconos (4.4.0+dfsg-3) unstable; urgency=medium . * Team upload. * suitesparse7.patch: new patch, fixes FTBFS against suitesparse 7. (Closes: #1041225) Checksums-Sha1: e960d8ff369262b341ee700324b3c7fb0a0e4b44 3591 siconos_4.4.0+dfsg-3.dsc f4da2ec3f7972e677074633f8bc5183cf44355d2 36424 siconos_4.4.0+dfsg-3.debian.tar.xz 3c377057c0b78947ac457267132a981d2c2ca68e 24195 siconos_4.4.0+dfsg-3_amd64.buildinfo Checksums-Sha256: 3b8b0ddd8d271cf18175341435124cb817d4c7ac8c0eba7aef12f3dfcc2b8932 3591 siconos_4.4.0+dfsg-3.dsc b0fc819d82ed473354d594adec77fa55d89b03f6155b5bba47bb139f62143d7a 36424 siconos_4.4.0+dfsg-3.debian.tar.xz dc3cf161b7acfc4fc056037ce591e85330d63beb391bbe9aa72d95db04d586ff 24195 siconos_4.4.0+dfsg-3_amd64.buildinfo Files: 05f2045d438c5dfb55b66ea2077d2d0b 3591 science optional siconos_4.4.0+dfsg-3.dsc d97bb273d5cf59084cc78d92eb7690f4 36424 science optional siconos_4.4.0+dfsg-3.debian.tar.xz 61222ee5be3c6f4b2fe2a7f66efe9b50 24195 science optional siconos_4.4.0+dfsg-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEU5UdlScuDFuCvoxKLOzpNQ7OvkoFAmS2+BYACgkQLOzpNQ7O vkrlYw/+P+qpBn5CUw9JpmBWJSC3iDzo3Gn2PDcEyhSBEYQYWX7M3IwSDzygiqPP F7bxWuLK4+mtgreOqKu+0Ydf5q1+RMHF1AmeTJDLGcFCMc21+NRC05hi25Ixftqg Xj9LnUGQtDcwsfMtav12uTmNbfTiyY+tjaaOk9EGjR0psj+7dPpRrqB019Z3En7L K3T/dV63oPRKLY0zCm9fnuhRUj+5n2p/wetNK2tW8v0bQRWfsvx5dQ8U9L5KH8xh zikhOzEjazciNs/3fGe+yutfcVagqRq/Bvu2noaWtnaqGAm6CKSTJptSReC1qqZM mo5zjNiRXPMopzKk3mwqP5lkG3HVmgJ/I+iclZ6mwkGyoNJDMVTV3oP26RboHiCL rrMvw6PEXN61AY7kjUeemMLtAZ866oHhsOyVZGjUII5cvfFB9HbpMMVe1qTBLVGs bFb7msnVuz/9FJT7vzzyisEu3Qve/xpVBuo4Ru4J89RP0elh0cSwgMX1N8LbBKMA Lfg9h34vXHlkiXHedFunrkwYPmLudMXtReyZYTf1HvAk18mIPnokJCdV/2DUfqd3 jcgXzggJMd6cLXR3s4dV81zNIL5wsHjTWCLX7HRcW/BHnJnuzVcSsbjTttjCUwJr u7aQSTvtESHQm8g6L8Fjb0zSs0smOvEpsr5ydi0lxLpP2/8dDn0= =yg6X -END PGP SIGNATURE End Message ---
Bug#1037769: marked as done (mangohud: ftbfs with GCC-13)
Your message dated Tue, 18 Jul 2023 21:08:34 + with message-id and subject line Bug#1037769: fixed in mangohud 0.6.9.1-1 has caused the Debian Bug report #1037769, regarding mangohud: ftbfs with GCC-13 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1037769: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037769 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:mangohud Version: 0.6.8-2 Severity: normal Tags: sid trixie User: debian-...@lists.debian.org Usertags: ftbfs-gcc-13 [This bug is targeted to the upcoming trixie release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-13/g++-13, but succeeds to build with gcc-12/g++-12. The severity of this report will be raised before the trixie release. The full build log can be found at: http://qa-logs.debian.net/2023/05/22/logs/mangohud_0.6.8-2_unstable_gccexp.log The last lines of the build log are at the end of this report. To build with GCC 13, either set CC=gcc-13 CXX=g++-13 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-13/porting_to.html [...] Build targets in project: 10 MangoHud v0.6.8 Subprojects imgui: YES User defined options buildtype: plain libdir : lib/x86_64-linux-gnu localstatedir: /var prefix : /usr sysconfdir : /etc wrap_mode: nodownload mangoapp : true mangoapp_layer : true mangohudctl : true use_system_spdlog: enabled use_system_vulkan: enabled with_nvml: disabled with_wayland : enabled with_xnvctrl : enabled Found ninja-1.11.1 at /usr/bin/ninja make[1]: Leaving directory '/<>' dh_auto_build cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 ninja -j8 -v [1/100] /usr/bin/meson --internal vcstagger ../version.h.in version.h v0.6.8 /<> @VCS_TAG@ '(.*)' git describe --tags --dirty=+ [2/100] /usr/bin/python3 ../bin/gen_enum_to_str.py --xml /usr/share/vulkan/registry/vk.xml --outdir /<>/obj-x86_64-linux-gnu [3/100] c++ -Isubprojects/imgui-1.81/libimgui.a.p -Isubprojects/imgui-1.81 -I../subprojects/imgui-1.81 -I../subprojects/imgui-1.81/backends -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -std=c++14 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -MD -MQ subprojects/imgui-1.81/libimgui.a.p/backends_imgui_impl_glfw.cpp.o -MF subprojects/imgui-1.81/libimgui.a.p/backends_imgui_impl_glfw.cpp.o.d -o subprojects/imgui-1.81/libimgui.a.p/backends_imgui_impl_glfw.cpp.o -c ../subprojects/imgui-1.81/backends/imgui_impl_glfw.cpp [4/100] /usr/bin/glslangValidator -V -x -o src/overlay.frag.spv.h ../src/overlay.frag ../src/overlay.frag [5/100] c++ -Isubprojects/imgui-1.81/libimgui.a.p -Isubprojects/imgui-1.81 -I../subprojects/imgui-1.81 -I../subprojects/imgui-1.81/backends -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -std=c++14 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -MD -MQ subprojects/imgui-1.81/libimgui.a.p/backends_imgui_impl_opengl3.cpp.o -MF subprojects/imgui-1.81/libimgui.a.p/backends_imgui_impl_opengl3.cpp.o.d -o subprojects/imgui-1.81/libimgui.a.p/backends_imgui_impl_opengl3.cpp.o -c ../subprojects/imgui-1.81/backends/imgui_impl_opengl3.cpp [6/100] c++ -Isrc/libMangoHud_dlsym.so.p -Isrc -I../src -I../include -fvisibility=hidden -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -std=c++14 -Werror=return-type -Wno-unused-parameter -fno-math-errno -fno-trapping-math -Wno-non-virtual-dtor -Wno-missing-field-initializers -Wno-format-truncation -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS '-DPACKAGE_VERSION="v0.6.8"' -DS
Bug#1041432: box64: unsatisfiable dependencies
On Tue, Jul 18, 2023 at 4:55 PM Johannes Schauer Marin Rodrigues wrote: > $ apt-cache show crossbuild-essential-mips64el | grep Depends: > Depends: gcc-mips64el-linux-gnuabi64 (>= 4:10.2) | gcc:mips64el, > g++-mips64el-linux-gnuabi64 (>= 4:10.2) | g++:mips64el, dpkg-cross > > But other packages use the same thing. Why does it work there? I guess you should ask the Release Team for help. I don't know. Thank you, Jeremy Bícha
Bug#1041432: box64: unsatisfiable dependencies
Quoting Jeremy Bícha (2023-07-18 22:29:58) > On Tue, Jul 18, 2023 at 4:23 PM Johannes Schauer Marin Rodrigues > wrote: > > Quoting Jeremy Bícha (2023-07-18 21:20:21) > > > https://tracker.debian.org/pkg/box64 says that box64 is unable to migrate > > > into Testing because it has unsatisfiable dependencies on amd64, arm64, > > > ppc64el (and I guess riscv64) > > > > I saw that but it doesn't say which one is unsatisfiable. Do you have an > > idea > > about what is going on? > > I am guessing that britney (or whatever is checking) is not familiar > with the :amd64 syntax even on amd64. $ apt-cache show crossbuild-essential-mips64el | grep Depends: Depends: gcc-mips64el-linux-gnuabi64 (>= 4:10.2) | gcc:mips64el, g++-mips64el-linux-gnuabi64 (>= 4:10.2) | g++:mips64el, dpkg-cross But other packages use the same thing. Why does it work there? signature.asc Description: signature
Bug#1037885: marked as done (vkbasalt: ftbfs with GCC-13)
Your message dated Tue, 18 Jul 2023 20:46:25 +
with message-id
and subject line Bug#1037885: fixed in vkbasalt 0.3.2.10-1
has caused the Debian Bug report #1037885,
regarding vkbasalt: ftbfs with GCC-13
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1037885: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037885
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:vkbasalt
Version: 0.3.2.9-1
Severity: normal
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-13
[This bug is targeted to the upcoming trixie release]
Please keep this issue open in the bug tracker for the package it
was filed for. If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.
The package fails to build in a test rebuild on at least amd64 with
gcc-13/g++-13, but succeeds to build with gcc-12/g++-12. The
severity of this report will be raised before the trixie release.
The full build log can be found at:
http://qa-logs.debian.net/2023/05/22/logs/vkbasalt_0.3.2.9-1_unstable_gccexp.log
The last lines of the build log are at the end of this report.
To build with GCC 13, either set CC=gcc-13 CXX=g++-13 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.
apt-get -t=experimental install g++
Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-13/porting_to.html
[...]
../src/reshade/effect_codegen_spirv.cpp:1682:64: note: in definition of macro
‘IMPLEMENT_INTRINSIC_SPIRV’
1682 | #define IMPLEMENT_INTRINSIC_SPIRV(name, i, code) case name##i: code
|^~~~
../src/reshade/effect_symbol_table_intrinsics.inl:1728:30: error: ‘const
__gnu_cxx::__alloc_traits,
reshadefx::expression>::value_type’ {aka ‘const struct reshadefx::expression’}
has no member named ‘base’
1728 | .add(args[3].base)
| ^~~~
../src/reshade/effect_codegen_spirv.cpp:1682:64: note: in definition of macro
‘IMPLEMENT_INTRINSIC_SPIRV’
1682 | #define IMPLEMENT_INTRINSIC_SPIRV(name, i, code) case name##i: code
|^~~~
../src/reshade/effect_symbol_table_intrinsics.inl:1730:30: error: ‘const
__gnu_cxx::__alloc_traits,
reshadefx::expression>::value_type’ {aka ‘const struct reshadefx::expression’}
has no member named ‘base’
1730 | .add(args[2].base)
| ^~~~
../src/reshade/effect_codegen_spirv.cpp:1682:64: note: in definition of macro
‘IMPLEMENT_INTRINSIC_SPIRV’
1682 | #define IMPLEMENT_INTRINSIC_SPIRV(name, i, code) case name##i: code
|^~~~
../src/reshade/effect_codegen_spirv.cpp: In member function ‘virtual
reshadefx::codegen::id codegen_spirv::emit_construct(const
reshadefx::location&, const reshadefx::type&, const
std::vector&)’:
../src/reshade/effect_codegen_spirv.cpp:1692:102: error: ‘const struct
reshadefx::expression’ has no member named ‘base’
1692 | assert((arg.type.is_scalar() ||
type.is_array()) && arg.chain.empty() && arg.base != 0);
|
^~~~
../src/reshade/effect_codegen_spirv.cpp:1713:66: error: ‘const
__gnu_cxx::__alloc_traits,
reshadefx::expression>::value_type’ {aka ‘const struct reshadefx::expression’}
has no member named ‘base’
1713 | inst.add(args[arg + row].base);
| ^~~~
../src/reshade/effect_codegen_spirv.cpp:1726:51: error: ‘const struct
reshadefx::expression’ has no member named ‘base’
1726 | ids.push_back(arg.base);
| ^~~~
In file included from ../src/reshade/effect_codegen_spirv.cpp:7:
../src/reshade/effect_codegen.hpp: In instantiation of
‘reshadefx::codegen::find_struct(id):: [with auto:19 =
reshadefx::struct_info]’:
/usr/include/c++/13/bits/predefined_ops.h:318:23: required from ‘constexpr
bool __gnu_cxx::__ops::_Iter_pred<_Predicate>::operator()(_Iterator) [with
_Iterator = __gnu_cxx::__n
Processed: tagging 1041429, tagging 1041427, tagging 1041428 ..., tagging 1041430
Processing commands for cont...@bugs.debian.org: > tags 1041429 + upstream Bug #1041429 [src:restrictedpython] restrictedpython: CVE-2023-37271 Added tag(s) upstream. > tags 1041427 + upstream Bug #1041427 [src:bitcoin] bitcoin: CVE-2023-37192 Added tag(s) upstream. > tags 1041428 + upstream Bug #1041428 [src:sqlfluff] sqlfluff: CVE-2023-36830 Added tag(s) upstream. > forwarded 1041428 https://github.com/sqlfluff/sqlfluff/pull/4925 Bug #1041428 [src:sqlfluff] sqlfluff: CVE-2023-36830 Set Bug forwarded-to-address to 'https://github.com/sqlfluff/sqlfluff/pull/4925'. > tags 1041430 + upstream Bug #1041430 [src:ruby-sanitize] ruby-sanitize: CVE-2023-36823 Added tag(s) upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 1041427: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041427 1041428: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041428 1041429: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041429 1041430: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041430 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1040628: marked as done (dnstwist autopkg tests fail with pillow 10.0.0)
Your message dated Tue, 18 Jul 2023 20:36:20 +
with message-id
and subject line Bug#1040628: fixed in dnstwist 0~20230509-1
has caused the Debian Bug report #1040628,
regarding dnstwist autopkg tests fail with pillow 10.0.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.)
--
1040628: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040628
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:dnstwist
Version: 0~20221213-1
Severity: serious
Tags: sid trixie
see
https://ci.debian.net/data/autopkgtest/testing/amd64/d/dnstwist/35498772/log.gz
61s autopkgtest [17:23:09]: test testdebiandomain: [---
65s Traceback (most recent call last):
65s File "/usr/bin/dnstwist", line 33, in
65s sys.exit(load_entry_point('dnstwist==20221213', 'console_scripts',
'dnstwist')())
65s
^^^
65s File "/usr/lib/python3/dist-packages/dnstwist.py", line 933, in wrapper
65s result = func(*args, **kwargs)
65s ^
65s File "/usr/lib/python3/dist-packages/dnstwist.py", line 1190, in run
65s phash = pHash(BytesIO(screenshot))
65s ^^
65s File "/usr/lib/python3/dist-packages/dnstwist.py", line 298, in __init__
65s img = Image.open(image).convert('L').resize((hsize, hsize),
Image.ANTIALIAS)
65s
^^^
65s AttributeError: module 'PIL.Image' has no attribute 'ANTIALIAS'
65s dnstwist execution failed
66s autopkgtest [17:23:14]: test testdebiandomain: ---]
66s testdebiandomain FAIL non-zero exit status 1
66s autopkgtest [17:23:14]: test testdebiandomain: - - - - - - - - - -
results - - - - - - - - - -
66s autopkgtest [17:23:14]: test testdebiandomain: - - - - - - - - - - stderr
- - - - - - - - - -
66s Traceback (most recent call last):
66s File "/usr/bin/dnstwist", line 33, in
66s sys.exit(load_entry_point('dnstwist==20221213', 'console_scripts',
'dnstwist')())
66s
^^^
66s File "/usr/lib/python3/dist-packages/dnstwist.py", line 933, in wrapper
66s result = func(*args, **kwargs)
66s ^
66s File "/usr/lib/python3/dist-packages/dnstwist.py", line 1190, in run
66s phash = pHash(BytesIO(screenshot))
66s ^^
66s File "/usr/lib/python3/dist-packages/dnstwist.py", line 298, in __init__
66s img = Image.open(image).convert('L').resize((hsize, hsize),
Image.ANTIALIAS)
66s
^^^
66s AttributeError: module 'PIL.Image' has no attribute 'ANTIALIAS'
66s dnstwist execution failed
--- End Message ---
--- Begin Message ---
Source: dnstwist
Source-Version: 0~20230509-1
Done: Peter Wienemann
We believe that the bug you reported is fixed in the latest version of
dnstwist, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1040...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Peter Wienemann (supplier of updated dnstwist 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, 18 Jul 2023 20:28:38 +0200
Source: dnstwist
Architecture: source
Version: 0~20230509-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Security Tools
Changed-By: Peter Wienemann
Closes: 1040628
Changes:
dnstwist (0~20230509-1) unstable; urgency=medium
.
* New upstream version 0~20230509
* Update patch patch-out-embedded-jquery-cdn
* Add patch to adapt to changes in pillow 10.0.0
(Closes: #1040628, LP: #2027963)
* Add python3-tlsh as recommended dependency
* Use TLSH instead of ssdeep as hash in autopkgtest.
Adjust test dependencies accordingly.
* Update copyright years for upstream code and Debian packaging
Checksums-Sha1:
bbd5e4fce855fbac460225cfd12f3449ec10b94e 2344 dnstwist_0~20230509-1.dsc
48bb954e1b89fca0ed7ca997fb1fc6881d01602e 407028 dnstwist_0~20230509.orig.tar.xz
ee8df754667caa7fbef89a3f0e3b3a76178223fc 6212
dnstwist_0~20230509-1.debian.tar.xz
b467fb66b9e44f10268d2908278231d2a159ed26 6913
d
Processed: tagging 1041423, found 1041423 in 0.6.2.1-1
Processing commands for cont...@bugs.debian.org: > tags 1041423 + upstream Bug #1041423 [src:cjose] cjose: CVE-2023-37464 Added tag(s) upstream. > found 1041423 0.6.2.1-1 Bug #1041423 [src:cjose] cjose: CVE-2023-37464 Marked as found in versions cjose/0.6.2.1-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1041423: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041423 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1041432: box64: unsatisfiable dependencies
On Tue, Jul 18, 2023 at 4:23 PM Johannes Schauer Marin Rodrigues wrote: > Quoting Jeremy Bícha (2023-07-18 21:20:21) > > https://tracker.debian.org/pkg/box64 says that box64 is unable to migrate > > into Testing because it has unsatisfiable dependencies on amd64, arm64, > > ppc64el (and I guess riscv64) > > I saw that but it doesn't say which one is unsatisfiable. Do you have an idea > about what is going on? I am guessing that britney (or whatever is checking) is not familiar with the :amd64 syntax even on amd64. Thank you, Jeremy Bícha
Bug#1041432: box64: unsatisfiable dependencies
Hi, Quoting Jeremy Bícha (2023-07-18 21:20:21) > https://tracker.debian.org/pkg/box64 says that box64 is unable to migrate > into Testing because it has unsatisfiable dependencies on amd64, arm64, > ppc64el (and I guess riscv64) I saw that but it doesn't say which one is unsatisfiable. Do you have an idea about what is going on? Thanks! cheers, josch signature.asc Description: signature
Processed: retitle 1040830 to iperf3: CVE-2023-38403: ESNET-SECADV-2023-0001: iperf3 memory allocation hazard and crash ...
Processing commands for cont...@bugs.debian.org:
> retitle 1040830 iperf3: CVE-2023-38403: ESNET-SECADV-2023-0001: iperf3 memory
> allocation hazard and crash
Bug #1040830 {Done: Roberto Lumbreras } [src:iperf3]
ESNET-SECADV-2023-0001: iperf3 memory allocation hazard and crash
Changed Bug title to 'iperf3: CVE-2023-38403: ESNET-SECADV-2023-0001: iperf3
memory allocation hazard and crash' from 'ESNET-SECADV-2023-0001: iperf3 memory
allocation hazard and crash'.
> found 1040830 3.9-1
Bug #1040830 {Done: Roberto Lumbreras } [src:iperf3] iperf3:
CVE-2023-38403: ESNET-SECADV-2023-0001: iperf3 memory allocation hazard and
crash
Ignoring request to alter found versions of bug #1040830 to the same values
previously set
> fixed 1040830 3.9-1+deb11u1
Bug #1040830 {Done: Roberto Lumbreras } [src:iperf3] iperf3:
CVE-2023-38403: ESNET-SECADV-2023-0001: iperf3 memory allocation hazard and
crash
Marked as fixed in versions iperf3/3.9-1+deb11u1.
> fixed 1040830 3.12-1+deb12u1
Bug #1040830 {Done: Roberto Lumbreras } [src:iperf3] iperf3:
CVE-2023-38403: ESNET-SECADV-2023-0001: iperf3 memory allocation hazard and
crash
Marked as fixed in versions iperf3/3.12-1+deb12u1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1040830: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040830
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1041437: [debian bookworm] [kernel 6.1.0-9-rt-armmp] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b
Package:linux-image-6.1.0-9-rt-armm Version: 6.1.0-9-rt-armmp Severity: serious Dear developer, On Debian bookworm, target nanopir1, please find following issue [ 3991.659348] secondary_start_kernel from 0x40301ec0 [ 3991.659348] secondary_start_kernel from 0x40301ec0 [ 3991.659348] secondary_start_kernel from 0x40301ec0 [ 3991.878735] Kernel panic - not syncing: Attempted to kill init! exitcode=0x000b [ 3991.878763] CPU: 3 PID: 1 Comm: systemd Tainted: G C L 6.1.0-9-rt-armmp #1 Debian 6.1.27-1 [ 3991.878777] Hardware name: Allwinner sun8i Family [ 3991.878796] unwind_backtrace from show_stack+0x18/0x1c [ 3991.878839] show_stack from dump_stack_lvl+0x40/0x4c [ 3991.878867] dump_stack_lvl from panic+0x114/0x37c [ 3991.878892] panic from make_task_dead+0x0/0x184 [ 3992.631427] CPU1: stopping [ 3992.631448] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G C L 6.1.0-9-rt-armmp #1 Debian 6.1.27-1 [ 3992.631462] Hardware name: Allwinner sun8i Family [ 3992.631474] unwind_backtrace from show_stack+0x18/0x1c [ 3992.631504] show_stack from dump_stack_lvl+0x40/0x4c [ 3992.631527] dump_stack_lvl from do_handle_IPI+0x36c/0x3d8 [ 3992.631552] do_handle_IPI from ipi_handler+0x20/0x28 [ 3992.631573] ipi_handler from handle_percpu_devid_irq+0xac/0x278 [ 3992.631600] handle_percpu_devid_irq from generic_handle_domain_irq+0x30/0x40 [ 3992.631620] generic_handle_domain_irq from gic_handle_irq+0x90/0xb0 [ 3992.631639] gic_handle_irq from generic_handle_arch_irq+0x58/0x78 [ 3992.631659] generic_handle_arch_irq from call_with_stack+0x18/0x20 [ 3992.631688] call_with_stack from __irq_svc+0x98/0xdc [ 3992.631708] Exception stack(0xf0875f68 to 0xf0875fb0) [ 3992.631721] 5f60: 0001 c1064990 0067b901 c0321080 c158d340 0001 [ 3992.631732] 5f80: c140f89c c140f8fc 4020406a 410fc075 03126e98 f0875fb8 [ 3992.631740] 5fa0: c030a750 c030a754 60070013 [ 3992.631746] __irq_svc from arch_cpu_idle+0x40/0x44 [ 3992.631762] arch_cpu_idle from default_idle_call+0x48/0x8c [ 3992.631782] default_idle_call from do_idle+0xbc/0x12c [ 3992.631804] do_idle from cpu_startup_entry+0x20/0x24 [ 3992.631824] cpu_startup_entry from secondary_start_kernel+0x134/0x154 [ 3992.631847] secondary_start_kernel from 0x40301ec0 [ 3992.631921] CPU0: stopping [ 3992.631931] CPU: 0 PID: 0 Comm: swapper/0 Tainted: G C L 6.1.0-9-rt-armmp #1 Debian 6.1.27-1 [ 3992.631942] Hardware name: Allwinner sun8i Family [ 3992.631948] unwind_backtrace from show_stack+0x18/0x1c [ 3992.631969] show_stack from dump_stack_lvl+0x40/0x4c [ 3992.631989] dump_stack_lvl from do_handle_IPI+0x36c/0x3d8 [ 3992.632012] do_handle_IPI from ipi_handler+0x20/0x28 [ 3992.632034] ipi_handler from handle_percpu_devid_irq+0xac/0x278 [ 3992.632056] handle_percpu_devid_irq from generic_handle_domain_irq+0x30/0x40 [ 3992.632074] generic_handle_domain_irq from gic_handle_irq+0x90/0xb0 [ 3992.632090] gic_handle_irq from generic_handle_arch_irq+0x58/0x78 [ 3992.632110] generic_handle_arch_irq from __irq_svc+0x88/0xdc [ 3992.632128] Exception stack(0xc1401f10 to 0xc1401f58) [ 3992.632138] 1f00: c1064990 00999581 c0321080 [ 3992.632148] 1f20: c158d340 c140f89c c140f8fc c9fff9f7 [ 3992.632158] 1f40: 03126e98 c1401f60 c030a750 c030a754 60030013 [ 3992.632164] __irq_svc from arch_cpu_idle+0x40/0x44 [ 3992.632179] arch_cpu_idle from default_idle_call+0x48/0x8c [ 3992.632195] default_idle_call from do_idle+0xbc/0x12c [ 3992.632215] do_idle from cpu_startup_entry+0x20/0x24 [ 3992.632234] cpu_startup_entry from rest_init+0xd8/0xdc [ 3992.632257] rest_init from arch_post_acpi_subsys_init+0x0/0x18 [ 3992.632290] CPU2: stopping [ 3992.632299] CPU: 2 PID: 240 Comm: systemd-journal Tainted: G C L 6.1.0-9-rt-armmp #1 Debian 6.1.27-1 Best regards -- -- Jean-Marc LACROIX (06 82 29 98 66) -- -- mailto : jeanmarc.lacr...@free.fr --
Bug#1041436: [debian bookworm] brcmfmac mmc0:0001:1: firmware: failed to load brcm/brcmfmac43430-sdio.friendlyarm,nanopi-r1.bin (-2)
Source: firmware-brcm80211 Version: 20230515-3 Severity: grave Dear Debian team, I am trying to install firmware-brcm80211 on nanopir1 SBC running Debian 12, because this target contains one internal WIFI based on Broadcom 43430 chip. I have installed Debian kernel linux-image-rt-armmp from Debian. Because there is also one another bug on DTS in kernel to support Wifi chip, i have installed on this target Debian kernel from "trixie" release. With this release, DTS is more recent (!). I have also installed firmware-brcm80211 from "trixie," so that Debian firmwares are the most recent also. The current configuration is ... root@nanopi-r1:~# uname -a Linux nanopi-r1 6.3.0-1-rt-armmp #1 SMP PREEMPT_RT Debian 6.3.7-1 (2023-06-12) armv7l GNU/Linux root@nanopi-r1:~# dpkg -l |grep firmware ii firmware-brcm80211 20230515-3all Binary firmware for Broadcom/Cypress 802.11 wireless cards ii firmware-linux-free20200122-1all Binary firmware for various drivers in the Linux kernel root@nanopi-r1:~# dpkg -l |grep linux-image ii linux-image-6.3.0-1-rt-armmp 6.3.7-1 armhfLinux 6.3 for ARMv7 multiplatform compatible SoCs, PREEMPT_RT ii linux-image-rt-armmp 6.3.7-1 armhfLinux for ARMv7 multiplatform compatible SoCs (meta-package) root@nanopi-r1:~# apt policy Package files: 100 /var/lib/dpkg/status release a=now 90 http://ftp.de.debian.org/debian trixie/non-free-firmware armhf Packages release o=Debian,a=testing,n=trixie,l=Debian,c=non-free-firmware,b=armhf origin ftp.de.debian.org 90 http://ftp.de.debian.org/debian trixie/non-free armhf Packages release o=Debian,a=testing,n=trixie,l=Debian,c=non-free,b=armhf origin ftp.de.debian.org 90 http://ftp.de.debian.org/debian trixie/contrib armhf Packages release o=Debian,a=testing,n=trixie,l=Debian,c=contrib,b=armhf origin ftp.de.debian.org 90 http://ftp.de.debian.org/debian trixie/main armhf Packages release o=Debian,a=testing,n=trixie,l=Debian,c=main,b=armhf origin ftp.de.debian.org 500 http://ftp.de.debian.org/debian bookworm/non-free-firmware armhf Packages release v=12.0,o=Debian,a=stable,n=bookworm,l=Debian,c=non-free-firmware,b=armhf origin ftp.de.debian.org 500 http://ftp.de.debian.org/debian bookworm/non-free armhf Packages release v=12.0,o=Debian,a=stable,n=bookworm,l=Debian,c=non-free,b=armhf origin ftp.de.debian.org 500 http://ftp.de.debian.org/debian bookworm/contrib armhf Packages release v=12.0,o=Debian,a=stable,n=bookworm,l=Debian,c=contrib,b=armhf origin ftp.de.debian.org 500 http://ftp.de.debian.org/debian bookworm/main armhf Packages release v=12.0,o=Debian,a=stable,n=bookworm,l=Debian,c=main,b=armhf origin ftp.de.debian.org Pinned packages: firmware-brcm80211 -> 20230515-3 with priority 980 linux-image-rt-armmp -> 6.3.7-1 with priority 980 root@nanopi-r1:~# With this configuration, when inserting wifi module (brcmfmac), following kernel message is ... [ 2208.995544] usbcore: deregistering interface driver brcmfmac [ 2243.459746] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1 [ 2243.460057] brcmfmac mmc0:0001:1: firmware: failed to load brcm/brcmfmac43430-sdio.friendlyarm,nanopi-r1.bin (-2) [ 2243.460155] brcmfmac mmc0:0001:1: firmware: failed to load brcm/brcmfmac43430-sdio.friendlyarm,nanopi-r1.bin (-2) [ 2243.460166] brcmfmac mmc0:0001:1: Direct firmware load for brcm/brcmfmac43430-sdio.friendlyarm,nanopi-r1.bin failed with error -2 [ 2243.461611] brcmfmac mmc0:0001:1: firmware: direct-loading firmware brcm/brcmfmac43430-sdio.bin [ 2243.462219] brcmfmac mmc0:0001:1: firmware: failed to load brcm/brcmfmac43430-sdio.friendlyarm,nanopi-r1.txt (-2) [ 2243.462333] brcmfmac mmc0:0001:1: firmware: failed to load brcm/brcmfmac43430-sdio.friendlyarm,nanopi-r1.txt (-2) [ 2243.462460] brcmfmac mmc0:0001:1: firmware: failed to load brcm/brcmfmac43430-sdio.txt (-2) [ 2243.462549] brcmfmac mmc0:0001:1: firmware: failed to load brcm/brcmfmac43430-sdio.txt (-2) [ 2243.462561] brcmfmac mmc0:0001:1: Direct firmware load for brcm/brcmfmac43430-sdio.txt failed with error -2 [ 2243.462567] usbcore: registered new interface driver brcmfmac It seems SDIO chip is correctly detected, but at the same time, not possible to insert firmware. As a result, there is no network interface, because ... root@nanopi-r1:~# ip link ls 1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: eth0: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether 02:81:9f:b8:31:a7 brd ff:ff:ff:ff:ff:ff altname end0 3: eth1: mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000 link/ether a2:a8:a0:49:74:4b brd ff:ff:ff:ff:ff:ff root@nanopi-r1:~#
Bug#1041435: bitsnpicas: unusable, chokes with nullptr exception
Package: bitsnpicas Version: 2.0+ds-1 Severity: serious X-Debbugs-Cc: t...@debian.org Dear Maintainer, bitsnpicas is currently unusable and chokes with: $ bitsnpicas Exception in thread "main" java.lang.NullPointerException at java.base/java.io.Reader.(Reader.java:168) at java.base/java.io.InputStreamReader.(InputStreamReader.java:76) at java.base/java.util.Scanner.(Scanner.java:566) at com.kreative.unicode.data.Encoding.(Encoding.java:26) at com.kreative.unicode.data.EncodingList.(EncodingList.java:58) at com.kreative.unicode.data.EncodingList.instance(EncodingList.java:20) at com.kreative.bitsnpicas.edit.GlyphListModelList$GlyphListModelRootNode.(GlyphListModelList.java:93) at com.kreative.bitsnpicas.edit.GlyphListModelList.(GlyphListModelList.java:29) at com.kreative.bitsnpicas.edit.GlyphListPanel.(GlyphListPanel.java:34) at com.kreative.bitsnpicas.edit.BitmapListFrame.(BitmapListFrame.java:19) at com.kreative.bitsnpicas.edit.Main.openFont(Main.java:158) at com.kreative.bitsnpicas.edit.Main.newBitmapFont(Main.java:71) at com.kreative.bitsnpicas.edit.Main.main(Main.java:55) at com.kreative.bitsnpicas.main.Main.main(Main.java:12) This is because of the exclusion of following files w/o patching the code properly main/java/BitsNPicas/src/com/kreative/unicode/mappings/Mac*.txt main/java/BitsNPicas/src/com/kreative/unicode/mappings/Windows*.txt main/java/BitsNPicas/src/com/kreative/unicode/mappings/IBM*.txt I applied a patch trying to exclude unicodes and can get it to a usable state. The patch is attached with this bug report. However, even after being able to launch the menu, I see windows and IBM related unicode options in the menu. I did not dive deep into the code, but it could be stemming from main/java/BitsNPicas/src/com/kreative/unicode/data/unidata.ucd In which case the unicode bin itself contains non-free content and needs fixing accordingly. Thanks, Nilesh -- System Information: Debian Release: 12.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-9-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=en_IN, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8), LANGUAGE=en_US.UTF-8 Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages bitsnpicas depends on: ii xdg-utils 1.1.3-4.1 bitsnpicas recommends no packages. bitsnpicas suggests no packages. -- no debconf information diff --git a/main/java/BitsNPicas/Makefile b/main/java/BitsNPicas/Makefile index d339248..3955afc 100644 --- a/main/java/BitsNPicas/Makefile +++ b/main/java/BitsNPicas/Makefile @@ -48,47 +48,16 @@ BitsNPicas.jar: bin jar cmf dep/MANIFEST.MF BitsNPicas.jar -C bin com/kreative/unicode -C bin com/kreative/bitsnpicas chmod +x BitsNPicas.jar -BitsNPicas.app: BitsNPicas-Pre10.15.app BitsNPicas-MacOS10.15.app BitsNPicas-MacOS11.0.app +BitsNPicas.app: BitsNPicas-Pre10.15.app BitsNPicas-Pre10.15.app: dep BitsNPicas.jar - mkdir -p BitsNPicas-Pre10.15.app/Contents/MacOS mkdir -p BitsNPicas-Pre10.15.app/Contents/Resources/Java cp -f dep/PkgInfo BitsNPicas-Pre10.15.app/Contents cp -f dep/Info.plist BitsNPicas-Pre10.15.app/Contents - cp -f dep/universalJavaApplicationStub-Pre10.15 BitsNPicas-Pre10.15.app/Contents/MacOS/BitsNPicas cp -f dep/kbnp*.icns dep/dmov*.icns dep/movr*.icns BitsNPicas-Pre10.15.app/Contents/Resources cp -f dep/*.jar BitsNPicas-Pre10.15.app/Contents/Resources/Java cp -f BitsNPicas.jar BitsNPicas-Pre10.15.app/Contents/Resources/Java -BitsNPicas-MacOS10.15.app: dep BitsNPicas.jar - mkdir -p BitsNPicas-MacOS10.15.app/Contents/MacOS - mkdir -p BitsNPicas-MacOS10.15.app/Contents/Resources/Java - cp -f dep/PkgInfo BitsNPicas-MacOS10.15.app/Contents - cp -f dep/Info.plist BitsNPicas-MacOS10.15.app/Contents - cp -f dep/universalJavaApplicationStub-MacOS10.15 BitsNPicas-MacOS10.15.app/Contents/MacOS/BitsNPicas - cp -f dep/kbnp*.icns dep/dmov*.icns dep/movr*.icns BitsNPicas-MacOS10.15.app/Contents/Resources - cp -f dep/*.jar BitsNPicas-MacOS10.15.app/Contents/Resources/Java - cp -f BitsNPicas.jar BitsNPicas-MacOS10.15.app/Contents/Resources/Java - -BitsNPicas-MacOS11.0.app: dep BitsNPicas.jar - mkdir -p BitsNPicas-MacOS11.0.app/Contents/MacOS - mkdir -p BitsNPicas-MacOS11.0.app/Contents/Resources/Java - cp -f dep/PkgInfo BitsNPicas-MacOS11.0.app/Contents - cp -f dep/Info.plist BitsNPicas-MacOS11.0.app/Contents - cp -f dep/universalJavaApplicationStub-MacOS11.0 BitsNPicas-MacOS11.0.app/Contents/MacOS/BitsNPicas - cp -f dep/kbnp*.icns dep/dmov*.icns dep/movr*.icns BitsNPicas-MacOS11.0.app/Contents/Resources - cp -f dep/*.jar BitsNPicas-MacOS11.0.app/Contents/Resources/Java - cp -f BitsNPicas.jar BitsNPicas-MacOS11.0.app/Contents/Resources/Java - -BitsNPicas.dmg: BitsNPicas.app - mkdir -p dmgtmp - cp -R BitsNPicas-Pre10.15.app dmgtmp - cp -R
Bug#1041432: box64: unsatisfiable dependencies
Source: box64 Version: 0.2.2+dfsg-2 Severity: serious https://tracker.debian.org/pkg/box64 says that box64 is unable to migrate into Testing because it has unsatisfiable dependencies on amd64, arm64, ppc64el (and I guess riscv64) Thank you, Jeremy Bícha
Bug#1040628: marked as pending in Dnstwist
Control: tag -1 pending Hello, Bug #1040628 in Dnstwist reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/pkg-security-team/dnstwist/-/commit/761047d3414f7a98bb436ba2986bdf0844f9ba22 Add patch to adapt to changes in pillow 10.0.0 See https://github.com/elceef/dnstwist/issues/194 Closes: #1040628, LP: #2027963 (this message was generated automatically) -- Greetings https://bugs.debian.org/1040628
Processed: Bug#1040628 marked as pending in Dnstwist
Processing control commands: > tag -1 pending Bug #1040628 [src:dnstwist] dnstwist autopkg tests fail with pillow 10.0.0 Added tag(s) pending. -- 1040628: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040628 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1041430: ruby-sanitize: CVE-2023-36823
Source: ruby-sanitize X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerability was published for ruby-sanitize. CVE-2023-36823[0]: | Sanitize is an allowlist-based HTML and CSS sanitizer. Using | carefully crafted input, an attacker may be able to sneak arbitrary | HTML and CSS through Sanitize starting with version 3.0.0 and prior | to version 6.0.2 when Sanitize is configured to use the built-in | "relaxed" config or when using a custom config that allows `style` | elements and one or more CSS at-rules. This could result in cross- | site scripting or other undesired behavior when the malicious HTML | and CSS are rendered in a browser. Sanitize 6.0.2 performs | additional escaping of CSS in `style` element content, which fixes | this issue. Users who are unable to upgrade can prevent this issue | by using a Sanitize config that doesn't allow `style` elements, | using a Sanitize config that doesn't allow CSS at-rules, or by | manually escaping the character sequence `https://github.com/rgrove/sanitize/commit/76ed46e6dc70820f38efe27de8dabd54dddb5220 (v6.0.2) https://github.com/rgrove/sanitize/security/advisories/GHSA-f5ww-cq3m-q3g7 If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2023-36823 https://www.cve.org/CVERecord?id=CVE-2023-36823 Please adjust the affected versions in the BTS as needed.
Bug#1041429: restrictedpython: CVE-2023-37271
Source: restrictedpython X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerability was published for restrictedpython. CVE-2023-37271[0]: | RestrictedPython is a tool that helps to define a subset of the | Python language which allows users to provide a program input into a | trusted environment. RestrictedPython does not check access to stack | frames and their attributes. Stack frames are accessible within at | least generators and generator expressions, which are allowed inside | RestrictedPython. Prior to versions 6.1 and 5.3, an attacker with | access to a RestrictedPython environment can write code that gets | the current stack frame in a generator and then walk the stack all | the way beyond the RestrictedPython invocation boundary, thus | breaking out of the restricted sandbox and potentially allowing | arbitrary code execution in the Python interpreter. All | RestrictedPython deployments that allow untrusted users to write | Python code in the RestrictedPython environment are at risk. In | terms of Zope and Plone, this would mean deployments where the | administrator allows untrusted users to create and/or edit objects | of type `Script (Python)`, `DTML Method`, `DTML Document` or `Zope | Page Template`. This is a non-default configuration and likely to be | extremely rare. The problem has been fixed in versions 6.1 and 5.3. https://github.com/zopefoundation/RestrictedPython/security/advisories/GHSA-wqc8-x2pr-7jqh https://github.com/zopefoundation/RestrictedPython/commit/c8eca66ae49081f0016d2e1f094c3d72095ef531 (master) https://github.com/zopefoundation/RestrictedPython/commit/d8c5aa72c5d0ec8eceab635d93d6bc8321116002 (5.3) If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2023-37271 https://www.cve.org/CVERecord?id=CVE-2023-37271 Please adjust the affected versions in the BTS as needed.
Bug#1041427: bitcoin: CVE-2023-37192
Source: bitcoin X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerability was published for bitcoin. CVE-2023-37192[0]: | Memory management and protection issues in Bitcoin Core v22 allows | attackers to modify the stored sending address within the app's | memory, potentially allowing them to redirect Bitcoin transactions | to wallets of their own choosing. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2023-37192 https://www.cve.org/CVERecord?id=CVE-2023-37192 Please adjust the affected versions in the BTS as needed.
Bug#1041423: cjose: CVE-2023-37464
Source: cjose X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerability was published for cjose. CVE-2023-37464[0]: | OpenIDC/cjose is a C library implementing the Javascript Object | Signing and Encryption (JOSE). The AES GCM decryption routine | incorrectly uses the Tag length from the actual Authentication Tag | provided in the JWE. The spec says that a fixed length of 16 octets | must be applied. Therefore this bug allows an attacker to provide a | truncated Authentication Tag and to modify the JWE accordingly. | Users should upgrade to a version >= 0.6.2.2. Users unable to | upgrade should avoid using AES GCM encryption and replace it with | another encryption algorithm (e.g. AES CBC). https://github.com/OpenIDC/cjose/security/advisories/GHSA-3rhg-3gf2-6xgj https://github.com/OpenIDC/cjose/commit/7325e9a5e71e2fc0e350487ecac7d84acdf0ed5e (v0.6.2.2) If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2023-37464 https://www.cve.org/CVERecord?id=CVE-2023-37464 Please adjust the affected versions in the BTS as needed.
Processed: Re: RM: ganv -- RoQA; depends on gtk2
Processing control commands: > tags -1 - sid trixie Bug #1038641 [src:ganv] RM: ganv -- RoQA; depends on gtk2 Removed tag(s) trixie and sid. > severity -1 normal Bug #1038641 [src:ganv] RM: ganv -- RoQA; depends on gtk2 Severity set to 'normal' from 'serious' > reassign -1 ftp.debian.org Bug #1038641 [src:ganv] RM: ganv -- RoQA; depends on gtk2 Bug reassigned from package 'src:ganv' to 'ftp.debian.org'. No longer marked as found in versions ganv/1.8.2-1. Ignoring request to alter fixed versions of bug #1038641 to the same values previously set -- 1038641: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038641 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1038641: RM: ganv -- RoQA; depends on gtk2
Control: tags -1 - sid trixie Control: severity -1 normal Control: reassign -1 ftp.debian.org On Mon, 19 Jun 2023 15:29:40 +0200 Bastian Germann wrote: ganv does not have any reverse dependencies anymore. I suggest to remove it. The Multimedia Team has not answered this request within a month so I file the RM bug.
Processed: notfound 1041207 in 1.0.128+nmu3
Processing commands for cont...@bugs.debian.org:
> notfound 1041207 1.0.128+nmu3
Bug #1041207 {Done: Adam Borowski } [debootstrap]
debootstrap: bad NMU produces buildds not supported by dpkg _and_ CTTE
No longer marked as found in versions debootstrap/1.0.128+nmu3.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1041207: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041207
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#929685: ca-certificates-java: What is the resolution to this bug
Package: ca-certificates-java Followup-For: Bug #929685 X-Debbugs-Cc: foren...@wi.rr.com What is tyhe resolution to this bug? -- System Information: Debian Release: 12.0 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-9-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_DIE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages ca-certificates-java depends on: ii ca-certificates 20230311 ii default-jre-headless [java8-runtime-headless] 2:1.17-74 iu openjdk-17-jre-headless [java8-runtime-headless] 17.0.7+7-1~deb12u1 ca-certificates-java recommends no packages. ca-certificates-java suggests no packages. -- Configuration Files: /etc/default/cacerts [Errno 13] Permission denied: '/etc/default/cacerts' -- no debconf information
Processed: Re: Bug#1041211: libsdl-perl: FTBFS and autopkgtest failure with sdl12-compat, especially on 32-bit
Processing control commands: > tags -1 + upstream Bug #1041211 [src:sdl12-compat] libsdl-perl: FTBFS and autopkgtest failure with sdl12-compat, especially on 32-bit Added tag(s) upstream. > clone -1 -2 Bug #1041211 [src:sdl12-compat] libsdl-perl: FTBFS and autopkgtest failure with sdl12-compat, especially on 32-bit Bug 1041211 cloned as bug 1041416 1039911 was blocked by: 1041211 1039911 was not blocking any bugs. Added blocking bug(s) of 1039911: 1041416 > reassign -1 src:libsdl-perl 2.548-3 Bug #1041211 [src:sdl12-compat] libsdl-perl: FTBFS and autopkgtest failure with sdl12-compat, especially on 32-bit Bug reassigned from package 'src:sdl12-compat' to 'src:libsdl-perl'. No longer marked as found in versions sdl12-compat/1.2.64-5. Ignoring request to alter fixed versions of bug #1041211 to the same values previously set Bug #1041211 [src:libsdl-perl] libsdl-perl: FTBFS and autopkgtest failure with sdl12-compat, especially on 32-bit Marked as found in versions libsdl-perl/2.548-3. > forwarded -1 https://github.com/PerlGameDev/SDL/issues/305 Bug #1041211 [src:libsdl-perl] libsdl-perl: FTBFS and autopkgtest failure with sdl12-compat, especially on 32-bit Changed Bug forwarded-to-address to 'https://github.com/PerlGameDev/SDL/issues/305' from 'https://github.com/libsdl-org/sdl12-compat/issues/305'. > severity -2 wishlist Bug #1041416 [src:sdl12-compat] libsdl-perl: FTBFS and autopkgtest failure with sdl12-compat, especially on 32-bit Severity set to 'wishlist' from 'serious' > retitle -2 sdl12-compat: could work around libsdl-perl incorrectly freeing > SDL_SetVideoMode() result Bug #1041416 [src:sdl12-compat] libsdl-perl: FTBFS and autopkgtest failure with sdl12-compat, especially on 32-bit Changed Bug title to 'sdl12-compat: could work around libsdl-perl incorrectly freeing SDL_SetVideoMode() result' from 'libsdl-perl: FTBFS and autopkgtest failure with sdl12-compat, especially on 32-bit'. -- 1039911: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039911 1041211: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041211 1041416: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041416 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1041211: libsdl-perl: FTBFS and autopkgtest failure with sdl12-compat, especially on 32-bit
Control: tags -1 + upstream Control: clone -1 -2 Control: reassign -1 src:libsdl-perl 2.548-3 Control: forwarded -1 https://github.com/PerlGameDev/SDL/issues/305 Control: severity -2 wishlist Control: retitle -2 sdl12-compat: could work around libsdl-perl incorrectly freeing SDL_SetVideoMode() result On Tue, 18 Jul 2023 at 02:07:39 +0100, Simon McVittie wrote: > On Mon, 17 Jul 2023 at 10:35:14 +0100, Simon McVittie wrote: > > I can reproduce a use-after-free on amd64. The test doesn't crash on amd64 > > for whatever reason, but it's visible when using valgrind, or when > > recompiling sdl12-compat and libsdl2 with -fsanitize=address. > > I was able to reduce the Perl test to a small C reproducer, which I've > sent upstream to sdl12-compat (see URL above). As far as I can tell, > it's most likely to be a sdl12-compat bug, but I don't understand the > memory management for these surfaces well enough to fix it. SDL upstream have clarified that what libsdl-perl is doing here was never correct, so actually, this is more a libsdl-perl bug than a sdl12-compat bug. The result of SDL_SetVideoMode() is never meant to be freed by a library user, only internally by SDL itself. I've sent a possible fix to https://github.com/PerlGameDev/SDL/pull/306, but I'm intentionally not tagging this bug +patch, because it badly needs reviewing by someone who has written XS bindings before (I'd never tried writing XS before today). > A brute-force workaround would be to intentionally leak every surface > object that was previously the video surface, by adding a flag that > would make SDL_FreeSurface ignore it, but I hope upstream will be able > to suggest something less bad than that. Let's use #1041211 for the RC bug in libsdl-perl (FTBFS and autopkgtest failure triggered by the new version of libsdl1.2debian), and use its new clone -2 to represent a possible workaround in sdl12-compat. sdl12-compat aims for bug-for-bug compatibility with classic SDL 1.2, so they are hoping to be able to avoid the crash. If they can, I'll downgrade #1041211 to be non-RC after that workaround is uploaded. smcv
Bug#1041415: emacs: fails to install: post-installation script subprocess returned error exit status 1
Package: emacs
Version: 1:28.2+1-15
Severity: serious
Dear Maintainer,
in a sid chroot:
root@debian:~# apt install emacs
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following additional packages will be installed:
emacs-bin-common emacs-common emacs-el emacs-gtk fonts-noto-color-emoji
libgccjit0 libm17n-0 libotf1 m17n-db
Suggested packages:
emacs-common-non-dfsg ncurses-term m17n-docs
The following NEW packages will be installed:
emacs emacs-bin-common emacs-common emacs-el emacs-gtk fonts-noto-color-emoji
libgccjit0 libm17n-0 libotf1 m17n-db
0 upgraded, 10 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/57.4 MB of archives.
After this operation, 179 MB of additional disk space will be used.
Do you want to continue? [Y/n]
E: Can not write log (Is /dev/pts mounted?) - posix_openpt (19: No such device)
Selecting previously unselected package emacs-el.
(Reading database ... 243178 files and directories currently installed.)
Preparing to unpack .../0-emacs-el_1%3a28.2+1-15_all.deb ...
Unpacking emacs-el (1:28.2+1-15) ...
Selecting previously unselected package emacs-common.
Preparing to unpack .../1-emacs-common_1%3a28.2+1-15_all.deb ...
Unpacking emacs-common (1:28.2+1-15) ...
Selecting previously unselected package emacs-bin-common.
Preparing to unpack .../2-emacs-bin-common_1%3a28.2+1-15_amd64.deb ...
Unpacking emacs-bin-common (1:28.2+1-15) ...
Selecting previously unselected package libgccjit0:amd64.
Preparing to unpack .../3-libgccjit0_13.1.0-8_amd64.deb ...
Unpacking libgccjit0:amd64 (13.1.0-8) ...
Selecting previously unselected package m17n-db.
Preparing to unpack .../4-m17n-db_1.8.2-1_all.deb ...
Unpacking m17n-db (1.8.2-1) ...
Selecting previously unselected package libotf1:amd64.
Preparing to unpack .../5-libotf1_0.9.16-4_amd64.deb ...
Unpacking libotf1:amd64 (0.9.16-4) ...
Selecting previously unselected package libm17n-0:amd64.
Preparing to unpack .../6-libm17n-0_1.8.2-1_amd64.deb ...
Unpacking libm17n-0:amd64 (1.8.2-1) ...
Selecting previously unselected package emacs-gtk.
Preparing to unpack .../7-emacs-gtk_1%3a28.2+1-15_amd64.deb ...
Unpacking emacs-gtk (1:28.2+1-15) ...
Selecting previously unselected package emacs.
Preparing to unpack .../8-emacs_1%3a28.2+1-15_all.deb ...
Unpacking emacs (1:28.2+1-15) ...
Selecting previously unselected package fonts-noto-color-emoji.
Preparing to unpack .../9-fonts-noto-color-emoji_2.038-1_all.deb ...
Unpacking fonts-noto-color-emoji (2.038-1) ...
Setting up libotf1:amd64 (0.9.16-4) ...
Setting up fonts-noto-color-emoji (2.038-1) ...
Setting up m17n-db (1.8.2-1) ...
Setting up libm17n-0:amd64 (1.8.2-1) ...
Setting up libgccjit0:amd64 (13.1.0-8) ...
Setting up emacs-el (1:28.2+1-15) ...
Setting up emacs-common (1:28.2+1-15) ...
Setting up emacs-bin-common (1:28.2+1-15) ...
update-alternatives: using /usr/bin/ctags.emacs to provide /usr/bin/ctags
(ctags) in auto mode
update-alternatives: using /usr/bin/ebrowse.emacs to provide /usr/bin/ebrowse
(ebrowse) in auto mode
update-alternatives: using /usr/bin/emacsclient.emacs to provide
/usr/bin/emacsclient (emacsclient) in auto mode
update-alternatives: using /usr/bin/etags.emacs to provide /usr/bin/etags
(etags) in auto mode
Setting up emacs-gtk (1:28.2+1-15) ...
update-alternatives: using /usr/bin/emacs-gtk to provide /usr/bin/emacs (emacs)
in auto mode
Install emacsen-common for emacs
emacsen-common: Handling install of emacsen flavor emacs
>>Error occurred processing /usr/share/emacs/site-lisp/debian-startup.el: File
>>error (("Doing chmod" "Operation not supported"
>>"/usr/share/emacs/site-lisp/debian-startup.elcxkbhIA"))
ERROR: install script from emacsen-common package failed
dpkg: error processing package emacs-gtk (--configure):
installed emacs-gtk package post-installation script subprocess returned error
exit status 1
dpkg: dependency problems prevent configuration of emacs:
emacs depends on emacs-gtk (>= 1:27.1) | emacs-lucid (>= 1:27.1) | emacs-nox
(>= 1:27.1); however:
Package emacs-gtk is not configured yet.
Package emacs-lucid is not installed.
Package emacs-nox is not installed.
dpkg: error processing package emacs (--configure):
dependency problems - leaving unconfigured
Processing triggers for hicolor-icon-theme (0.17-2) ...
Processing triggers for libc-bin (2.37-6) ...
Processing triggers for man-db (2.11.2-2) ...
Processing triggers for install-info (7.0.3-2) ...
Processing triggers for mailcap (3.70+nmu1) ...
Processing triggers for fontconfig (2.14.1-4) ...
Errors were encountered while processing:
emacs-gtk
emacs
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@debian:~#
--
cheers,
Holger
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ holger@(debian|reproducible-builds|layer-acht).org
⢿⡄⠘⠷⠚⠋⠀ OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C
⠈⠳⣄
A ship is always safe at shore, but that is not what it's built for.
(Albert Einstein)
signature.asc
Description: PGP signature
Processed: user debian...@lists.debian.org, usertagging 1041299, affects 1041299, block 1041161 with 1041162 ...
Processing commands for cont...@bugs.debian.org: > user debian...@lists.debian.org Setting user to debian...@lists.debian.org (was a...@debian.org). > usertags 1041299 piuparts There were no usertags set. Usertags are now: piuparts. > affects 1041299 + graphicsmagick-imagemagick-compat libplucene-perl > imagemagick-6.q16 imagemagick-6.q16hdri Bug #1041299 [rawloader] rawloader: multiple undeclared file conflicts Added indication that 1041299 affects graphicsmagick-imagemagick-compat, libplucene-perl, imagemagick-6.q16, and imagemagick-6.q16hdri > block 1041161 with 1041162 Bug #1041161 [src:dkms] dkms autopkg test fails on arm64 1041161 was not blocked by any bugs. 1041161 was not blocking any bugs. Added blocking bug(s) of 1041161: 1041162 > found 1041332 2.17.10-9 Bug #1041332 [mrtg] mrtg: modifies conffiles (policy 10.7.3): /etc/mrtg/mrtg.cfg Marked as found in versions mrtg/2.17.10-9. > thanks Stopping processing here. Please contact me if you need assistance. -- 1041161: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041161 1041299: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041299 1041332: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041332 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1041412: golang-1.21-src: missing Breaks+Replaces: golang-1.21-go (<< 1.21~rc3)
Package: golang-1.21-src Version: 1.21~rc3-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'testing'. It installed fine in 'testing', then the upgrade to 'sid' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. 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 .../golang-1.21-src_1.21~rc3-1_all.deb ... Unpacking golang-1.21-src (1.21~rc3-1) over (1.21~rc2-2) ... dpkg: error processing archive /var/cache/apt/archives/golang-1.21-src_1.21~rc3-1_all.deb (--unpack): trying to overwrite '/usr/share/go-1.21/src/internal/platform/zosarch.go', which is also in package golang-1.21-go 1.21~rc2-2 Errors were encountered while processing: /var/cache/apt/archives/golang-1.21-src_1.21~rc3-1_all.deb cheers, Andreas golang-1.21-go=1.21~rc2-2_golang-1.21-src=1.21~rc3-1.log.gz Description: application/gzip
Bug#1041410: libdogleg-dev: missing Breaks+Replaces: libdogleg-doc (<< 0.16-2)
Package: libdogleg-dev Version: 0.16-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'testing'. It installed fine in 'testing', then the upgrade to 'sid' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. 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 .../libdogleg-dev_0.16-2_amd64.deb ... Unpacking libdogleg-dev:amd64 (0.16-2) ... dpkg: error processing archive /var/cache/apt/archives/libdogleg-dev_0.16-2_amd64.deb (--unpack): trying to overwrite '/usr/share/man/man3/libdogleg.3.gz', which is also in package libdogleg-doc 0.15.4-2 Errors were encountered while processing: /var/cache/apt/archives/libdogleg-dev_0.16-2_amd64.deb And you still have a Depends on the no longer built libdogleg-doc cheers, Andreas
Bug#1040853: python-lockfile autopkg test fail with setuptools 68
Just wanted to quickly confirm that the same fix proposed at: https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=1040854;filename=python-tinyrpc_0.6-4ubuntu1.debdiff;msg=10 works well for python-lockfile. -Dan
Bug#1037739: marked as done (libseqlib: ftbfs with GCC-13)
Your message dated Tue, 18 Jul 2023 15:04:04 + with message-id and subject line Bug#1037739: fixed in libseqlib 1.2.0+dfsg-10 has caused the Debian Bug report #1037739, regarding libseqlib: ftbfs with GCC-13 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1037739: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037739 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:libseqlib Version: 1.2.0+dfsg-9 Severity: normal Tags: sid trixie User: debian-...@lists.debian.org Usertags: ftbfs-gcc-13 [This bug is targeted to the upcoming trixie release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-13/g++-13, but succeeds to build with gcc-12/g++-12. The severity of this report will be raised before the trixie release. The full build log can be found at: http://qa-logs.debian.net/2023/05/22/logs/libseqlib_1.2.0+dfsg-9_unstable_gccexp.log The last lines of the build log are at the end of this report. To build with GCC 13, either set CC=gcc-13 CXX=g++-13 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-13/porting_to.html [...] +#MISSING: 1.2.0+dfsg-9# _ZNSt8__detail9_ExecutorIN9__gnu_cxx17__normal_iteratorIPKcNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcESaINS5_9sub_matchISB_EEENS5_12regex_traitsIcEELb1EED1Ev@Base 1.2.0 +#MISSING: 1.2.0+dfsg-9# _ZNSt8__detail9_ExecutorIN9__gnu_cxx17__normal_iteratorIPKcNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcESaINS5_9sub_matchISB_EEENS5_12regex_traitsIcEELb1EED2Ev@Base 1.2.0 _ZNSt8__detail9_Map_baseINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS6_N6SeqLib4_BamEESaISB_ENS_10_Select1stESt8equal_toIS6_ESt4hashIS6_ENS_18_Mod_range_hashingENS_20_Default_ranged_hashENS_20_Prime_rehash_policyENS_17_Hashtable_traitsILb1ELb0ELb1EEELb1EEixERS8_@Base 1.2.0 (optional)_ZNSt8__detail9_Map_baseIiSt4pairIKiSt6vectorIN6SeqLib9TIntervalIimEESaIS6_EEESaIS9_ENS_10_Select1stESt8equal_toIiESt4hashIiENS_18_Mod_range_hashingENS_20_Default_ranged_hashENS_20_Prime_rehash_policyENS_17_Hashtable_traitsILb0ELb0ELb1EEELb1EEixERS2_@Base 1.2.0 _ZNSt8__detail9_StateSeqINSt7__cxx1112regex_traitsIcEEE8_M_cloneEv@Base 1.2.0 - (optional)_ZSt11__make_heapIN9__gnu_cxx17__normal_iteratorIPN12aho_corasick7ahoemitIcEESt6vectorIS4_SaIS4_NS0_5__ops15_Iter_comp_iterIZNS2_13interval_treeIS4_E15remove_overlapsERKS8_EUlRKS4_SH_E0_EEEvT_SK_RT0_@Base 1.2.0 - (optional)_ZSt11__make_heapIN9__gnu_cxx17__normal_iteratorIPN12aho_corasick7ahoemitIcEESt6vectorIS4_SaIS4_NS0_5__ops15_Iter_comp_iterIZNS2_13interval_treeIS4_E15remove_overlapsERKS8_EUlRKS4_SH_E_EEEvT_SK_RT0_@Base 1.2.0 +#MISSING: 1.2.0+dfsg-9# (optional)_ZSt11__make_heapIN9__gnu_cxx17__normal_iteratorIPN12aho_corasick7ahoemitIcEESt6vectorIS4_SaIS4_NS0_5__ops15_Iter_comp_iterIZNS2_13interval_treeIS4_E15remove_overlapsERKS8_EUlRKS4_SH_E0_EEEvT_SK_RT0_@Base 1.2.0 +#MISSING: 1.2.0+dfsg-9# (optional)_ZSt11__make_heapIN9__gnu_cxx17__normal_iteratorIPN12aho_corasick7ahoemitIcEESt6vectorIS4_SaIS4_NS0_5__ops15_Iter_comp_iterIZNS2_13interval_treeIS4_E15remove_overlapsERKS8_EUlRKS4_SH_E_EEEvT_SK_RT0_@Base 1.2.0 (optional)_ZSt13__adjust_heapIN9__gnu_cxx17__normal_iteratorIP9mem_aln_tSt6vectorIS2_SaIS2_lS2_NS0_5__ops15_Iter_comp_iterIPFbRKS2_SB_vT_T0_SG_T1_T2_@Base 1.2.0 (optional)_ZSt13__adjust_heapIN9__gnu_cxx17__normal_iteratorIPN12aho_corasick7ahoemitIcEESt6vectorIS4_SaIS4_lS4_NS0_5__ops15_Iter_comp_iterIZNS2_13interval_treeIS4_E15remove_overlapsERKS8_EUlRKS4_SH_E_EEEvT_T0_SL_T1_T2_@Base 1.2.0 + _ZSt13__heap_selectIN9__gnu_cxx17__normal_iteratorIPN12aho_corasick7ahoemitIcEESt6vectorIS4_SaIS4_NS0_5__ops15_Iter_comp_iterIZNS2_13interval_treeIS4_E15remove_overlapsERKS8_EUlRKS4_SH_E_EEEvT_SK_SK_T0_@Base 1.2.0+dfsg-9 (optional)_ZSt13__heap_selectIN9__gnu_cxx17__normal_iteratorIPN6SeqLib13GenomicRegionESt6vectorIS3_SaIS3_NS0_5__ops15_Iter_less_iterEEvT_SB_SB_T0_@Base 1.2.0 (optional)_ZSt13binary_searchIN9__gnu_cxx17__normal_iteratorIPK
Bug#1037881: marked as done (usbguard: ftbfs with GCC-13)
Your message dated Tue, 18 Jul 2023 14:45:16 + with message-id and subject line Bug#1037881: fixed in usbguard 1.1.2+ds-4 has caused the Debian Bug report #1037881, regarding usbguard: ftbfs with GCC-13 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1037881: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037881 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:usbguard Version: 1.1.2+ds-3 Severity: normal Tags: sid trixie User: debian-...@lists.debian.org Usertags: ftbfs-gcc-13 [This bug is targeted to the upcoming trixie release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-13/g++-13, but succeeds to build with gcc-12/g++-12. The severity of this report will be raised before the trixie release. The full build log can be found at: http://qa-logs.debian.net/2023/05/22/logs/usbguard_1.1.2+ds-3_unstable_gccexp.log The last lines of the build log are at the end of this report. To build with GCC 13, either set CC=gcc-13 CXX=g++-13 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-13/porting_to.html [...] make all-recursive make[2]: Entering directory '/<>' Makefile:3515: warning: overriding recipe for target 'check' Makefile:3018: warning: ignoring old recipe for target 'check' Making all in src/Tests/ make[3]: Entering directory '/<>/src/Tests' Making all in Fuzzers make[4]: Entering directory '/<>/src/Tests/Fuzzers' make[4]: Nothing to be done for 'all'. make[4]: Leaving directory '/<>/src/Tests/Fuzzers' make[4]: Entering directory '/<>/src/Tests' make[4]: Nothing to be done for 'all-am'. make[4]: Leaving directory '/<>/src/Tests' make[3]: Leaving directory '/<>/src/Tests' make[3]: Entering directory '/<>' Makefile:3515: warning: overriding recipe for target 'check' Makefile:3018: warning: ignoring old recipe for target 'check' g++ -DHAVE_CONFIG_H -I. -I./src -fPIE -I./src -I./src/Library/public -I./src/CLI -DHAVE_BUILD_CONFIG_H -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++17 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -pthread -fPIE -fvisibility=hidden -pedantic -Wno-unknown-pragmas -Wall -Wextra -Wformat=2 -Wredundant-decls -Wcast-align -Wmissing-declarations -Wmissing-include-dirs -Wmissing-format-attribute -Wswitch-enum -Wswitch-default -Winvalid-pch -Wformat-nonliteral -Wno-deprecated-register -Wno-missing-field-initializers -Wno-implicit-fallthrough -c -o src/CLI/usbguard_rule_parser-usbguard-rule-parser.o `test -f 'src/CLI/usbguard-rule-parser.cpp' || echo './'`src/CLI/usbguard-rule-parser.cpp g++ -DHAVE_CONFIG_H -I. -I./src -fPIE -I./src -I./src/Library/public -DHAVE_BUILD_CONFIG_H -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -std=c++17 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -pthread -fPIE -fvisibility=hidden -pedantic -Wno-unknown-pragmas -Wall -Wextra -Wformat=2 -Wredundant-decls -Wcast-align -Wmissing-declarations -Wmissing-include-dirs -Wmissing-format-attribute -Wswitch-enum -Wswitch-default -Winvalid-pch -Wformat-nonliteral -Wno-deprecated-register -Wno-missing-field-initializers -Wno-implicit-fallthrough -c -o src/Common/usbguard_daemon-Utility.o `test -f 'src/Common/Utility.cpp' || echo './'`src/Common/Utility.cpp g++ -DHAVE_CONFIG_H -I. -I./src -fPIE -I./src -I./src/Library/public -I./src/CLI -DHAVE_BUILD_CONFIG_H -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -std=c++17 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -pthread -fPIE -fvisibility=hidden -pedantic -Wno-unknown-pragmas -Wall -Wextra -Wformat=2 -Wredundant-decls -Wcast-align -Wmissing-declarations -Wmissing-include-dirs -Wmissing-format-attribute -Wswitch-enum -Wswitch-default -Winvalid-pch -Wformat-nonliteral -Wno-deprecated-register -Wno-missing-field-initializers -Wno-implicit-fallthrough -c -o src/CLI/usbguard-usbguard.o `test -f 'src/CLI/usbguard.cpp' || echo './'`src/CLI/usbguard.cpp g++ -DHAVE_CONFIG_H -I. -I
Processed: Re: Bug#1040223: libimage-imlib2-perl: Creates empty package on bookworm upwards (maybe because of libimlib2-dev?)
Processing control commands: > tag -1 patch Bug #1040223 [src:libimage-imlib2-perl] libimage-imlib2-perl: Creates empty package on bookworm upwards (maybe because of libimlib2-dev?) Added tag(s) patch. -- 1040223: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040223 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1040223: libimage-imlib2-perl: Creates empty package on bookworm upwards (maybe because of libimlib2-dev?)
Control: tag -1 patch
On Mon, Jul 03, 2023 at 06:00:44PM +0200, gregor herrmann wrote:
> Source: libimage-imlib2-perl
> Version: 2.03-1.1
> Severity: grave
> Tags: bookworm trixie sid
> Justification: renders package unusable
> While looking at Niko's and Dom's first rebuilds for perl 5.38, I
> noticed that libimage-imlib2-perl "successfully" builds but creates
> a basically empty package:
>
> http://perl.debian.net/rebuild-logs/perl-5.38/libimage-imlib2-perl_2.03-1.1/libimage-imlib2-perl_2.03-1.1.buildlog
>
> dh_auto_configure -a
> dh_auto_configure: warning: Compatibility levels before 10 are deprecated
> (level 8 in use)
> /usr/bin/perl -I. Build.PL --installdirs vendor
> You must install the imlib2 library before you can install
> Image::Imlib2. You can obtain imlib2 from
> http://sourceforge.net/projects/enlightenment/
[...]
> I've started to work on patch which uses pkg-config instead of
> imlib2-config; good news: The package builds (as in: actually builds
> code :)) in oldstable+stable+testing+sid and the
> perl-5.38-rebuild-repo; but the tests only pass in oldstable,
> starting with stable/bookworm (aka libimlib2-dev >= 1.10) they fail
> with:
> # Failed test at t/simple.t line 68.
> # got: '0'
> # expected: '1'
Hi, thanks for looking at this.
FWIW I found some prior art in NetBSD for the pkg-config part:
https://github.com/NetBSD/pkgsrc/blob/trunk/graphics/p5-Image-Imlib2/patches/patch-Build.PL
but yours looks good to me as well :)
I think the failing test is a bug in imlib2 1.10.0 and I've just filed #1041406
about it.
I'm attaching a workaround that might be appropriate at least until imlib2 is
fixed.
--
Niko Tyni nt...@debian.org
>From c2d646b9fa925ac2a91cb6cfb3fe6dad430c7927 Mon Sep 17 00:00:00 2001
From: Niko Tyni
Date: Tue, 18 Jul 2023 15:16:21 +0100
Subject: [PATCH] Work around an imlib2 bug with alpha channel cloning
As discussed in https://bugs.debian.org/1041406 imlib2 1.10.0 introduced
a bug where imlib_clone_image() no longer copies the alpha flag. This
breaks test 12 of t/simple.t :
# Failed test at t/simple.t line 68.
# got: '0'
# expected: '1'
Work around this on our side by checking for any difference after
cloning and copying the alpha flag if necessary.
Bug-Debian: https://bugs.debian.org/1040223
---
lib/Image/Imlib2.xs | 11 +++
1 file changed, 11 insertions(+)
diff --git a/lib/Image/Imlib2.xs b/lib/Image/Imlib2.xs
index f48d4ec..cc54d2b 100644
--- a/lib/Image/Imlib2.xs
+++ b/lib/Image/Imlib2.xs
@@ -931,9 +931,20 @@ Imlib2_clone(image)
CODE:
{
Imlib_Image cloned;
+ char alpha_orig;
+ char alpha_cloned;
imlib_context_set_image(image);
cloned = imlib_clone_image();
+
+ /* imlib2 no longer clones the alpha flag since 1.10 */
+ alpha_orig = imlib_image_has_alpha();
+ imlib_context_set_image(cloned);
+ alpha_cloned = imlib_image_has_alpha();
+ if (alpha_orig != alpha_cloned) {
+ imlib_image_set_has_alpha(alpha_orig);
+ }
+ imlib_context_set_image(image);
RETVAL = cloned;
}
--
2.39.1
Processed: tagging 1037905
Processing commands for cont...@bugs.debian.org: > tags 1037905 + ftbfs Bug #1037905 [src:yade] yade: ftbfs with GCC-13 Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 1037905: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037905 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1037739: marked as pending in libseqlib
Control: tag -1 pending Hello, Bug #1037739 in libseqlib 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/med-team/libseqlib/-/commit/d358946f695abfb1232f12e5cfc00981ad5fea3f d/libseqlib2.symbols.amd64: update. Mark symbols optimized out by LTO as optional. This has the side effect of resolving build failures with Gcc 13. Closes: #1015520 Closes: #1037739 (this message was generated automatically) -- Greetings https://bugs.debian.org/1037739
Processed: Bug#1037739 marked as pending in libseqlib
Processing control commands: > tag -1 pending Bug #1037739 [src:libseqlib] libseqlib: ftbfs with GCC-13 Added tag(s) pending. -- 1037739: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037739 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1041077: marked as done (deepin-boot-maker FTBFS with googletest 1.13.0)
Your message dated Tue, 18 Jul 2023 13:49:01 + with message-id and subject line Bug#1041077: fixed in deepin-boot-maker 5.7.8+dfsg-3 has caused the Debian Bug report #1041077, regarding deepin-boot-maker FTBFS with googletest 1.13.0 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1041077: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041077 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: deepin-boot-maker Version: 5.7.8+dfsg-2 Severity: serious Tags: ftbfs trixie sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/deepin-boot-maker.html ... In file included from /usr/include/gtest/gtest-message.h:57, from /usr/include/gtest/gtest-assertion-result.h:46, from /usr/include/gtest/gtest.h:64, from imagecheckobj.h:4, from imagecheckobj.cpp:1: /usr/include/gtest/internal/gtest-port.h:270:2: error: #error C++ versions less than C++14 are not supported. 270 | #error C++ versions less than C++14 are not supported. | ^ ... --- End Message --- --- Begin Message --- Source: deepin-boot-maker Source-Version: 5.7.8+dfsg-3 Done: Nisha Pariyar We believe that the bug you reported is fixed in the latest version of deepin-boot-maker, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1041...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Nisha Pariyar (supplier of updated deepin-boot-maker 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, 18 Jul 2023 19:09:28 +0545 Source: deepin-boot-maker Architecture: source Version: 5.7.8+dfsg-3 Distribution: unstable Urgency: medium Maintainer: Debian Deepin Packaging Team Changed-By: Nisha Pariyar Closes: 1041077 Changes: deepin-boot-maker (5.7.8+dfsg-3) unstable; urgency=medium . * debian/patches: Fix ftbfs by removing explicit cxx11. (Closes: #1041077) * debian/control: + Bump standard version to 4.6.2. + Add myself to uploaders list. + Change in build depends libxcb-util0-dev to libxcb-util-dev. Checksums-Sha1: f4b2bcb53d5da14ff4c76b8be43a59b042e03c6d 2464 deepin-boot-maker_5.7.8+dfsg-3.dsc e5facbdd8115318a25289fd29e2f3241802dafc3 3640 deepin-boot-maker_5.7.8+dfsg-3.debian.tar.xz 0f5a1db4afbb13fdec595939e01c33562f887f59 14733 deepin-boot-maker_5.7.8+dfsg-3_amd64.buildinfo Checksums-Sha256: 7cfc5600aaa2aa49b3e46923e323395d06ab09f518a81241f81e1c6030fb10b8 2464 deepin-boot-maker_5.7.8+dfsg-3.dsc 31352dd8fe373d65d354b721f74a428aec8e539c03bee300d0964e8b261b4f28 3640 deepin-boot-maker_5.7.8+dfsg-3.debian.tar.xz 5a93eb1ac40cf279da4f6ea0da50a132976a770430ac8d45cef7987b406590d3 14733 deepin-boot-maker_5.7.8+dfsg-3_amd64.buildinfo Files: 9cbf118876908bf09f88755f3738c69b 2464 misc optional deepin-boot-maker_5.7.8+dfsg-3.dsc 8f0b2b73d2b3f68a24eacaa9de7158f1 3640 misc optional deepin-boot-maker_5.7.8+dfsg-3.debian.tar.xz 04b9c5db1a1d6509fae26e951824c4ad 14733 misc optional deepin-boot-maker_5.7.8+dfsg-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE2lMFjb4VS9/L8WutS1Qq9wT3RRYFAmS2lHcACgkQS1Qq9wT3 RRY8xw//fx3P+n4YAwQcLx42h1MROcplfoQWnIGQmhBjhXVP/gx6olKsHOh2YYuO W7hIpjr43y6LUPZ79RdcvhzsLiV2aU4u7QpJA0PDlKohUbnLJxKOCAReu4k817vj Q0Gn8Tjy7tvGhJUZj2ozGBmKstM8KZ2PgoqzbcxLNacCGHxUkJnJXYARfoa0lJTA rmXGNxLC19y43xiN7zklUw5/jTB4hC9rrOzLlBwOciRqjXlGfqKyb6UrgLN4/wke m+j9ob3bz0ZpD7ZVhiLh2ycbrg5nYFHIsZLr63v5YbHOsehcqZfwgC0ng7kdI91X qyw5IIOrdY4B4gAV+gtBSz0gKYU2WFiiwaJCQYLrKqZJOCp+ird546FUVljxubeb 5gaP7V9Xbgqo35mEDTFT3UPu4d29FempHiKoBqZtDd34HzaI7C8XqCBcCEC7Ms0j 8k/UFkRqBtGoxkcJCfeRmyAPfHuGDwMscjpgvUUlar8VomCAy0S/85OxizawIsDC IpQ47m2Hk2GrXS2uGwp1PUybyilDIx6LsLi8GCoB0leaohb2cbNNOgYd9uvqbZ6d qLZ4NqYD8meN4KY1DU27ZrAz0FUdX4wL5PqFIrbuNbu2hhHWR5NdEHMN1k2z3ILw MSlSDaiHo6anFW8+VCKqyondI8RIKvGiNZk4R0ZQHtuWi1kLZ3s= =jG7J -END PGP SIGNATURE End Message ---
Processed: owner 1041387
Processing commands for cont...@bugs.debian.org: > owner 1041387 ! Bug #1041387 [libpdfbox-java] libpdfbox-java: missing Breaks+Replaces: libpdfbox-java-doc (<< 1:1.8.16-3) Owner recorded as tony mancill . > thanks Stopping processing here. Please contact me if you need assistance. -- 1041387: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041387 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1039611 closed by Debian FTP Masters (reply to Michael Fladischer ) (Bug#1039611: fixed in python-django-celery-beat 2.5.0-1)
Processing control commands:
> reassign -1 src:python-django-celery-beat 2.4.0-1
Bug #1039611 {Done: Michael Fladischer } [src:celery,
src:python-django-celery-beat] celery breaks python-django-celery-beat
autopkgtest: 'zoneinfo.ZoneInfo' object has no attribute 'zone'
Bug reassigned from package 'src:celery, src:python-django-celery-beat' to
'src:python-django-celery-beat'.
No longer marked as found in versions python-django-celery-beat/2.4.0-1 and
celery/5.3.1-1.
No longer marked as fixed in versions python-django-celery-beat/2.5.0-1.
Bug #1039611 {Done: Michael Fladischer }
[src:python-django-celery-beat] celery breaks python-django-celery-beat
autopkgtest: 'zoneinfo.ZoneInfo' object has no attribute 'zone'
Marked as found in versions python-django-celery-beat/2.4.0-1.
> affects -1 src:celery
Bug #1039611 {Done: Michael Fladischer }
[src:python-django-celery-beat] celery breaks python-django-celery-beat
autopkgtest: 'zoneinfo.ZoneInfo' object has no attribute 'zone'
Added indication that 1039611 affects src:celery
> fixed -1 2.5.0-1
Bug #1039611 {Done: Michael Fladischer }
[src:python-django-celery-beat] celery breaks python-django-celery-beat
autopkgtest: 'zoneinfo.ZoneInfo' object has no attribute 'zone'
Marked as fixed in versions python-django-celery-beat/2.5.0-1.
--
1039611: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039611
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1039611: closed by Debian FTP Masters (reply to Michael Fladischer ) (Bug#1039611: fixed in python-django-celery-beat 2.5.0-1)
control: reassign -1 src:python-django-celery-beat 2.4.0-1 control: affects -1 src:celery control: fixed -1 2.5.0-1 Hi, On 29-06-2023 15:54, Debian Bug Tracking System wrote: python-django-celery-beat (2.5.0-1) unstable; urgency=medium . * New upstream version 2.5.0 * Refresh patches. * Add python3-cron-descriptor to Build-Depends, required by tests. * Add patch to fix language field in django.po files. * Add patch to fix tests with celery 5.3 (Closes: #1039611). * Bump Standards-Version to 4.6.2. * Update d/copyright with new years. Looking at the current autopkgtest results of python-django-celery-beat it seems that there's relations missing between python-django-celery-beat and celery. The test passes in unstable, but updating *either* python-django-celery-beat or celery in testing makes the test fail. If this failure spotted in the test is core functionality of python-django-celery-beat, then a *versioned* Breaks in celery might be in order. I recommend to *at least* update the *versioned* Depends on celery in python-django-celery-beat. Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#1037880: marked as done (usbguard-notifier: ftbfs with GCC-13)
Your message dated Tue, 18 Jul 2023 13:35:38 + with message-id and subject line Bug#1037880: fixed in usbguard-notifier 0.1.0-2 has caused the Debian Bug report #1037880, regarding usbguard-notifier: ftbfs with GCC-13 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1037880: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037880 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:usbguard-notifier Version: 0.1.0-1 Severity: normal Tags: sid trixie User: debian-...@lists.debian.org Usertags: ftbfs-gcc-13 [This bug is targeted to the upcoming trixie release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-13/g++-13, but succeeds to build with gcc-12/g++-12. The severity of this report will be raised before the trixie release. The full build log can be found at: http://qa-logs.debian.net/2023/05/22/logs/usbguard-notifier_0.1.0-1_unstable_gccexp.log The last lines of the build log are at the end of this report. To build with GCC 13, either set CC=gcc-13 CXX=g++-13 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-13/porting_to.html [...] src/Serializer.cpp: In member function ‘bool usbguardNotifier::Serializer::serialize(const usbguardNotifier::Notification&) const’: src/Serializer.cpp:59:39: error: ‘const struct usbguardNotifier::Notification’ has no member named ‘device_id’; did you mean ‘device_name’? 59 | out << n.event_type << delim << n.device_id << delim << n.device_name | ^ | device_name src/Serializer.cpp:61:14: error: ‘const struct usbguardNotifier::Notification’ has no member named ‘rule_id’; did you mean ‘rule’? 61 | << n.rule_id << delim << n.rule << std::endl; | ^~~ | rule src/Serializer.cpp: In member function ‘bool usbguardNotifier::Serializer::deserialize(std::ifstream&, usbguardNotifier::Notification&) const’: src/Serializer.cpp:95:13: error: ‘struct usbguardNotifier::Notification’ has no member named ‘device_id’; did you mean ‘device_name’? 95 | in >> n.device_id; | ^ | device_name src/Serializer.cpp:100:13: error: ‘struct usbguardNotifier::Notification’ has no member named ‘rule_id’; did you mean ‘rule’? 100 | in >> n.rule_id; | ^~~ | rule src/Serializer.cpp: In member function ‘bool usbguardNotifier::Serializer::deserialize(std::ifstream&, usbguardNotifier::Notification&) const’: src/Serializer.cpp:95:13: error: ‘struct usbguardNotifier::Notification’ has no member named ‘device_id’; did you mean ‘device_name’? 95 | in >> n.device_id; | ^ | device_name src/Serializer.cpp:100:13: error: ‘struct usbguardNotifier::Notification’ has no member named ‘rule_id’; did you mean ‘rule’? 100 | in >> n.rule_id; | ^~~ | rule make[3]: *** [Makefile:781: src/usbguard_notifier_cli-Serializer.o] Error 1 make[3]: *** Waiting for unfinished jobs make[3]: *** [Makefile:753: src/usbguard_notifier-Serializer.o] Error 1 In file included from src/Notifier.hpp:24, from src/Main.cpp:21: src/Serializer.hpp:35:5: error: ‘uint32_t’ does not name a type 35 | uint32_t device_id; | ^~~~ src/Serializer.hpp:25:1: note: ‘uint32_t’ is defined in header ‘’; did you forget to ‘#include ’? 24 | #include +++ |+#include 25 | #include src/Serializer.hpp:39:5: error: ‘uint32_t’ does not name a type 39 | uint32_t rule_id; | ^~~~ src/Serializer.hpp:39:5: note: ‘uint32_t’ is defined in header ‘’; did you forget to ‘#include ’? In file included from src/Notifier.hpp:24, from src/Notifier.cpp:22: src/Serializer.hpp:35:5: error: ‘uint32_t’ does not name a type 35 | uint32_t device_id; | ^~~~ src/Serializer.hpp:25:1: note: ‘ui
Bug#1037728: marked as done (libgenome: ftbfs with GCC-13)
Your message dated Tue, 18 Jul 2023 13:19:00 + with message-id and subject line Bug#1037728: fixed in libgenome 1.3.11+svn20110227.4616-6 has caused the Debian Bug report #1037728, regarding libgenome: ftbfs with GCC-13 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1037728: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037728 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:libgenome Version: 1.3.11+svn20110227.4616-5 Severity: normal Tags: sid trixie User: debian-...@lists.debian.org Usertags: ftbfs-gcc-13 [This bug is targeted to the upcoming trixie release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-13/g++-13, but succeeds to build with gcc-12/g++-12. The severity of this report will be raised before the trixie release. The full build log can be found at: http://qa-logs.debian.net/2023/05/22/logs/libgenome_1.3.11+svn20110227.4616-5_unstable_gccexp.log The last lines of the build log are at the end of this report. To build with GCC 13, either set CC=gcc-13 CXX=g++-13 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-13/porting_to.html [...] +#MISSING: 1.3.11+svn20110227.4616-5# _ZNSt12_Vector_baseIPN6genome13gnBaseFeatureESaIS2_EED1Ev@Base 1.3.11+svn20110227.4616 +#MISSING: 1.3.11+svn20110227.4616-5# _ZNSt12_Vector_baseIPN6genome13gnBaseFeatureESaIS2_EED2Ev@Base 1.3.11+svn20110227.4616 +#MISSING: 1.3.11+svn20110227.4616-5# _ZNSt12_Vector_baseIPN6genome15gnBaseQualifierESaIS2_EED1Ev@Base 1.3.11+svn20110227.4616 +#MISSING: 1.3.11+svn20110227.4616-5# _ZNSt12_Vector_baseIPN6genome15gnBaseQualifierESaIS2_EED2Ev@Base 1.3.11+svn20110227.4616 _ZNSt6vectorIN6genome10gnLocationESaIS1_EE17_M_realloc_insertIJRKS1_EEEvN9__gnu_cxx17__normal_iteratorIPS1_S3_EEDpOT_@Base 1.3.11+svn20110227.4616 - (optional)_ZNSt6vectorIN6genome10gnLocationESaIS1_EE6insertEN9__gnu_cxx17__normal_iteratorIPKS1_S3_EERS6_@Base 1.3.11+svn20110227.4616 +#MISSING: 1.3.11+svn20110227.4616-5# (optional)_ZNSt6vectorIN6genome10gnLocationESaIS1_EE6insertEN9__gnu_cxx17__normal_iteratorIPKS1_S3_EERS6_@Base 1.3.11+svn20110227.4616 _ZNSt6vectorIN6genome10gnLocationESaIS1_EED1Ev@Base 1.3.11+svn20110227.4616 _ZNSt6vectorIN6genome10gnLocationESaIS1_EED2Ev@Base 1.3.11+svn20110227.4616 _ZNSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EE17_M_realloc_insertIJRKS5_EEEvN9__gnu_cxx17__normal_iteratorIPS5_S7_EEDpOT_@Base 1.3.11+svn20110227.4616 _ZNSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EE17_M_realloc_insertIJS5_EEEvN9__gnu_cxx17__normal_iteratorIPS5_S7_EEDpOT_@Base 1.3.11+svn20110227.4616 - (optional)_ZNSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EE6insertEN9__gnu_cxx17__normal_iteratorIPKS5_S7_EERSA_@Base 1.3.11+svn20110227.4616 - (optional)_ZNSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EE8_M_eraseEN9__gnu_cxx17__normal_iteratorIPS5_S7_EE@Base 1.3.11+svn20110227.4616 +#MISSING: 1.3.11+svn20110227.4616-5# (optional)_ZNSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EE6insertEN9__gnu_cxx17__normal_iteratorIPKS5_S7_EERSA_@Base 1.3.11+svn20110227.4616 +#MISSING: 1.3.11+svn20110227.4616-5# (optional)_ZNSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EE8_M_eraseEN9__gnu_cxx17__normal_iteratorIPS5_S7_EE@Base 1.3.11+svn20110227.4616 _ZNSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EED1Ev@Base 1.3.11+svn20110227.4616 _ZNSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EED2Ev@Base 1.3.11+svn20110227.4616 (optional)_ZNSt6vectorIPN6genome12gnBaseHeaderESaIS2_EE17_M_realloc_insertIJRKS2_EEEvN9__gnu_cxx17__normal_iteratorIPS2_S4_EEDpOT_@Base 1.3.11+svn20110227.4616 (optional)_ZNSt6vectorIPN6genome12gnBaseHeaderESaIS2_EE17_M_realloc_insertIJS2_EEEvN9__gnu_cxx17__normal_iteratorIPS2_S4_EEDpOT_@Base 1.3.11+svn20110227.4616 - (optional)_ZNSt6vectorIPN6genome12gnBaseHeaderESaIS2_EE6insertEN9__gn
Processed: Bug#1037728 marked as pending in libgenome
Processing control commands: > tag -1 pending Bug #1037728 [src:libgenome] libgenome: ftbfs with GCC-13 Added tag(s) pending. -- 1037728: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037728 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1037728: marked as pending in libgenome
Control: tag -1 pending Hello, Bug #1037728 in libgenome 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/med-team/libgenome/-/commit/41bd06fd143f86006d0dd8ad0259fe4c0bcc0e88 d/libgenome0.symbols.amd64: update. Mark symbols optimized out by LTO as optional. This has also the side effect of resolving build issues encountered with Gcc 13. Closes: #1015488 Closes: #1037728 (this message was generated automatically) -- Greetings https://bugs.debian.org/1037728
Bug#1037891: marked as done (waybar: ftbfs with GCC-13)
Your message dated Tue, 18 Jul 2023 14:55:18 +0200
with message-id <34554c44-9d59-a901-8d17-ec217d19e...@debian.org>
and subject line fixed in 0.9.19-1
has caused the Debian Bug report #1037891,
regarding waybar: ftbfs with GCC-13
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1037891: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037891
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:waybar
Version: 0.9.17-2
Severity: normal
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-13
[This bug is targeted to the upcoming trixie release]
Please keep this issue open in the bug tracker for the package it
was filed for. If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.
The package fails to build in a test rebuild on at least amd64 with
gcc-13/g++-13, but succeeds to build with gcc-12/g++-12. The
severity of this report will be raised before the trixie release.
The full build log can be found at:
http://qa-logs.debian.net/2023/05/22/logs/waybar_0.9.17-2_unstable_gccexp.log
The last lines of the build log are at the end of this report.
To build with GCC 13, either set CC=gcc-13 CXX=g++-13 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.
apt-get -t=experimental install g++
Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-13/porting_to.html
[...]
| ^~~~
../src/modules/sway/ipc/client.cpp:96:16: error: ‘runtime_error’ is not a
member of ‘std’
96 | throw std::runtime_error("Invalid IPC magic");
|^
../src/modules/sway/ipc/client.cpp:96:16: note: ‘std::runtime_error’ is defined
in header ‘’; did you forget to ‘#include ’?
../src/modules/sway/ipc/client.cpp:100:15: error: aggregate ‘std::string
payload’ has incomplete type and cannot be defined
100 | std::string payload;
| ^~~
../src/modules/sway/ipc/client.cpp:108:18: error: ‘runtime_error’ is not a
member of ‘std’
108 | throw std::runtime_error("Unable to receive IPC payload");
| ^
../src/modules/sway/ipc/client.cpp:108:18: note: ‘std::runtime_error’ is
defined in header ‘’; did you forget to ‘#include ’?
../src/modules/sway/ipc/client.cpp:112:49: error: could not convert
‘{, , }’ from
‘’ to
‘waybar::modules::sway::Ipc::ipc_response’
112 | return {data32[0], data32[1], &payload.front()};
| ^
| |
|
../src/modules/sway/ipc/client.cpp: In member function
‘waybar::modules::sway::Ipc::ipc_response waybar::modules::sway::Ipc::send(int,
uint32_t, const std::string&)’:
../src/modules/sway/ipc/client.cpp:116:15: error: aggregate ‘std::string
header’ has incomplete type and cannot be defined
116 | std::string header;
| ^~
../src/modules/sway/ipc/client.cpp:120:15: error: invalid use of incomplete
type ‘const std::string’ {aka ‘const class std::__cxx11::basic_string’}
120 | data32[0] = payload.size();
| ^~~
/usr/include/c++/13/bits/stringfwd.h:72:11: note: declaration of ‘std::string’
{aka ‘class std::__cxx11::basic_string’}
72 | class basic_string;
| ^~~~
../src/modules/sway/ipc/client.cpp:124:16: error: ‘runtime_error’ is not a
member of ‘std’
124 | throw std::runtime_error("Unable to send IPC header");
|^
../src/modules/sway/ipc/client.cpp:124:16: note: ‘std::runtime_error’ is
defined in header ‘’; did you forget to ‘#include ’?
../src/modules/sway/ipc/client.cpp:126:18: error: invalid use of incomplete
type ‘const std::string’ {aka ‘const class std::__cxx11::basic_string’}
126 | if (::send(fd, payload.c_str(), payload.size(), 0) == -1) {
| ^~~
/usr/include/c++/13/bits/stringfwd.h:72:11: note: declaration of ‘std::string’
{aka ‘class std::__cxx11::basic_string’}
72 | class basic_string;
| ^~~~
../src/modules/sway/ipc/client.cpp:126:35: error: invalid use of incomplete
type ‘const std::string’ {aka ‘const class std::__cxx11::basic_string’}
126 |
Processed: libatomic-queue: ftbfs with GCC-13 forwarded upstream
Processing commands for cont...@bugs.debian.org: > forwarded 1037715 https://github.com/max0x7ba/atomic_queue/issues/55 Bug #1037715 [src:libatomic-queue] libatomic-queue: ftbfs with GCC-13 Set Bug forwarded-to-address to 'https://github.com/max0x7ba/atomic_queue/issues/55'. > thank you Stopping processing here. Please contact me if you need assistance. -- 1037715: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037715 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1037614: [3dprinter-general] Bug#1037614: cura-engine: ftbfs with GCC-13
thanks for collecting all the patches and putting them together. There's still an issue on i386 left, and at least from looking at the CI tests, it might have been caused by this fix: https://salsa.debian.org/3dprinting-team/cura-engine/-/pipelines Any ideas? Very interesting! I couldn't reproduce it in a i686 chroot, but after upgrading all packages (including gcc 13), I'm getting it as well. So the missing include was just the tip of the iceberg and we're seeing some real errors on 32 bit now. I'll look into, the error looks vaguely familiar...
Processed: Re: freedv: FTBFS: lpcnet_freedv.h: No such file or directory
Processing control commands: > reassign -1 codec2 Bug #1041259 [src:freedv] freedv: FTBFS: lpcnet_freedv.h: No such file or directory Bug reassigned from package 'src:freedv' to 'codec2'. No longer marked as found in versions freedv/1.8.11-1. Ignoring request to alter fixed versions of bug #1041259 to the same values previously set > found -1 1.1.1-5 Bug #1041259 [codec2] freedv: FTBFS: lpcnet_freedv.h: No such file or directory Marked as found in versions codec2/1.1.1-5. > affects -1 src:freedy Bug #1041259 [codec2] freedv: FTBFS: lpcnet_freedv.h: No such file or directory Added indication that 1041259 affects src:freedy -- 1041259: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041259 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1041259: freedv: FTBFS: lpcnet_freedv.h: No such file or directory
control: reassign -1 codec2 control: found -1 1.1.1-5 control: affects -1 src:freedy Hello, the missing header is not installed anymore by codec2, there is no bug on freedy side. To me looks like a codec2 packaging error, but it might be that this header is not intended anymore to be put into a shared include and be used as public api. In this case, we can patch freedy to not use it (looks like it might be just using it to print the library version). On Sun, 16 Jul 2023 17:42:05 +0200 Sebastian Ramacher wrote: Source: freedv Version: 1.8.11-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) https://buildd.debian.org/status/fetch.php?pkg=freedv&arch=amd64&ver=1.8.11-1%2Bb2&stamp=1689518012&raw=0 [ 95%] Building CXX object src/CMakeFiles/freedv.dir/ongui.cpp.o cd /<>/Build/src && /usr/bin/c++ -DAUDIO_ENGINE_PULSEAUDIO_ENABLE -DGIT_HASH=\"None\" -DWXUSINGDLL -D_FILE_OFFSET_BITS=64 -D__WXGTK__ -I/<>/src -I/<>/Build/src -I/<>/Build -isystem /usr/lib/x86_64-linux-gnu/wx/include/gtk3-unicode-3.2 -isystem /usr/include/wx-3.2 -isystem /usr/include/codec2 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -pthread -O2 -g -DNDEBUG -std=c++14 -MD -MT src/CMakeFiles/freedv.dir/ongui.cpp.o -MF CMakeFiles/freedv.dir/ongui.cpp.o.d -o CMakeFiles/freedv.dir/ongui.cpp.o -c /<>/src/ongui.cpp /<>/src/ongui.cpp:8:10: fatal error: lpcnet_freedv.h: No such file or directory 8 | #include "lpcnet_freedv.h" | ^ compilation terminated. make[3]: *** [src/CMakeFiles/freedv.dir/build.make:345: src/CMakeFiles/freedv.dir/ongui.cpp.o] Error 1 Cheers -- Sebastian Ramacher OpenPGP_signature Description: OpenPGP digital signature
Bug#1037804: Fixed upstream
control: tags -1 +fixed-upstream This bug has been fixed upstream. Since a new version is released soon, I'll wait for that. That fix will be included when it is packaged. Thanks, Bas
Processed: Fixed upstream
Processing control commands: > tags -1 +fixed-upstream Bug #1037804 [src:openmsx] openmsx: ftbfs with GCC-13 Added tag(s) fixed-upstream. -- 1037804: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037804 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1040837: [Pkg-rust-maintainers] Bug#1040837: Bug#1040837: rust-log: breaks API without coordination
Quoting Fabian Grünbichler (2023-07-17 21:01:07) > On Sat, Jul 15, 2023 at 05:07:25PM +0200, Jonas Smedegaard wrote: > > Quoting Jonas Smedegaard (2023-07-15 09:55:04) > > > Quoting Fabian Grünbichler (2023-07-12 19:53:08) > > > > The feature in question is probably not a good candidate for packaging > > > > though, given the lack of stability guarantees provided by upstream[0]: [...] > probably it would be best to push for stabilization :) do you want to > file some issues or should I? ;) I'd be happy if you would file these issue. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ * Sponsorship: https://ko-fi.com/drjones [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#1041388: libclang-rt-17-dev: ships /usr/lib/llvm-17/lib/clang/17/lib/wasi/libclang_rt.builtins-wasm*.a, already in libclang-rt-17-dev-wasm*
Package: libclang-rt-17-dev Version: 1:17~++20230709044550+c54ff51be9c1-1~exp1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install because it tries to overwrite other packages files. >From the attached log (scroll to the bottom...): Selecting previously unselected package libclang-rt-17-dev:amd64. Preparing to unpack .../libclang-rt-17-dev_1%3a17~++20230709044550+c54ff51be9c1-1~exp1_amd64.deb ... Unpacking libclang-rt-17-dev:amd64 (1:17~++20230709044550+c54ff51be9c1-1~exp1) ... dpkg: error processing archive /var/cache/apt/archives/libclang-rt-17-dev_1%3a17~++20230709044550+c54ff51be9c1-1~exp1_amd64.deb (--unpack): trying to overwrite '/usr/lib/llvm-17/lib/clang/17/lib/wasi/libclang_rt.builtins-wasm64.a', which is also in package libclang-rt-17-dev-wasm64 1:17~++20230709044550+c54ff51be9c1-1~exp1 Errors were encountered while processing: /var/cache/apt/archives/libclang-rt-17-dev_1%3a17~++20230709044550+c54ff51be9c1-1~exp1_amd64.deb Selecting previously unselected package libclang-rt-17-dev:amd64. Preparing to unpack .../libclang-rt-17-dev_1%3a17~++20230709044550+c54ff51be9c1-1~exp1_amd64.deb ... Unpacking libclang-rt-17-dev:amd64 (1:17~++20230709044550+c54ff51be9c1-1~exp1) ... dpkg: error processing archive /var/cache/apt/archives/libclang-rt-17-dev_1%3a17~++20230709044550+c54ff51be9c1-1~exp1_amd64.deb (--unpack): trying to overwrite '/usr/lib/llvm-17/lib/clang/17/lib/wasi/libclang_rt.builtins-wasm32.a', which is also in package libclang-rt-17-dev-wasm32 1:17~++20230709044550+c54ff51be9c1-1~exp1 Errors were encountered while processing: /var/cache/apt/archives/libclang-rt-17-dev_1%3a17~++20230709044550+c54ff51be9c1-1~exp1_amd64.deb cheers, Andreas libclang-rt-17-dev-wasm64=1:17~++20230709044550+c54ff51be9c1-1~exp1_libclang-rt-17-dev=1:17~++20230709044550+c54ff51be9c1-1~exp1.log.gz Description: application/gzip
Processed: tagging 1041384
Processing commands for cont...@bugs.debian.org: > tags 1041384 + sid trixie Bug #1041384 [librust-derive-builder-dev] librust-derive-builder-dev: impossible to install Added tag(s) sid and trixie. > thanks Stopping processing here. Please contact me if you need assistance. -- 1041384: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041384 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1041387: libpdfbox-java: missing Breaks+Replaces: libpdfbox-java-doc (<< 1:1.8.16-3)
Package: libpdfbox-java Version: 1:1.8.16-3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'testing'. It installed fine in 'testing', then the upgrade to 'sid' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. 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 .../libpdfbox-java_1%3a1.8.16-3_all.deb ... Unpacking libpdfbox-java (1:1.8.16-3) ... dpkg: error processing archive /var/cache/apt/archives/libpdfbox-java_1%3a1.8.16-3_all.deb (--unpack): trying to overwrite '/usr/share/doc/libpdfbox-java/examples/pom.xml', which is also in package libpdfbox-java-doc 1:1.8.16-2 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/libpdfbox-java_1%3a1.8.16-3_all.deb cheers, Andreas libpdfbox-java-doc=1:1.8.16-2_libpdfbox-java=1:1.8.16-3.log.gz Description: application/gzip
Bug#1041386: librust-netlink-packet-route-dev: impossible to install
Package: librust-netlink-packet-route-dev Version: 0.12.0-1+b1 Severity: grave Justification: renders package unusable -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Impossible to install: Depends on missing package librust-netlink-packet-core-0.4+default-dev -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmS2VuYACgkQLHwxRsGg ASEHeg/+I9XHtaLpg9DERDh/oR1xVub7xHjpHOo0Eexgn2jrf2bHf2TOdnESCbBt wTDJKC35rpU5ozpF2jvbxpsZ0KesqtyYwKUe7l1pIm6Q1/3CIz9Xu/i+KBAfii+I m1srqjZf2zDuQNh4dVZH1z55ZtTXHs1e/tIlECIdmOcLt2GZ76KWdAYGz/CCTDhA z7l8PQnkU/RbmA+jKPXUiE5b0kf9l9xeoqNGcWF9nhNj04MQ2nkDaDCY3TSFD7gD wWLcuvsc7xe8D5m30MDrHON0xlRGko02qe/aWI58oOfYcdIZiiVUVLtT3UyRZy+E a5M4UtVKs1slBkDG0kIH2XU6m7ue0Z34SD4ynEvg2U95u7w5WNP8xlyHFHMGhujE Di4sasX5fUZkUK2h7ikq2rmn0eReABRrUNHLdaeiH84CY3XjbSLpXQwlZy0u0Pg6 nMOHLO2hzrjZHKgmgc21fmSjJm//hh/rhlKqMY0HcOUdbSwPquy2SQTigGquhuv8 XEDaIBGuMzctRhVOvdZRLRhIiHjKpavtov2Oxib21MyxVG/r3fJ1RoqRtL954roV muKssIq/BzYLCqaqAT3X4P3Bw9hSHSpv9UL9RMEqVrdnk57gcK+nrU01ohqkLlch E6iFGGVPee1pDC4SOEjLO62afMb2iTgSnBrGksPPthrtuGoZRjg= =Jud/ -END PGP SIGNATURE-
Bug#1041385: librust-netlink-proto-dev: impossible to install
Package: librust-netlink-proto-dev Version: 0.10.0-1+b1 Severity: grave Justification: renders package unusable -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Impossible to install: Depends on missing package librust-netlink-packet-core-0.4+default-dev -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmS2VpAACgkQLHwxRsGg ASGcNA/6AyKMVC6CDJmtvKJy/Cu48JPhuc0jQIyKFzm6eCju3bDYtejKYwxhOmKl pCOqoQPErQQj06B+zxTNlPY735WQtZxFiYUMh2okv7Im94u5NFhl53ipNaWkVjYH IyQt7P0yWSSLk3V4/dy3sgcdLAAZNA+TfIgQDtm3OETLgqMzB3kK1jnZdOTfFcvo V+VV/CZP8KfslZspomsBxyVmoDc6fGMmI4Hd047cniHcb4DvgzaLnH1i3n0oqfnc HFw+/M/Q2SruF68ULeGcfwgMLsKsNJZzhTFz1wWdAO078gcGR2zxGUort5ncWBmL Gg9EzfW1Gg2lAmlwenDBx/RH5CKu25iqkvRSsbTWGVcdnpLblfDQfhMXOa7+GeqY 38sSPco8CpXlR0TGcli5mVP6nTZN9ExHvc/ZkA8r5gegl7EU2w8fJ7jMjm1cEcyP CLozTr7wv3D7qdRVScx6XabgUpLiMACUNT7b05nrgOIDYtgr/HxAUpVYM6C+bzX5 I2Kyh53hAWiqRlvMfJTIdRCvmm4Yan721b8wrOxhS+tgpAlv5+sqg/m2E3nji6LS yqIA7GgFITQUoDFxyy2E13ncFZgPpAOtvevdV6vZSAa0assIgaK4wH7EeLOdLQ8Q l6jPYXQj1DZUS4pXBhMhUyf8Ww4tr31rLTJCLTLU4HWXI3ThcVo= =YB6S -END PGP SIGNATURE-
Bug#1041384: librust-derive-builder-dev: impossible to install
Package: librust-derive-builder-dev Version: 0.9.0-5 Severity: grave Justification: renders package unusable -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Package depends on missing package librust-derive-builder-core-0.9.0+default-dev, rendering it impossible to install. - Jonas -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmS2VfYACgkQLHwxRsGg ASHj0g//bUDAwTeu7qqtjkEHUNDKBuKTu676ESwwMYj3oQYAE2677X1Gythob9oe RqXnfgRj9M+cgp2Mmi1q9902q/5tDUWXv66ecnESZZbk3fTvO4k6N3DWbxfwuwwl atsaDIbkEHwBrD4p7yuHnboruxRj4q7l5LJsLdAZ+d0S0ugZcx9whoxjRDHrTt8X 8He0OFBb+L45vrJQw8I7yv6VlcuVsm6aoLCK7t08p0LJTYlf7f+uctYBNlpxZjVc 4jUh/3GTu6WzmSr3UKfMY4SpycL7688vth5N+nb7RvhW+Q5FBj9g7rzIQjxM1Bt1 QBkr3EolSqyarfYwzOwnY3bLAERCO5kws1mkE4mopLe6ylfypIGtduzm7ChtM+E3 6JLg1GXyjcsrCYuulrVdRHKts/6zrTLCmFZnal/WmPM7gb3OhT9P3vcZSiOXGKXC wfd/80/qg8mAIlzIQHWr6nuAVlp/HEnTGon8b+Kc5rW2U01xF56MvJMGEFvf6KdG bMIyEjvdji/cLqgZshOiQfVKDb32onUVt2AuUURUcg5peDSIC2thsgJkWGl4N2ze gvLPiOtLhPm/8G7hdHSySlofSFGjQni2l4v3pj6tMk7MQCrcrZhWtezrjocmTO9Z 3j/PMGyeJxCVtJPDcl1eyAbwuA7dESbmpRglmx418Etvqm0VwPk= =CMTF -END PGP SIGNATURE-
Processed: found 1040830 in 3.9-1
Processing commands for cont...@bugs.debian.org:
> found 1040830 3.9-1
Bug #1040830 {Done: Roberto Lumbreras } [src:iperf3]
ESNET-SECADV-2023-0001: iperf3 memory allocation hazard and crash
Marked as found in versions iperf3/3.9-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1040830: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040830
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1037888: marked as done (w-scan-cpp: ftbfs with GCC-13)
Your message dated Tue, 18 Jul 2023 10:33:11 +0200 with message-id <5f3ad466-65d7-85c7-0acc-52286bcf5...@yahoo.fr> and subject line has caused the Debian Bug report #1037888, regarding w-scan-cpp: ftbfs with GCC-13 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1037888: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037888 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:w-scan-cpp Version: 0~20230121-1 Severity: normal Tags: sid trixie User: debian-...@lists.debian.org Usertags: ftbfs-gcc-13 [This bug is targeted to the upcoming trixie release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-13/g++-13, but succeeds to build with gcc-12/g++-12. The severity of this report will be raised before the trixie release. The full build log can be found at: http://qa-logs.debian.net/2023/05/22/logs/w-scan-cpp_0~20230121-1_unstable_gccexp.log The last lines of the build log are at the end of this report. To build with GCC 13, either set CC=gcc-13 CXX=g++-13 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-13/porting_to.html [...] g++ -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -g -O3 -fPIC -Werror=overloaded-virtual -Wdate-time -D_FORTIFY_SOURCE=2 -Wno-parentheses -Wno-unused-parameter -c -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -DPLUGIN_NAME_I18N='"cmd"' -DAPIVERSION='"2.6.3"' -DSTATIC_PLUGINS -I/<> -I/<>/vdr -I/<>/vdr/PLUGINS/src -I/usr/include/freetype2 -I/usr/include/libpng16 -o /<>/vdr/audio.o /<>/vdr/audio.c g++ -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -g -O3 -fPIC -Werror=overloaded-virtual -Wdate-time -D_FORTIFY_SOURCE=2 -Wno-parentheses -Wno-unused-parameter -c -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -DPLUGIN_NAME_I18N='"cmd"' -DAPIVERSION='"2.6.3"' -DSTATIC_PLUGINS -I/<> -I/<>/vdr -I/<>/vdr/PLUGINS/src -I/usr/include/freetype2 -I/usr/include/libpng16 -o /<>/vdr/channels.o /<>/vdr/channels.c g++ -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -g -O3 -fPIC -Werror=overloaded-virtual -Wdate-time -D_FORTIFY_SOURCE=2 -Wno-parentheses -Wno-unused-parameter -c -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -DPLUGIN_NAME_I18N='"cmd"' -DAPIVERSION='"2.6.3"' -DSTATIC_PLUGINS -I/<> -I/<>/vdr -I/<>/vdr/PLUGINS/src -I/usr/include/freetype2 -I/usr/include/libpng16 -o /<>/vdr/ci.o /<>/vdr/ci.c g++ -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -g -O3 -fPIC -Werror=overloaded-virtual -Wdate-time -D_FORTIFY_SOURCE=2 -Wno-parentheses -Wno-unused-parameter -c -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -DPLUGIN_NAME_I18N='"cmd"' -DAPIVERSION='"2.6.3"' -DSTATIC_PLUGINS -I/<> -I/<>/vdr -I/<>/vdr/PLUGINS/src -I/usr/include/freetype2 -I/usr/include/libpng16 -o /<>/vdr/config.o /<>/vdr/config.c g++ -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -g -O3 -fPIC -Werror=overloaded-virtual -Wdate-time -D_FORTIFY_SOURCE=2 -Wno-parentheses -Wno-unused-parameter -c -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -DPLUGIN_NAME_I18N='"cmd"' -DAPIVERSION='"2.6.3"' -DSTATIC_PLUGINS -I/<> -I/<>/vdr -I/<>/vdr/PLUGINS/src -I/usr/include/freetype2 -I/usr/include/libpng16 -o /<>/vdr/cutter.o /<>/vdr/cutter.c g++ -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -g -O3 -fPIC -Werror=overloaded-virtual -Wdate-time -D_FORTIFY_SOURCE=2 -Wno-parentheses -Wno-unused-parameter -c -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -DPLUGIN_NAME_I18N='"cmd"' -DAPIVERSION='"2.6.3"' -DSTATIC_PLUGINS -I/<> -I/<>/vdr -I/<>/vdr/PLUGINS/src -I/usr/include/freetype2 -I/usr/include/libpng16 -o /<>/vd
Bug#1037665: marked as done (freefilesync: ftbfs with GCC-13)
Your message dated Tue, 18 Jul 2023 10:30:33 +0200 with message-id <48e4d769-0eb2-e0be-e4be-99e8c8bb2...@yahoo.fr> and subject line has caused the Debian Bug report #1037665, regarding freefilesync: ftbfs with GCC-13 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1037665: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037665 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:freefilesync Version: 12.0-2 Severity: normal Tags: sid trixie User: debian-...@lists.debian.org Usertags: ftbfs-gcc-13 [This bug is targeted to the upcoming trixie release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-13/g++-13, but succeeds to build with gcc-12/g++-12. The severity of this report will be raised before the trixie release. The full build log can be found at: http://qa-logs.debian.net/2023/05/22/logs/freefilesync_12.0-2_unstable_gccexp.log The last lines of the build log are at the end of this report. To build with GCC 13, either set CC=gcc-13 CXX=g++-13 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-13/porting_to.html [...] mkdir -p /tmp/FreeFileSync_Make/ffs/src/ g++ -Wdate-time -D_FORTIFY_SOURCE=2 -DAPP_NAME_SUFFIX='L" for Debian"' -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -g -std=c++2b -pipe -DWXINTL_NO_GETTEXT_MACRO -I../.. -I../../zenXml -include "zen/i18n.h" -include "zen/warn_static.h" -Wall -Wfatal-errors -Wmissing-include-dirs -Wswitch-enum -Wcast-align -Wnon-virtual-dtor -Wno-unused-function -Wshadow -Wno-maybe-uninitialized -O3 -DNDEBUG `wx-config --version=3.2 --cxxflags --debug=no` -pthread `pkg-config --cflags openssl` `pkg-config --cflags libcurl` `pkg-config --cflags libssh2` `pkg-config --cflags gtk+-3.0` -isystem/usr/include/gtk-3.0 `pkg-config --cflags libselinux` -DHAVE_SELINUX -c ffs_paths.cpp -o /tmp/FreeFileSync_Make/ffs/src/ffs_paths.cpp.o mkdir -p /tmp/FreeFileSync_Make/ffs/src/ mkdir -p /tmp/FreeFileSync_Make/ffs/src/ mkdir -p /tmp/FreeFileSync_Make/ffs/src/ g++ -Wdate-time -D_FORTIFY_SOURCE=2 -DAPP_NAME_SUFFIX='L" for Debian"' -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -g -std=c++2b -pipe -DWXINTL_NO_GETTEXT_MACRO -I../.. -I../../zenXml -include "zen/i18n.h" -include "zen/warn_static.h" -Wall -Wfatal-errors -Wmissing-include-dirs -Wswitch-enum -Wcast-align -Wnon-virtual-dtor -Wno-unused-function -Wshadow -Wno-maybe-uninitialized -O3 -DNDEBUG `wx-config --version=3.2 --cxxflags --debug=no` -pthread `pkg-config --cflags openssl` `pkg-config --cflags libcurl` `pkg-config --cflags libssh2` `pkg-config --cflags gtk+-3.0` -isystem/usr/include/gtk-3.0 `pkg-config --cflags libselinux` -DHAVE_SELINUX -c icon_buffer.cpp -o /tmp/FreeFileSync_Make/ffs/src/icon_buffer.cpp.o g++ -Wdate-time -D_FORTIFY_SOURCE=2 -DAPP_NAME_SUFFIX='L" for Debian"' -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -g -std=c++2b -pipe -DWXINTL_NO_GETTEXT_MACRO -I../.. -I../../zenXml -include "zen/i18n.h" -include "zen/warn_static.h" -Wall -Wfatal-errors -Wmissing-include-dirs -Wswitch-enum -Wcast-align -Wnon-virtual-dtor -Wno-unused-function -Wshadow -Wno-maybe-uninitialized -O3 -DNDEBUG `wx-config --version=3.2 --cxxflags --debug=no` -pthread `pkg-config --cflags openssl` `pkg-config --cflags libcurl` `pkg-config --cflags libssh2` `pkg-config --cflags gtk+-3.0` -isystem/usr/include/gtk-3.0 `pkg-config --cflags libselinux` -DHAVE_SELINUX -c localization.cpp -o /tmp/FreeFileSync_Make/ffs/src/localization.cpp.o g++ -Wdate-time -D_FORTIFY_SOURCE=2 -DAPP_NAME_SUFFIX='L" for Debian"' -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -g -std=c++2b -pipe -DWXINTL_NO_GETTEXT_MACRO -I../.. -I../../zenXml -include "zen/i18n.h" -include "zen/warn_static.h" -Wall -Wfatal-errors -Wmissing-include-dirs -Wswitch-enum -Wcast-align -Wnon-virtual-dtor -Wno-unused-function -Wshadow -Wno-maybe-
Bug#1037614: [3dprinter-general] Bug#1037614: cura-engine: ftbfs with GCC-13
Re: Gregor Riepl > > The package fails to build in a test rebuild on at least amd64 with > > gcc-13/g++-13, but succeeds to build with gcc-12/g++-12. The > > severity of this report will be raised before the trixie release. > > This issue was due to a missing #include , and it was already fixed > upstream in an unrelated commit. Hi Gregor, thanks for collecting all the patches and putting them together. There's still an issue on i386 left, and at least from looking at the CI tests, it might have been caused by this fix: https://salsa.debian.org/3dprinting-team/cura-engine/-/pipelines Any ideas? I have only an old and super slow notebook here on vacation, so can't really do any C++ debugging now. Christoph
Bug#1036281: marked as done (libraw: CVE-2023-1729)
Your message dated Tue, 18 Jul 2023 07:20:18 + with message-id and subject line Bug#1036281: fixed in libraw 0.21.1-5 has caused the Debian Bug report #1036281, regarding libraw: CVE-2023-1729 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.) -- 1036281: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036281 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libraw X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerability was published for libraw. CVE-2023-1729[0]: | A flaw was found in LibRaw. A heap-buffer-overflow in raw2image_ex() | caused by a maliciously crafted file may lead to an application crash. https://bugzilla.redhat.com/show_bug.cgi?id=2188240 https://github.com/LibRaw/LibRaw/issues/557 Fixed by: https://github.com/LibRaw/LibRaw/commit/9ab70f6dca19229cb5caad7cc31af4e7501bac93 (master) Fixed by: https://github.com/LibRaw/LibRaw/commit/477e0719ffc07190c89b4f3d12d51b1292e75828 (0.21-stable) If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2023-1729 https://www.cve.org/CVERecord?id=CVE-2023-1729 Please adjust the affected versions in the BTS as needed. --- End Message --- --- Begin Message --- Source: libraw Source-Version: 0.21.1-5 Done: Matteo F. Vescovi We believe that the bug you reported is fixed in the latest version of libraw, 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 1036...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matteo F. Vescovi (supplier of updated libraw package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 05 Jul 2023 22:47:57 +0200 Source: libraw Architecture: source Version: 0.21.1-5 Distribution: unstable Urgency: medium Maintainer: Debian PhotoTools Maintainers Changed-By: Matteo F. Vescovi Closes: 1036281 Changes: libraw (0.21.1-5) unstable; urgency=medium . * debian/patches/: patchset updated (Closes: #1036281) - 0001-Do-not-set-shrink-flag-for-3-4-component-images.patch added CVE-2023-1729: | A flaw was found in LibRaw. A heap-buffer-overflow | in raw2image_ex() caused by a maliciously crafted file | may lead to an application crash. Checksums-Sha1: 4dac7a2e3bc14edfc4c8b6a93b542a35d2339422 2339 libraw_0.21.1-5.dsc b7ee789d5d6b46cde1a3431646b0200b4d33f5d2 23828 libraw_0.21.1-5.debian.tar.xz 41bfdee6b2a9a5ee03e61c42b8403ec34e586870 6496 libraw_0.21.1-5_source.buildinfo Checksums-Sha256: a079cee63b48be5b58d6cac13e66d3982909b8d74a29e09b8a585e4e6e2389ce 2339 libraw_0.21.1-5.dsc f990e84a42edcd2b4af0f3c5a38a3b73e810008ab13d6ce480dc3336a825f377 23828 libraw_0.21.1-5.debian.tar.xz 0624d508c2cf98136932a50529c793353e466b8f254196fe9a1d29437590fb32 6496 libraw_0.21.1-5_source.buildinfo Files: ca53b7cabaf4b10ec93af27add759d94 2339 libs optional libraw_0.21.1-5.dsc 5048b249ea5d4a20f1b9150b27ac52a1 23828 libs optional libraw_0.21.1-5.debian.tar.xz 8e4718eeed5ea982b7cd80f65d64754f 6496 libs optional libraw_0.21.1-5_source.buildinfo -BEGIN PGP SIGNATURE- Comment: Debian powered! iQKTBAEBCgB9FiEE890J+NqH0d9QRsmbBhL0lE7NzVoFAmS2NrtfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEYz REQwOUY4REE4N0QxREY1MDQ2Qzk5QjA2MTJGNDk0NEVDRENENUEACgkQBhL0lE7N zVqfmxAAh+DydQPCpTvNxaaYqijufwNyFMdFCk98tnT0PtEajk8kSlPPtgDKK7NB ab1694TzPdn4AiWV/B4yIcp1VuuBaB0/ab5JNDXZFr7mEXw7uKOh3BG8hj30t+L6 5hQ+GOGlEQ6u9RKWchE9gw+jImBObPLMAETwvP9/SKaLcPJEzUtRmkhBvvJl3zJ3 T+fe9+ecjLzaK8O3cRWanNWg44HJlesGufxAl4yaXFUEcMo7oqRpjpu6yu1hYieN gCHxHAbd9OvECUEavTXhvF/U731h1m+9rCg74JeOi45cEr1VYDL8RB4jDavt2FMa RhEF20PIJ3TkijYve5myAbFi5SC6MJIFuLNsDW9AyaNuC0LcmtnPPEGMCb8kWOqD DoBvNS50CVYXg2i7VrqWV2yDmQxAfXOd0l7EOQHP4iVn1BeV3IXmNrPI1Tn+z7H3 tt0S/X2aIbJ0AoX7/x70uttlBXbaRKkHvqxPLEpGB5IOnios2Ni4QCnL6VCTfN/x 20tlcDWnJwJPHViR5KdJ5yvQAT/FDO2ooRIQpHXRM2Td6S257P61wxrfyt+Wr4Sc +a/A09hD6X4zZFzYrRUIk3Ivz7y3OG+EDQ55xyPaDbXFvnwQbbV/K6frFDA0T+Qa /SHQmsLx95dftQ8+eYr2kt9kAuWAo2ZOxyi2iaDKi6nQVDJbwq8= =wZsJ
Bug#1037730: marked as done (libheif: ftbfs with GCC-13)
Your message dated Tue, 18 Jul 2023 08:56:47 +0200 with message-id and subject line Re: libheif: ftbfs with GCC-13 has caused the Debian Bug report #1037730, regarding libheif: ftbfs with GCC-13 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1037730: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037730 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:libheif Version: 1.15.1-1 Severity: normal Tags: sid trixie User: debian-...@lists.debian.org Usertags: ftbfs-gcc-13 [This bug is targeted to the upcoming trixie release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-13/g++-13, but succeeds to build with gcc-12/g++-12. The severity of this report will be raised before the trixie release. The full build log can be found at: http://qa-logs.debian.net/2023/05/22/logs/libheif_1.15.1-1_unstable_gccexp.log The last lines of the build log are at the end of this report. To build with GCC 13, either set CC=gcc-13 CXX=g++-13 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-13/porting_to.html [...] make -f CMakeFiles/Makefile2 all make[2]: Entering directory '/<>/obj-x86_64-linux-gnu' make -f libheif/CMakeFiles/heif.dir/build.make libheif/CMakeFiles/heif.dir/depend make[3]: Entering directory '/<>/obj-x86_64-linux-gnu' cd /<>/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /<> /<>/libheif /<>/obj-x86_64-linux-gnu /<>/obj-x86_64-linux-gnu/libheif /<>/obj-x86_64-linux-gnu/libheif/CMakeFiles/heif.dir/DependInfo.cmake --color= make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu' make -f libheif/CMakeFiles/heif.dir/build.make libheif/CMakeFiles/heif.dir/build make[3]: Entering directory '/<>/obj-x86_64-linux-gnu' [ 2%] Building CXX object libheif/CMakeFiles/heif.dir/heif_context.cc.o cd /<>/obj-x86_64-linux-gnu/libheif && /usr/bin/c++ -DENABLE_MULTITHREADING_SUPPORT=1 -DENABLE_PARALLEL_TILE_DECODING=1 -DENABLE_PLUGIN_LOADING=1 -DHAVE_AOM_DECODER=1 -DHAVE_AOM_ENCODER=1 -DHAVE_DAV1D=1 -DHAVE_LIBDE265=1 -DHAVE_UNISTD_H -DHAVE_VISIBILITY -DHAVE_X265=1 -DLIBHEIF_EXPORTS -DWITH_DEFLATE_HEADER_COMPRESSION=1 -Dheif_EXPORTS -I/<>/obj-x86_64-linux-gnu -I/<> -I/<>/include/libheif -I/<>/include -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -fvisibility=hidden -fvisibility-inlines-hidden -Wall -Werror -Wsign-compare -Wconversion -Wno-sign-conversion -Wno-error=conversion -Wno-error=unused-parameter -Wno-error=deprecated-declarations -std=c++11 -MD -MT libheif/CMakeFiles/heif.dir/heif_context.cc.o -MF CMakeFiles/heif.dir/heif_context.cc.o.d -o CMakeFiles/heif.dir/heif_context.cc.o -c /<>/libheif/heif_conte xt.cc [ 4%] Building CXX object libheif/CMakeFiles/heif.dir/box.cc.o [ 6%] Building CXX object libheif/CMakeFiles/heif.dir/bitstream.cc.o [ 8%] Building CXX object libheif/CMakeFiles/heif.dir/heif.cc.o [ 10%] Building CXX object libheif/CMakeFiles/heif.dir/error.cc.o [ 13%] Building CXX object libheif/CMakeFiles/heif.dir/heif_file.cc.o cd /<>/obj-x86_64-linux-gnu/libheif && /usr/bin/c++ -DENABLE_MULTITHREADING_SUPPORT=1 -DENABLE_PARALLEL_TILE_DECODING=1 -DENABLE_PLUGIN_LOADING=1 -DHAVE_AOM_DECODER=1 -DHAVE_AOM_ENCODER=1 -DHAVE_DAV1D=1 -DHAVE_LIBDE265=1 -DHAVE_UNISTD_H -DHAVE_VISIBILITY -DHAVE_X265=1 -DLIBHEIF_EXPORTS -DWITH_DEFLATE_HEADER_COMPRESSION=1 -Dheif_EXPORTS -I/<>/obj-x86_64-linux-gnu -I/<> -I/<>/include/libheif -I/<>/include -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -fvisibility=hidden -fvisibility-inlines-hidden -Wall -Werror -Wsign-compare -Wconversion -Wno-sign-conversion -Wno-error=conversion -Wno-error=unused-parameter -Wno-error=deprecated-declarations -std=c++11 -MD -MT libheif/CMakeFiles/heif.dir/box.cc.o -MF CMakeFiles/heif.dir/box.cc.o.d -o CMakeFiles/heif.dir/box.cc.o -c /<>/libheif/box.cc cd /<>/obj-x86_64-linux-gnu/libheif && /usr
