Bug#973905: block 973905 by 972803
block 973905 by 972803 fixed 973905 0.6.0-2 thanks This bug has been fixed in git [1], but can't be uploaded since the package doesn't build with python 3.9 (#972803). [1]: https://salsa.debian.org/python-team/packages/python-typing-inspect/-/commit/7d1368bad8b2a76c83018195bb35fe85ebc480d2 -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau ⢿⡄⠘⠷⠚⠋ po...@debian.org / veronneau.org ⠈⠳⣄ OpenPGP_signature Description: OpenPGP digital signature
Processed: block 973905 by 972803
Processing commands for cont...@bugs.debian.org: > block 973905 by 972803 Bug #973905 [src:python-typing-inspect] python-typing-inspect's autopkg test fails 973905 was not blocked by any bugs. 973905 was not blocking any bugs. Added blocking bug(s) of 973905: 972803 > fixed 973905 0.6.0-2 Bug #973905 [src:python-typing-inspect] python-typing-inspect's autopkg test fails The source 'python-typing-inspect' and version '0.6.0-2' do not appear to match any binary packages Marked as fixed in versions python-typing-inspect/0.6.0-2. > thanks Stopping processing here. Please contact me if you need assistance. -- 973905: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973905 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#959905: Any update?
Hi Alexandre, Any update on this bug? It's stopping the migration to testing and it would be nice to have this tool in the next stable release of Debian. Thanks! -- Martin Michlmayr https://www.cyrius.com/
Bug#977516: osmo-bsc: build-depends on obsolete package.
On 16/12/2020 21:48, Thorsten Alteholz wrote: Hi Peter, are you sure about your bug report? The control file of osmo-bsc/1.6.1+dfsg1-3 contains: Build-Depends: debhelper-compat (= 12), pkg-config, libosmocore-dev (>= 1.4.0), libosmo-sccp-dev (>= 1.3.0), libosmo-mgcp-client-dev (>= 1.7.0), libosmo-legacy-mgcp-dev, libosmo-abis-dev (>= 1.0.1), libosmo-netif-dev (>= 1.0.0), libosmo-sigtran-dev (>= 1.3.0), libsqlite3-dev, libpcap-dev, libcdk5-dev, txt2man # libosmo-legacy-mgcp-dev (>= 1.7.0), The dependency libosmo-legacy-mgcp-dev is commented out I see libosmo-legacy-mgcp-dev in the build-dependency list twice, the second one is commented out, but the first one is still active. and instead libosmo-mgcp-client-dev (>= 1.7.0) is used, which is provided by osmo-mgw/1.7.0+dfsg1-2 Thorsten
Bug#977185: marked as done (nheko: switch to Boost 1.74)
Your message dated Thu, 17 Dec 2020 00:04:53 + with message-id and subject line Bug#977185: fixed in nheko 0.7.2-3 has caused the Debian Bug report #977185, regarding nheko: switch to Boost 1.74 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.) -- 977185: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977185 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: nheko Version: 0.7.2-2 Severity: serious X-Debbugs-Cc: sramac...@debian.org nheko currently hardcodes its boost build dependencies with an explicit version. Since the default boost version is now 1.74 and we are trying to remove boost 1.71 before the release of bullseye, please switch to 1.74 or to the unversioned boost packages. Cheers -- Sebastian Ramacher signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: nheko Source-Version: 0.7.2-3 Done: Hubert Chathi We believe that the bug you reported is fixed in the latest version of nheko, 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 977...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Hubert Chathi (supplier of updated nheko package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 14 Dec 2020 16:02:58 -0500 Source: nheko Architecture: source Version: 0.7.2-3 Distribution: unstable Urgency: medium Maintainer: Matrix Packaging Team Changed-By: Hubert Chathi Closes: 977185 Changes: nheko (0.7.2-3) unstable; urgency=medium . * debian/control: * Use default boost dev packages (Closes: #977185) Checksums-Sha1: 3122a9cbd9cef398275b192d696980a576946cfb 2416 nheko_0.7.2-3.dsc 64e0c136096b745dfb2251b78b409766116ed851 12876 nheko_0.7.2-3.debian.tar.xz ce7ca25d52de40c92f269b9bd9c72ccdd69a8160 1 nheko_0.7.2-3_amd64.buildinfo Checksums-Sha256: 9aee4bd76b221e007e6e307eaa7da45eb9ba6dfa901f548c769d2afb66f09077 2416 nheko_0.7.2-3.dsc 15111652930c337c5f7395eb233ab53a4e526d74bd8d9ad2bdd533e426262ae9 12876 nheko_0.7.2-3.debian.tar.xz 53f7fc0b373a26b08bdd12ebe782e6d62219ae76766291bf11b96ba96e6f 1 nheko_0.7.2-3_amd64.buildinfo Files: 275d9ce3abbd0555d445d9abc85425c0 2416 net optional nheko_0.7.2-3.dsc 355df998045228b9fd37a09a58c08e47 12876 net optional nheko_0.7.2-3.debian.tar.xz 802b7108388e80722721ba36d14cc918 1 net optional nheko_0.7.2-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQEzBAEBCgAdFiEE3juhvb4UN2X4rCw4rXmvZUDjNa8FAl/anBwACgkQrXmvZUDj Na8d3wf7BYQAZ/OuxPxjpixDWmZyiueGKbmBUnn7v/zqLkOc7cziYFZwOi8OeB2o zBD8LbxgRIG9hG3isSAzw/prpF5R77JdMdcX2p3rh8zpKvR93auC0YENyj7VQ6r3 FQH3nLiMatNLI3ZlyUzUShDCDcw/H44XeCia7+FrVPiptF33sscnxN6BoaMcN9DC /Z4ncMbG4QK5m1Cgn1O1/kJsgCXWDIj3wWNUoxX94plIB+7vAB63Jxzm46qnJNhZ 22Y5Aiv9N1ACAOfr/CCTzSYQbfDFl8ghtYRBnxqdenu7yLULaGUCQ/X8ucG4TCXV uHlPKUMC5hSh+E3Jv+27BP+G2tsHgg== =X511 -END PGP SIGNATURE End Message ---
Bug#977551: marked as done (gprbuild's autopkg tests fail)
Your message dated Wed, 16 Dec 2020 23:39:56 + with message-id and subject line Bug#977551: fixed in gprbuild 2021.0.0.0778b109-4 has caused the Debian Bug report #977551, regarding gprbuild's autopkg tests fail to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 977551: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977551 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:gprbuild Version: 2021.0.0.0778b109-3 Severity: serious Tags: sid bullseye two tests fail: autopkgtest [18:06:29]: test gpr-wrapper: [--- ==Messages for file: /tmp/autopkgtest-lxc.a8l7fm0h/downtmp/autopkgtest_tmp/p.gpr 1. with "gpr.gpr"; | >>> imported project file "gpr.gpr" not found gprbuild: "p.gpr" processing failed autopkgtest [18:06:30]: test gpr-wrapper: ---] autopkgtest [18:06:30]: test gpr-wrapper: - - - - - - - - - - results - - - - - - - - - - gpr-wrapper FAIL non-zero exit status 4 autopkgtest [18:06:30]: test gpr-wrapper: - - - - - - - - - - stderr - - - - - - - - - - gprbuild: "p.gpr" processing failed autopkgtest [18:07:44]: test examples: [--- cp: cannot stat '/usr/share/doc/gprbuild/examples': No such file or directory autopkgtest [18:07:46]: test examples: ---] autopkgtest [18:07:46]: test examples: - - - - - - - - - - results - - - - - - - - - - examples FAIL non-zero exit status 1 autopkgtest [18:07:46]: test examples: - - - - - - - - - - stderr - - - - - - - - - - cp: cannot stat '/usr/share/doc/gprbuild/examples': No such file or directory --- End Message --- --- Begin Message --- Source: gprbuild Source-Version: 2021.0.0.0778b109-4 Done: Nicolas Boulenguez We believe that the bug you reported is fixed in the latest version of gprbuild, 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 977...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Nicolas Boulenguez (supplier of updated gprbuild package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 16 Dec 2020 23:07:44 + Source: gprbuild Architecture: source Version: 2021.0.0.0778b109-4 Distribution: unstable Urgency: medium Maintainer: Nicolas Boulenguez Changed-By: Nicolas Boulenguez Closes: 977551 Changes: gprbuild (2021.0.0.0778b109-4) unstable; urgency=medium . * Fix dependencies for gpr-wrapper autopkgtest. Closes: #977551. * Standards-Version: 4.5.1. Checksums-Sha1: fe52979f73ef2666ee1b3c87dffd567e1ddb5990 2532 gprbuild_2021.0.0.0778b109-4.dsc 00d144d0b034cdf29c9f5abd36a3758be77d20a4 19860 gprbuild_2021.0.0.0778b109-4.debian.tar.xz 210409b0f76f7ff01227be79ebfae4cce825ed09 4216 gprbuild_2021.0.0.0778b109-4_source.buildinfo Checksums-Sha256: ab9994f177192ea77faa6407a11c266e86cc5cb455df7b71f96b7a06d24f127d 2532 gprbuild_2021.0.0.0778b109-4.dsc f6905e901267bac29eb12cfdfbb4487c87edeff1d22934a6136a0756ba412d14 19860 gprbuild_2021.0.0.0778b109-4.debian.tar.xz 11f684b5c524bed612087d5475bb1aa14ab08e7643f8a18ce606a075c2ec41f5 4216 gprbuild_2021.0.0.0778b109-4_source.buildinfo Files: c28cab7262ab53c0f31abb5e11aa27c8 2532 devel optional gprbuild_2021.0.0.0778b109-4.dsc e90e5a7e1fba89fcccaa2004cedc270c 19860 devel optional gprbuild_2021.0.0.0778b109-4.debian.tar.xz 4fd329015d27fad7430f96db139a4990 4216 devel optional gprbuild_2021.0.0.0778b109-4_source.buildinfo -BEGIN PGP SIGNATURE- iQJHBAEBCAAxFiEEYtlNMqmXIhEvWffytSqc9EkN/I0FAl/alEoTHG5pY29sYXNA ZGViaWFuLm9yZwAKCRC1Kpz0SQ38jRgtD/0SSnrB2Fi0uWDe9Yso7Can3ktoFNBZ O6QkjhBUZ6xBVp/B8/On+a/xP91gNsbyake2VuL9bTwKLatXgZeuFLtisMtI08OX PbvzNFMQxzNWPvY9vwryJ2P3GtRB+6aFL9OTBr7KwNtMVaYftLiXVdtvpxZvcUdm n4mr0GxaoBhgV3ehgNMrGfEDBP++hiawedtPBUbD78qcBAiUWLIABEl50C8k/FZP ofKqaJpx/SvKucnIT2xpY70COfI7duKQ5IPnm7Q6Y3ewRyplC9bIRUj2FUvcynoI ccut2muUAhhwG7/UdrNsdsNMkK7tbv4rFIfBcBrn9F7I15XTjcuBWtC38LkLPpji H5BxhMxN6iRZPrE7eB6BIStpJukmUSzTFAwzn+pWS6Tnp67V7BMNXDgcyKFOldTq XizPD54On4ylnXeGSb+hoVlEZ8Zj1IxCZl9PH9mUbpqACfbOW+9fgoKOHokM89Hw GoxM7Q7eC/UTqb2LSduMRhpShjoJsfhbVFeSwpSxb9dwJGJM9h41/ylRGrTgpMJp lOugsSAewLpNHxUMX8XzSIWU/ykMoZb7T/HmKK+n1gFd
Bug#977516: osmo-bsc: build-depends on obsolete package.
Hi Peter, are you sure about your bug report? The control file of osmo-bsc/1.6.1+dfsg1-3 contains: Build-Depends: debhelper-compat (= 12), pkg-config, libosmocore-dev (>= 1.4.0), libosmo-sccp-dev (>= 1.3.0), libosmo-mgcp-client-dev (>= 1.7.0), libosmo-legacy-mgcp-dev, libosmo-abis-dev (>= 1.0.1), libosmo-netif-dev (>= 1.0.0), libosmo-sigtran-dev (>= 1.3.0), libsqlite3-dev, libpcap-dev, libcdk5-dev, txt2man # libosmo-legacy-mgcp-dev (>= 1.7.0), The dependency libosmo-legacy-mgcp-dev is commented out and instead libosmo-mgcp-client-dev (>= 1.7.0) is used, which is provided by osmo-mgw/1.7.0+dfsg1-2 Thorsten
Processed: diff NMU for 0.46.0-1.1
Processing commands for cont...@bugs.debian.org: > tags 977226 +pending +patch Bug #977226 [src:openmw] openmw FTBFS: error: ‘for_each’ is not a member of ‘std’ Added tag(s) pending. Bug #977226 [src:openmw] openmw FTBFS: error: ‘for_each’ is not a member of ‘std’ Added tag(s) patch. > user team+bo...@tracker.debian.org Setting user to team+bo...@tracker.debian.org (was gl...@debian.org). > usertag 977226 +boost174 There were no usertags set. Usertags are now: boost174. > thanks Stopping processing here. Please contact me if you need assistance. -- 977226: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977226 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#977226: diff NMU for 0.46.0-1.1
tags 977226 +pending +patch user team+bo...@tracker.debian.org usertag 977226 +boost174 thanks Dear maintainer, I have prepared an NMU (versioned as 0.46.0-1.1) and uploaded to DELAYED/5. Please feel free to tell me if I should delay it longer, cancel or reschedule. Diff is attached. MR is here [1]. [1] https://salsa.debian.org/games-team/openmw/-/merge_requests/1 Best regards Anton nmu.debdiff Description: Binary data
Bug#957378: marked as done (isoqlog: ftbfs with GCC-10)
Your message dated Wed, 16 Dec 2020 22:33:38 + with message-id and subject line Bug#957378: fixed in isoqlog 2.2.1-9.1 has caused the Debian Bug report #957378, regarding isoqlog: ftbfs with GCC-10 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.) -- 957378: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957378 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:isoqlog Version: 2.2.1-9 Severity: normal Tags: sid bullseye User: debian-...@lists.debian.org Usertags: ftbfs-gcc-10 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-10/g++-10, but succeeds to build with gcc-9/g++-9. The severity of this report will be raised before the bullseye release, so nothing has to be done for the buster release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc10-20200225/isoqlog_2.2.1-9_unstable_gcc10.log The last lines of the build log are at the end of this report. To build with GCC 10, either set CC=gcc-10 CXX=g++-10 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-10/porting_to.html [...] /usr/bin/ld: LangCfg.o:./isoqlog/LangCfg.h:10: multiple definition of `L_Daily'; main.o:./isoqlog/LangCfg.h:10: first defined here /usr/bin/ld: LangCfg.o:./isoqlog/LangCfg.h:9: multiple definition of `L_Creationtime'; main.o:./isoqlog/LangCfg.h:9: first defined here /usr/bin/ld: LangCfg.o:./isoqlog/LangCfg.h:8: multiple definition of `L_Average'; main.o:./isoqlog/LangCfg.h:8: first defined here /usr/bin/ld: LangCfg.o:./isoqlog/Global.h:17: multiple definition of `t2'; Store.o:./isoqlog/Global.h:17: first defined here /usr/bin/ld: LangCfg.o:./isoqlog/Global.h:16: multiple definition of `today'; Store.o:./isoqlog/Global.h:16: first defined here /usr/bin/ld: LangCfg.o:./isoqlog/Global.h:15: multiple definition of `secs'; Store.o:./isoqlog/Global.h:15: first defined here /usr/bin/ld: Html.o:./isoqlog/LangCfg.h:13: multiple definition of `L_Encoding'; main.o:./isoqlog/LangCfg.h:13: first defined here /usr/bin/ld: Html.o:./isoqlog/LangCfg.h:24: multiple definition of `L_Stats'; main.o:./isoqlog/LangCfg.h:24: first defined here /usr/bin/ld: Html.o:./isoqlog/Dir.h:9: multiple definition of `cur_year'; Store.o:./isoqlog/Dir.h:9: first defined here /usr/bin/ld: Html.o:./isoqlog/Dir.h:9: multiple definition of `cur_month'; Store.o:./isoqlog/Dir.h:9: first defined here /usr/bin/ld: Html.o:./isoqlog/Dir.h:9: multiple definition of `cur_day'; Store.o:./isoqlog/Dir.h:9: first defined here /usr/bin/ld: Html.o:./isoqlog/Dir.h:9: multiple definition of `cur_min'; Store.o:./isoqlog/Dir.h:9: first defined here /usr/bin/ld: Html.o:./isoqlog/LangCfg.h:9: multiple definition of `L_Creationtime'; main.o:./isoqlog/LangCfg.h:9: first defined here /usr/bin/ld: Html.o:./isoqlog/Dir.h:9: multiple definition of `cur_hour'; Store.o:./isoqlog/Dir.h:9: first defined here /usr/bin/ld: Html.o:./isoqlog/LangCfg.h:18: multiple definition of `L_Number'; main.o:./isoqlog/LangCfg.h:18: first defined here /usr/bin/ld: Html.o:./isoqlog/LangCfg.h:19: multiple definition of `L_Receiver'; main.o:./isoqlog/LangCfg.h:19: first defined here /usr/bin/ld: Html.o:./isoqlog/LangCfg.h:14: multiple definition of `L_Mail'; main.o:./isoqlog/LangCfg.h:14: first defined here /usr/bin/ld: Html.o:./isoqlog/LangCfg.h:25: multiple definition of `L_Top'; main.o:./isoqlog/LangCfg.h:25: first defined here /usr/bin/ld: Html.o:./isoqlog/Data.h:111: multiple definition of `SortDomain'; Store.o:./isoqlog/Data.h:111: first defined here /usr/bin/ld: Html.o:./isoqlog/LangCfg.h:21: multiple definition of `L_Sender'; main.o:./isoqlog/LangCfg.h:21: first defined here /usr/bin/ld: Html.o:./isoqlog/LangCfg.h:23: multiple definition of `L_Size'; main.o:./isoqlog/LangCfg.h:23: first defined here /usr/bin/ld: Html.o:./isoqlog/LangCfg.h:26: multiple definition of `L_Total'; main.o:./isoqlog/LangCfg.h:26: first defined here /usr/bin/ld: Html.o:./isoqlog/LangCfg.h:20: multiple definition of `L_Received'; main.o:./isoqlog/LangC
Bug#975667: marked as done (supercollider: FTBFS against boost_1.74)
Your message dated Wed, 16 Dec 2020 22:19:21 + with message-id and subject line Bug#975667: fixed in supercollider 1:3.11.2+repack-1 has caused the Debian Bug report #975667, regarding supercollider: FTBFS against boost_1.74 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.) -- 975667: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975667 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: supercollider Version: 3.10.4+repack-1 Severity: important Tags: ftbfs User: team+bo...@tracker.debian.org Usertags: boost174 -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer, it was discovered that your package failed to build against boost_1.74. Logs can be found here [1]. Most relevant part is probably this: [1/558] /usr/bin/c++ -DBOOST_CHRONO_HEADER_ONLY -DBOOST_NO_AUTO_PTR -DSC_DATA_DIR=\"/usr/share/SuperCollider\" -I../external_libraries/boost -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -O2 -g -DNDEBUG -fschedule-insns2 -fomit-frame-pointer -Wreturn-type -fno-math-errno -fno-signaling-nans -fsigned-zeros -fno-associative-math -pthread -fvisibility=hidden -std=gnu++11 -MD -MT external_libraries/CMakeFiles/oscpack.dir/oscpack_build.cpp.o -MF external_libraries/CMakeFiles/oscpack.dir/oscpack_build.cpp.o.d -o external_libraries/CMakeFiles/oscpack.dir/oscpack_build.cpp.o -c ../external_libraries/oscpack_build.cpp FAILED: external_libraries/CMakeFiles/oscpack.dir/oscpack_build.cpp.o /usr/bin/c++ -DBOOST_CHRONO_HEADER_ONLY -DBOOST_NO_AUTO_PTR -DSC_DATA_DIR=\"/usr/share/SuperCollider\" -I../external_libraries/boost -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -O2 -g -DNDEBUG -fschedule-insns2 -fomit-frame-pointer -Wreturn-type -fno-math-errno -fno-signaling-nans -fsigned-zeros -fno-associative-math -pthread -fvisibility=hidden -std=gnu++11 -MD -MT external_libraries/CMakeFiles/oscpack.dir/oscpack_build.cpp.o -MF external_libraries/CMakeFiles/oscpack.dir/oscpack_build.cpp.o.d -o external_libraries/CMakeFiles/oscpack.dir/oscpack_build.cpp.o -c ../external_libraries/oscpack_build.cpp ../external_libraries/oscpack_build.cpp:1:10: fatal error: boost/detail/endian.hpp: No such file or directory 1 | #include | ^~~~ Maybe just changing the header to can fix the problem. It is planned to push boost_1.74 as the default version in Debian/Bullseye. [1] http://qa-logs.debian.net/2020/10/27-boost/boost/supercollider_3.10.4+repack-1_unstable_boost.log Best regards Anton - -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.9.0-1-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEEu71F6oGKuG/2fnKF0+Fzg8+n/wYFAl+9csYRHGdsYWRrQGRl Ymlhbi5vcmcACgkQ0+Fzg8+n/waSWQ/5AY9zhiXLzXCjD888eklyx8u/jKeSw/v/ lfugfHHV+fI/k+XJzAsMvPoqxWrCjOaI9FH9o69LbRX7OgQ/hP9mKfoSeddmDg/k FHgVEEBzGLK/Jsfg6ANccWosGJYzxfww87xW1HzHTC4ruucXiuVE+qg+vr1rLS0p zmzB7BZ2xKkkv/LVjSYbXIV4aIpnTOvIlTmRO4ja8kVyFiu7Tt7pCxsmOEYxSBzI HhXiqb9epxuJVw1D0BfltrtDiIileyDEmrRIgFIXA0nO07CeIZAk9KjacTXJsA0c gRSOfgYWongNCLkwg7B9YwpL/sN8AArSunUnmQKxXxtTz2sKGZDDv8aGBprENzgZ vGF/voBVUV9y+WcX/Yo0DZhUGNv//mq9bi1rcEiYKuxlwNHWSZX0cOwHCmb/H5r+ xGvm871yjxYOb6Ot9yjzpWBM9GkhuJ7hkmq3vxVK8ZHm9/aGxHuZ2JrxXCPiicwC R0/W+WfmWUhGXnkDoYVOnh8pXVvF0x4uQVCd+vO+TfjxLKdgBu1/T7Erm+Hvrwyr IL/9eOI2D9IU7ao6yUnMEpEfP8CmaKZMFXPCz5pV/oGNb/B3OPZhnvriL6F0BWjq mu2LMPXKEh1Ly+Ikb2BOFUui5HVjs53S3uvq7wQp7iSAelFbrlL7JXUgVezTOIo9 8RpTbBQtwCc= =0Nwc -END PGP SIGNATURE- --- End Message --- --- Begin Message --- Source: supercollider Source-Version: 1:3.11.2+repack-1 Done: Dennis Braun We believe that the bug you reported is fixed in the latest version of supercollider, 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 975...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dennis Braun (supplier of updated supercollider pac
Bug#977282: marked as done (libroscpp-core-dev has a runtime dependency on runtime libraries without depending on these)
Your message dated Wed, 16 Dec 2020 22:19:01 +
with message-id
and subject line Bug#977282: fixed in ros-roscpp-core 0.7.2-5
has caused the Debian Bug report #977282,
regarding libroscpp-core-dev has a runtime dependency on runtime libraries
without depending on these
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.)
--
977282: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977282
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ros-roscpp-core
Version: 0.7.2-4
Severity: serious
Tags: sid bullseye
libroscpp-core-dev has a runtime dependency on runtime libraries without
depending on these. This is seen with the current boost transition.
$ cat /usr/lib/x86_64-linux-gnu/pkgconfig/cpp_common.pc
prefix=/usr
Name: cpp_common
Description: Description of cpp_common
Version: 0.7.2
Cflags: -I${prefix}/include
Libs: -lcpp_common /usr/lib/x86_64-linux-gnu/libboost_system.so.1.74.0
/usr/lib/x86_64-linux-gnu/libboost_thread.so.1.74.0
/usr/lib/x86_64-linux-gnu/libconsole_bridge.so.0.4
Requires:
$ cat /usr/lib/x86_64-linux-gnu/pkgconfig/rostime.pc
prefix=/usr
Name: rostime
Description: Description of rostime
Version: 0.7.2
Cflags: -I${prefix}/include
Libs: -lrostime /usr/lib/x86_64-linux-gnu/libboost_date_time.so.1.74.0
/usr/lib/x86_64-linux-gnu/libboost_system.so.1.74.0
/usr/lib/x86_64-linux-gnu/libboost_thread.so.1.74.0
Requires: cpp_common
If that is really needed, then libroscpp-core-dev should depend on these runtime
libraries, so that transitions have a chance to identify these dependencies.
Or use pkgconfig files like everybody else:
- -lboost_system -lboost_thread
- -lboost_date_time -lboost_system
I'm only filing this for ros-roscpp-core and ros-pluginlib, however the whole
ros stack should be checked for similar issues.
--- End Message ---
--- Begin Message ---
Source: ros-roscpp-core
Source-Version: 0.7.2-5
Done: Jochen Sprickerhof
We believe that the bug you reported is fixed in the latest version of
ros-roscpp-core, 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 977...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Jochen Sprickerhof (supplier of updated ros-roscpp-core
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sun, 13 Dec 2020 21:50:43 +0100
Source: ros-roscpp-core
Architecture: source
Version: 0.7.2-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers
Changed-By: Jochen Sprickerhof
Closes: 977282
Changes:
ros-roscpp-core (0.7.2-5) unstable; urgency=medium
.
* Minimize Boost dependency (Closes: #977282)
* bump policy version (no changes)
Checksums-Sha1:
9b576565dc7204ea55bdf0a8391916ee99a651b0 2314 ros-roscpp-core_0.7.2-5.dsc
7d39ee6e1d8d35ef152bd2ccfc51192ab407a5c6 4840
ros-roscpp-core_0.7.2-5.debian.tar.xz
12f7812eb4b1785b88d3dab23a12ce0217815f11 8064
ros-roscpp-core_0.7.2-5_source.buildinfo
Checksums-Sha256:
d6441f860c723bb6402ca00763396560b64a30755cc8317c6c7e68c778e24541 2314
ros-roscpp-core_0.7.2-5.dsc
a29bb05bf55d61392d91e5563af0f54b9a93d192164cd05c2ba1eed46c6a594e 4840
ros-roscpp-core_0.7.2-5.debian.tar.xz
7cf61e361e383b85f000d7fceb323a142673e454d5d691eaf0afab5e68ea6359 8064
ros-roscpp-core_0.7.2-5_source.buildinfo
Files:
a3270d3f2a6858a98d951f3689b6f660 2314 libs optional ros-roscpp-core_0.7.2-5.dsc
a9f313fe12007469a88994700eff8a9c 4840 libs optional
ros-roscpp-core_0.7.2-5.debian.tar.xz
eede159cf81cce36ada657456620492f 8064 libs optional
ros-roscpp-core_0.7.2-5_source.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEc7KZy9TurdzAF+h6W//cwljmlDMFAl/ahGMACgkQW//cwljm
lDO5UA//bxWo8RnMFAf3D/FR0knzTmC45IfTIoPPvj5CpaFFLpuHNDM++SDTC2IE
MB4M/iWgOgFM0Mtta+yQjpLJ1liVLSXmFdoPstwly4d9LsvQ0ITQtIca1qq1sNjB
m7MdSB5J6hMMBpT28Z6Bpq7kNbHaOCwzkMdRFaQcpH7Cgspar9/6zd9V2ywH4F7t
4WhnGSymCuQkIcQzJbFD69jI7qMMzviU+4Qv9FNPdsp0kJnaJQdb8V/Ufj87v+ly
pKgtx/q42R2OBUx/RA1Lxz9jfME+081iy6/p7IdihRamKo/Dokq8Amm2/rWMAB68
r4UNR6G1/aAtOUgkzUZeGeAVse5HVBK3JeW5r+/TfmTCzxkPkEvnCt6N0KFFG/UH
8Ysh4s+nN96LFOg5/fHblMeskGPDw2vtQsCqBmKOUfKm+hixmm2zYxBROJIr8EiA
SlnrJcTqAphNZ3X9aIW2fYt4wR9WMSE+503a6xhYgOaAfxx6ZEtmsiQu3dgAi5CM
8nFMEE3
Bug#975167: marked as done (supercollider: FTBFS: ../QtCollider/primitives/prim_QPen.cpp:37:21: error: aggregate ‘QPainterPath path’ has incomplete type and cannot be defined)
Your message dated Wed, 16 Dec 2020 22:19:21 + with message-id and subject line Bug#975167: fixed in supercollider 1:3.11.2+repack-1 has caused the Debian Bug report #975167, regarding supercollider: FTBFS: ../QtCollider/primitives/prim_QPen.cpp:37:21: error: aggregate ‘QPainterPath path’ has incomplete type and cannot be defined to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 975167: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975167 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: supercollider Version: 1:3.10.4+repack-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201119 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /usr/bin/c++ -DBOOST_CHRONO_HEADER_ONLY -DBOOST_NO_AUTO_PTR > -DBUILDING_SCSYNTH -DHAVE_ALSA=1 -DHAVE_AVAHI=1 -DHAVE_HIDAPI -DHAVE_LID > -DHAVE_READLINE -DNOVA_SIMD -DQT_COLLIDER_EXPORTING -DQT_CORE_LIB > -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_NO_DEBUG -DQT_NO_KEYWORDS -DQT_OPENGL_LIB > -DQT_POSITIONING_LIB -DQT_PRINTSUPPORT_LIB -DQT_QMLMODELS_LIB -DQT_QML_LIB > -DQT_QUICK_LIB -DQT_SQL_LIB -DQT_SVG_LIB -DQT_WEBCHANNEL_LIB > -DQT_WEBENGINECORE_LIB -DQT_WEBENGINEWIDGETS_LIB -DQT_WIDGETS_LIB > -DSC_DATA_DIR=\"/usr/share/SuperCollider\" -DSC_HIDAPI -DSC_IDE > -DSC_MEMORY_ALIGNMENT=32 -DSC_PLUGIN_DIR=\"/usr/lib/SuperCollider/plugins\" > -DSC_QT -DSC_USE_QTWEBENGINE -DUSE_RENDEZVOUS=1 -DYYSTACK_USE_ALLOC -Icommon > -I../include/common -I../include/lang -I../include/plugin_interface > -I../include/server -I../common -I../external_libraries/boost_sync/include > -I../lang/LangSource -I../lang/LangPrimSource -I../external_libraries/nova-tt > -I../lang/LangSource/Bison -I../external_libraries/hidapi/hidapi > -I../external_libraries/hidapi/hidapi_parser -I../QtCollider > -I../lang/X11_INCLUDE_DIR -I../SCDoc -I../external_libraries/TLSF-2.4.6/src > -I../external_libraries/yaml-cpp/include -I../external_libraries/boost > -isystem /usr/include/x86_64-linux-gnu/qt5 -isystem > /usr/include/x86_64-linux-gnu/qt5/QtCore -isystem > /usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -isystem > /usr/include/x86_64-linux-gnu/qt5/QtGui -isystem > /usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem > /usr/include/x86_64-linux-gnu/qt5/QtNetwork -isystem > /usr/include/x86_64-linux-gnu/qt5/QtPrintSupport -isystem > /usr/include/x86_64-linux-gnu/qt5/QtQuick -isystem > /usr/include/x86_64-linux-gnu/qt5/QtQmlModels -isystem > /usr/include/x86_64-linux-gnu/qt5/QtQml -isystem > /usr/include/x86_64-linux-gnu/qt5/QtSql -isystem > /usr/include/x86_64-linux-gnu/qt5/QtOpenGL -isystem > /usr/include/x86_64-linux-gnu/qt5/QtSvg -isystem > /usr/include/x86_64-linux-gnu/qt5/QtWebEngineCore -isystem > /usr/include/x86_64-linux-gnu/qt5/QtWebChannel -isystem > /usr/include/x86_64-linux-gnu/qt5/QtPositioning -isystem > /usr/include/x86_64-linux-gnu/qt5/QtWebEngineWidgets -g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -O2 -g -DNDEBUG > -fschedule-insns2 -fomit-frame-pointer -Wreturn-type -fno-math-errno > -fno-signaling-nans -fsigned-zeros -fno-associative-math -pthread > -fvisibility=hidden -fPIC -std=gnu++11 -MD -MT > lang/CMakeFiles/libsclang.dir/__/QtCollider/primitives/prim_QPen.cpp.o -MF > lang/CMakeFiles/libsclang.dir/__/QtCollider/primitives/prim_QPen.cpp.o.d -o > lang/CMakeFiles/libsclang.dir/__/QtCollider/primitives/prim_QPen.cpp.o -c > ../QtCollider/primitives/prim_QPen.cpp > ../QtCollider/primitives/prim_QPen.cpp:37:21: error: aggregate ‘QPainterPath > path’ has incomplete type and cannot be defined >37 | static QPainterPath path; > | ^~~~ > ../QtCollider/primitives/prim_QPen.cpp: In function ‘bool > QtCollider::beginPainting(QPainter*, QObject*)’: > ../QtCollider/primitives/prim_QPen.cpp:61:25: error: invalid use of > incomplete type ‘class QPainterPath’ >61 | path = QPainterPath(); > | ^ > In file included from /usr/include/x86_64-linux-gnu/qt5/QtGui/qtransform.h:43, > from /usr/include/x86_64-linux-gnu/qt5/QtGui/qimage.h:48, > from /usr/include/x86_64-linux-gnu/qt5/QtGui/QImage:1, > from ../QtCollider/primitives/../image.h:24, > from ../QtCollider/primitives/prim_QPen.cpp:25: > /usr/include/x86_64-linux-gnu/qt5/QtGui/qmatrix.h:54:7: note: forward > declaration of ‘class QPainterPath’ >54 | class QPai
Bug#977185: Can be switched to default
I have checked and your package can easily be switched to the unversioned dev-package. Regards Anton
Bug#975660: marked as done (scram: FTBFS against boost_1.74)
Your message dated Wed, 16 Dec 2020 23:00:26 +0100 with message-id and subject line Close has caused the Debian Bug report #975660, regarding scram: FTBFS against boost_1.74 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.) -- 975660: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975660 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: scram Version: 0.16.2-1 Severity: important Tags: ftbfs User: team+bo...@tracker.debian.org Usertags: boost174 -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer, it was discovered that your package failed to build against boost_1.74. Logs can be found here [1]. Most relevant part is probably this: [ 19%] Building CXX object src/CMakeFiles/scram.dir/config.cc.o cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/c++ -DBOOST_ALL_NO_LIB -DBOOST_FILESYSTEM_DYN_LINK -DBOOST_PROGRAM_OPTIONS_DYN_LINK -DBOOST_RANDOM_DYN_LINK -DBOOST_SYSTEM_DYN_LINK -DPROJECT_SOURCE_DIR=\"/<>\" -Dscram_EXPORTS -I/<>/obj-x86_64-linux-gnu/src -I/<>/src -I/<> -isystem /usr/include/libxml2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fno-new-ttp-matching -O3 -DNDEBUG -fPIC -std=c++17 -o CMakeFiles/scram.dir/config.cc.o -c /<>/src/config.cc In file included from /<>/src/settings.cc:27: /<>/src/settings.cc: In member function ‘scram::core::Settings& scram::core::Settings::algorithm(std::string_view)’: /<>/src/error.h:39:40: error: ‘BOOST_THROW_EXCEPTION_CURRENT_FUNCTION’ was not declared in this scope 39 | throw err << ::boost::throw_function(BOOST_THROW_EXCEPTION_CURRENT_FUNCTION) \ It is planned to push boost_1.74 as the default version in Debian/Bullseye. [1] http://qa-logs.debian.net/2020/10/27-boost/boost/scram_0.16.2-1_unstable_boost.log Best regards Anton - -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.9.0-1-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEEu71F6oGKuG/2fnKF0+Fzg8+n/wYFAl+9Y0wRHGdsYWRrQGRl Ymlhbi5vcmcACgkQ0+Fzg8+n/wZ/vQ/+I16O0GIcjOiVDon3vjDctFUItgC3ynuq ceER0Hu6uHZxn3SWUzhQqCc4cVVp3wTXIELn6iYc3Ekv2H2ZgZYKP9sF6F5u6Ue3 7PxElbjUBZz/SQjMNyRALWZY/ZSFqlLr6iCZ9YIYA9Di/bE8y6gBNMdmczWG32yy umvpDH3sVd1S0ORLzvuCANfrQb6YZO5SFZYlE6zvqaIdXqbTICGLyx4QLMYIDE8e 07TcTPz61htFCfz55M6KUAtgO0ihPS0dCu19rp+8Gpf2n2PIZbytvtFWGZZPlAxy Bz9aY4PFqJKFs454hLb6SXNuF59QhNOCCg97+jxmqIy3OqyrEnQqv5RvwkgDoxsq 2rjbUGZMnWaUyb5tJuc3WKBUBvmIYcg0ciZYKDNwAhy2ECBRZvRRKXWT29tHS8Z3 3A37OcIbwx/Nre1x6ayyS8T5j3iHnTq5s4t7CwqOJWRHovyFWRTU7vCf51dDBTe6 8vxhrRzCv2UFfeDIOFnN6zNFGm+n+q5wWj/YVUHGGzUSbGa82+v7iQL3/+iI9pdP 1CYmueriQAuyiqsktxCASiYCuj+vbHgmTklWfnzeRdpEg3lE14A2sC7sHH8/KAYt kuGW2JO+lZAuZKUB5ZLVEc4uumdL+XzpqcprrpJZNDgeS6nrdKWJE7IMNFddReAK JrxPYAPm+fo= =H+2c -END PGP SIGNATURE- --- End Message --- --- Begin Message --- fixed 975660 0.16.2-2 thanks--- End Message ---
Processed: Close
Processing commands for cont...@bugs.debian.org: > fixed 975660 0.16.2-2 Bug #975660 [scram] scram: FTBFS against boost_1.74 There is no source info for the package 'scram' at version '0.16.2-2' with architecture '' Unable to make a source version for version '0.16.2-2' Marked as fixed in versions 0.16.2-2. > thanks Stopping processing here. Please contact me if you need assistance. -- 975660: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975660 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reopen
Processing commands for cont...@bugs.debian.org:
> reopen 977449
Bug #977449 {Done: Anton Gladky } [slic3r] slic3r: FTBFS with
boost 1.74
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions scram/0.16.2-2.
> notfixed 977449 0.16.2-2
Bug #977449 [slic3r] slic3r: FTBFS with boost 1.74
There is no source info for the package 'slic3r' at version '0.16.2-2' with
architecture ''
Unable to make a source version for version '0.16.2-2'
Ignoring request to alter fixed versions of bug #977449 to the same values
previously set
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
977449: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977449
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#977449: marked as done (slic3r: FTBFS with boost 1.74)
Your message dated Wed, 16 Dec 2020 21:49:55 + with message-id and subject line Bug#977449: fixed in scram 0.16.2-2 has caused the Debian Bug report #977449, regarding slic3r: FTBFS with boost 1.74 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.) -- 977449: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977449 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: slic3r Version: 1.3.0+dfsg1-3.1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org slic3r fails to build with boost 1.74: | g++ -I/usr/lib/x86_64-linux-gnu/perl/5.32/CORE -fPIC -xc++ -Isrc/libslic3r -D_GLIBCXX_USE_C99 -DHAS_BOOL -DNOGDI -DSLIC3RXS -DBOOST_ASIO_DISABLE_KQUEUE -Dexprtk_disable_rtl_io_file -Dexprtk_disable_return_statement -Dexprtk_disable_rtl_vecops -Dexprtk_disable_string_capabilities -Dexprtk_disable_enhanced_features -U__STRICT_ANSI__ -std=c++11 -DBOOST_LIBS -DNDEBUG -O -Wno-undefined-var-template -Isrc -Ibuildtmp -c -D_REENTRANT -D_GNU_SOURCE -DDEBIAN -fwrapv -fno-strict-aliasing -pipe -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -o src/libslic3r/PrintObject.o src/libslic3r/PrintObject.cpp | In file included from src/libslic3r/TriangleMesh.hpp:5, | from src/libslic3r/Model.hpp:9, | from src/libslic3r/Print.hpp:14, | from src/libslic3r/PrintObject.cpp:1: | src/admesh/stl.h:29:10: fatal error: boost/detail/endian.hpp: No such file or directory |29 | #include | | ^ | compilation terminated. See https://buildd.debian.org/status/fetch.php?pkg=slic3r&arch=amd64&ver=1.3.0%2Bdfsg1-3.1%2Bb2&stamp=1607967787&raw=0 Cheers -- Sebastian Ramacher signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: scram Source-Version: 0.16.2-2 Done: Anton Gladky We believe that the bug you reported is fixed in the latest version of scram, 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 977...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Anton Gladky (supplier of updated scram 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, 16 Dec 2020 22:34:36 +0100 Source: scram Architecture: source Version: 0.16.2-2 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Anton Gladky Closes: 977449 Changes: scram (0.16.2-2) unstable; urgency=medium . * Team upload. * [bb08829] Add .gitlab-ci.yml * [bdd4875] Fix compilation against boost_1.74. (Closes: #977449) * [9f0eef0] Use secure copyright file specification URI. * [c9e5bdf] Bump debhelper from old 10 to 12. + debian/rules: Rely on default use of dh_missing rather thanusing dh_install --list-missing. * [3c115ed] Set debhelper-compat version in Build-Depends. * [5832136] Set upstream metadata fields: Bug-Database, Bug-Submit, Repository, Repository-Browse. * [41fc902] Set Standards-Version 4.5.1. No changes * [15dc93c] Allow blhc to fail Checksums-Sha1: ae461bcbb3e108dd023a0741d406c41e5a1150df 2158 scram_0.16.2-2.dsc e1fd174aa17aa500089e10f31c98eea02aa40206 5316 scram_0.16.2-2.debian.tar.xz c087adcd9546b4d5b1099f363d191af8bbaa480d 10814 scram_0.16.2-2_source.buildinfo Checksums-Sha256: e93aa6b135941bd1737b8af91b5899758cd22c067388a63f227d74946ce0f96c 2158 scram_0.16.2-2.dsc b1421ceeebbabf644bdb00444eca8e63878a64d16ecb9ad3b02f94a525ddbbaf 5316 scram_0.16.2-2.debian.tar.xz 8c3f0f28036a23155604c4cd5c9a53498ee72f1381877b89d7a4ca97fbb5f871 10814 scram_0.16.2-2_source.buildinfo Files: fbf4bdfd130aabcbfef339e93fdfd694 2158 science optional scram_0.16.2-2.dsc baa0f234c00b05f487124ffbae45228f 5316 science optional scram_0.16.2-2.debian.tar.xz 94e6f63a20fbbd16b2b14a25035f7972 10814 science optional scram_0.16.2
Processed: Re: Bug#976909: h2o: FTBFS on ppc64el: ld: /usr/lib/gcc/powerpc64le-linux-gnu/10/../../../powerpc64le-linux-gnu/Scrt1.o:(.data.rel.ro.local+0x8): undefined reference to `main'
Processing commands for cont...@bugs.debian.org: > severity 976909 normal Bug #976909 [src:h2o] h2o: FTBFS on ppc64el: ld: /usr/lib/gcc/powerpc64le-linux-gnu/10/../../../powerpc64le-linux-gnu/Scrt1.o:(.data.rel.ro.local+0x8): undefined reference to `main' Severity set to 'normal' from 'serious' > tags 976909 +moreinfo Bug #976909 [src:h2o] h2o: FTBFS on ppc64el: ld: /usr/lib/gcc/powerpc64le-linux-gnu/10/../../../powerpc64le-linux-gnu/Scrt1.o:(.data.rel.ro.local+0x8): undefined reference to `main' Added tag(s) moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 976909: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976909 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#976909: h2o: FTBFS on ppc64el: ld: /usr/lib/gcc/powerpc64le-linux-gnu/10/../../../powerpc64le-linux-gnu/Scrt1.o:(.data.rel.ro.local+0x8): undefined reference to `main'
severity 976909 normal tags 976909 +moreinfo thanks Hi Lucas, thanks for filing the bug. But I cannot reproduce this failure and it looks like the last upload of the package h2o into the archive was successfully built of ppc64el [1]. Could you please check your setup and provide more information? [1] https://buildd.debian.org/status/fetch.php?pkg=h2o&arch=ppc64el&ver=2.2.5%2Bdfsg2-6&stamp=1608152493&raw=0 Regards Anton Am Mi., 9. Dez. 2020 um 10:09 Uhr schrieb Lucas Nussbaum : > > Source: h2o > Version: 2.2.5+dfsg2-5 > Severity: serious > Justification: FTBFS on ppc64el > Tags: bullseye sid ftbfs > Usertags: ftbfs-20201209 ftbfs-bullseye ftbfs-ppc64el
Bug#975771: marked as done (fbxkb: FTBFS: fbxkb.c:17:10: fatal error: gtk/gtk.h: No such file or directory)
Your message dated Wed, 16 Dec 2020 21:34:11 + with message-id and subject line Bug#975771: fixed in fbxkb 0.6-2.1 has caused the Debian Bug report #975771, regarding fbxkb: FTBFS: fbxkb.c:17:10: fatal error: gtk/gtk.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.) -- 975771: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975771 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: fbxkb Version: 0.6-2 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201125 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > gcc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wall -g -DG_DISABLE_DEPRECATED > -DGDK_DISABLE_DEPRECATED -DGTK_DISABLE_DEPRECATED -c fbxkb.c > fbxkb.c:17:10: fatal error: gtk/gtk.h: No such file or directory >17 | #include > | ^~~ > compilation terminated. > make[1]: *** [Makefile.common:35: fbxkb.o] Error 1 The full build log is available from: http://qa-logs.debian.net/2020/11/25/fbxkb_0.6-2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Source: fbxkb Source-Version: 0.6-2.1 Done: Sudip Mukherjee We believe that the bug you reported is fixed in the latest version of fbxkb, 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 975...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sudip Mukherjee (supplier of updated fbxkb package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 14 Dec 2020 20:31:49 + Source: fbxkb Architecture: source Version: 0.6-2.1 Distribution: unstable Urgency: medium Maintainer: Dmitry Borisyuk Changed-By: Sudip Mukherjee Closes: 975673 975771 Changes: fbxkb (0.6-2.1) unstable; urgency=medium . * Non-maintainer upload. * Add dependency on libgdk-pixbuf-xlib-2.0-dev. (Closes: #975673) - The dependency also fixes FTBFS with gtk/gtk.h. (Closes: #975771) Checksums-Sha1: 67684290d8170548c5d5ea1017b87517611bf168 1719 fbxkb_0.6-2.1.dsc 15d5374b1914c3817493c4c0a93ae4932578c391 6612 fbxkb_0.6-2.1.debian.tar.xz fece69e16a80c44ece63e3f46e60941322ad25eb 11264 fbxkb_0.6-2.1_amd64.buildinfo Checksums-Sha256: 5ebeea2e2f49a0c65a5265f98daf03487e6acd3d50441bbed956fcb3dd77f135 1719 fbxkb_0.6-2.1.dsc 018dd5694ce33cd31a31dc1906ad54996540bdae13b73cc02c10769e7e3ad70b 6612 fbxkb_0.6-2.1.debian.tar.xz ce24ddb801bb2433e9e4746fa1484bf35b98c313d1f241ec43b89a8079b9a3e6 11264 fbxkb_0.6-2.1_amd64.buildinfo Files: 1112ab3c0a2ebb6ca1ac2b8f8c42ac1b 1719 x11 optional fbxkb_0.6-2.1.dsc 55b0267deaeb4893cd53e5db56e84194 6612 x11 optional fbxkb_0.6-2.1.debian.tar.xz a1dfd52c382a4b24a49461d7e669c04c 11264 x11 optional fbxkb_0.6-2.1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEuDQJkCg9jZvBlJrHR5mjUUbRKzUFAl/X0qsACgkQR5mjUUbR KzV9Zw/9HADtWRYOo0FcZ1zI/+GLWzJULPjf9/Va0PkftxWq23OWTu5t7HjiXh6F 0td1yhFuwVE+slDgP9W8Xb/bIwALfIl5Q5TyFLNRCR6EFLRO0Bu4zGLVI6niceNu PwwmazrhWyPJ3Td1IDjspRLbyYqO5KIaZVY3AcYlc6o42mOaQf77p53ImaZ+EWvK ysTpgHHPRUn3tZtwMfamiIj/wB5yScnuLAFtqxTE4c/E3aQagtY/5Bh3tiZfLR+s /vmQ6Pb1m0Rq777v56PdTcyN5KtSih76XGm4jK/EOopn4aPNzNiChhNU+5bkHGQZ 0/KOV9kfSAI7+edVEogib/BZRdYpZ8yEs668y+lasPmOT/IWCVilqUTZ2ZqxEVmt yDQ0TfxiO9l48X7SolAfWpseWzfqaJOgS3WoUkA1u6H+MWOj6vNmqAaqM0fqOSQo QMyAIGxRRKeHWsKAOnMmaO30XNrHXko7v/MQQ9CJYUjkbzrvdTtWZN9QG+P+M6aP W5b0t2DkC5V1kEK1O/uHGeR6HUrrfikLO2/TEtzCRDjcJZ9Fqpia3PYYgqXsIEgn 8pe+5k6hIFAyxc0FIgucMExjWxssnZbzSDAv0+G/lB7dY4YkljOgpeyQNTP6r8MY vvm+Ll71OIJ/GbxgG1H4iylTMOPVFrrVJNfMkMpXv2ct4Iq7bFQ= =I8R6 -END PGP SIGNATURE End Message ---
Bug#975673: marked as done (fbxkb: requires gdk-pixbuf-xlib-2.0.pc but does not build-depend on a package containing it)
Your message dated Wed, 16 Dec 2020 21:34:11 + with message-id and subject line Bug#975673: fixed in fbxkb 0.6-2.1 has caused the Debian Bug report #975673, regarding fbxkb: requires gdk-pixbuf-xlib-2.0.pc but does not build-depend on a package containing it 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.) -- 975673: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975673 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: fbxkb Version: 0.6-2 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) To reproduce: build fbxkb on a release architecture in unstable (I used amd64). > make[1]: Entering directory '/<>' > Package gdk-pixbuf-xlib-2.0 was not found in the pkg-config search path. > Perhaps you should add the directory containing `gdk-pixbuf-xlib-2.0.pc' > to the PKG_CONFIG_PATH environment variable > No package 'gdk-pixbuf-xlib-2.0' found This is because the deprecated gdk-pixbuf-xlib-2.0 module used to be pulled in as an indirect dependency by GTK 2. However, GTK 2 doesn't actually use that module, and as a result libgtk2.0-dev no longer depends on it, causing fbxkb to fail to build. In the short term, please build-depend on either libgdk-pixbuf-xlib-2.0-dev | libgdk-pixbuf2.0-dev if you want backports to older Debian to be possible, or libgdk-pixbuf-xlib-2.0-dev if not. That's enough to close this bug. (This might also be a good opportunity to check that all the other packages required at build time are in the Build-Depends.) For the longer term, the upstream maintainers of gdk-pixbuf have deprecated the gdk-pixbuf-xlib-2.0 module[0] and do not intend to maintain it further, so it would be better if fbxkb can stop using it. Thanks, smcv [0] https://gitlab.gnome.org/Archive/gdk-pixbuf-xlib --- End Message --- --- Begin Message --- Source: fbxkb Source-Version: 0.6-2.1 Done: Sudip Mukherjee We believe that the bug you reported is fixed in the latest version of fbxkb, 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 975...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sudip Mukherjee (supplier of updated fbxkb package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 14 Dec 2020 20:31:49 + Source: fbxkb Architecture: source Version: 0.6-2.1 Distribution: unstable Urgency: medium Maintainer: Dmitry Borisyuk Changed-By: Sudip Mukherjee Closes: 975673 975771 Changes: fbxkb (0.6-2.1) unstable; urgency=medium . * Non-maintainer upload. * Add dependency on libgdk-pixbuf-xlib-2.0-dev. (Closes: #975673) - The dependency also fixes FTBFS with gtk/gtk.h. (Closes: #975771) Checksums-Sha1: 67684290d8170548c5d5ea1017b87517611bf168 1719 fbxkb_0.6-2.1.dsc 15d5374b1914c3817493c4c0a93ae4932578c391 6612 fbxkb_0.6-2.1.debian.tar.xz fece69e16a80c44ece63e3f46e60941322ad25eb 11264 fbxkb_0.6-2.1_amd64.buildinfo Checksums-Sha256: 5ebeea2e2f49a0c65a5265f98daf03487e6acd3d50441bbed956fcb3dd77f135 1719 fbxkb_0.6-2.1.dsc 018dd5694ce33cd31a31dc1906ad54996540bdae13b73cc02c10769e7e3ad70b 6612 fbxkb_0.6-2.1.debian.tar.xz ce24ddb801bb2433e9e4746fa1484bf35b98c313d1f241ec43b89a8079b9a3e6 11264 fbxkb_0.6-2.1_amd64.buildinfo Files: 1112ab3c0a2ebb6ca1ac2b8f8c42ac1b 1719 x11 optional fbxkb_0.6-2.1.dsc 55b0267deaeb4893cd53e5db56e84194 6612 x11 optional fbxkb_0.6-2.1.debian.tar.xz a1dfd52c382a4b24a49461d7e669c04c 11264 x11 optional fbxkb_0.6-2.1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEuDQJkCg9jZvBlJrHR5mjUUbRKzUFAl/X0qsACgkQR5mjUUbR KzV9Zw/9HADtWRYOo0FcZ1zI/+GLWzJULPjf9/Va0PkftxWq23OWTu5t7HjiXh6F 0td1yhFuwVE+slDgP9W8Xb/bIwALfIl5Q5TyFLNRCR6EFLRO0Bu4zGLVI6niceNu PwwmazrhWyPJ3Td1IDjspRLbyYqO5KIaZVY3AcYlc6o42mOaQf77p53ImaZ+EWvK ysTpgHHPRUn3tZtwMfamiIj/wB5yScnuLAFtqxTE4c/E3aQagtY/5Bh3tiZfLR+s /vmQ6Pb1m0Rq777v56PdTcyN5KtSih76XGm4jK/EOopn4aPNzNiChhNU+5bkHGQZ 0/KOV9kfSAI7+edVEogib/BZRdYpZ8yEs668y+lasPmOT/IWCVilqUTZ2ZqxEVmt yDQ0TfxiO9l48X7SolAfWpseWzfqaJOgS3WoUkA1u6H+MWOj6vNmqAaqM0fqOSQo QMyAIGxRRKeHWsKAOnMmaO30XNrHXko7v/MQQ9CJYUjkbzrvdTtWZN9QG+P+M6aP W5b0t2DkC5V1kEK1O/uHGeR6HUrrfikLO2/TEtzCRDjcJZ9Fqpi
Processed: severity of 975590 is serious
Processing commands for cont...@bugs.debian.org:
> # boost 1.74 is the default in unstable
> severity 975590 serious
Bug #975590 {Done: Chris Hofstaedtler } [pdns] pdns: FTBFS
against boost_1.74
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
975590: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975590
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#977568: xml-security-c: FTBFS with Xalan 1.12
Source: xml-security-c
Severity: serious
Tags: patch upstream
Hi,
xalan-c 1.12 is currently in experimental and contains some changes that
cause xml-security-c to FTBFS.
The attached quilt patch contains the necessary updates and allows for
compilation with either 1.11 and 1.12.
Best regards,
Bill
Description: Update for Xalan 1.12
Author: Bill Blough
Forwarded: no
Last-Update: 2020-12-16
---
This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
--- a/xsec/dsig/DSIGXPathHere.cpp
+++ b/xsec/dsig/DSIGXPathHere.cpp
@@ -30,7 +30,7 @@
#ifdef XSEC_HAVE_XPATH
-XALAN_USING_XALAN(XalanCopyConstruct);
+using xalanc::XalanCopyConstruct;
DSIGXPathHere::DSIGXPathHere() {
--- a/xsec/dsig/DSIGXPathHere.hpp
+++ b/xsec/dsig/DSIGXPathHere.hpp
@@ -56,12 +56,12 @@
// Namespace usage
-XALAN_USING_XALAN(Function);
-XALAN_USING_XALAN(XalanNode);
-XALAN_USING_XALAN(XPathExecutionContext);
-XALAN_USING_XALAN(XalanDOMString);
-XALAN_USING_XALAN(XObjectPtr);
-XALAN_USING_XALAN(MemoryManagerType);
+using xalanc::Function;
+using xalanc::XalanNode;
+using xalanc::XPathExecutionContext;
+using xalanc::XalanDOMString;
+using xalanc::XObjectPtr;
+using xalanc::MemoryManagerType;
XSEC_USING_XERCES(Locator);
--- a/xsec/samples/simpleDecrypt.cpp
+++ b/xsec/samples/simpleDecrypt.cpp
@@ -54,7 +54,7 @@
#ifdef XSEC_HAVE_XALAN
#include
-XALAN_USING_XALAN(XalanTransformer)
+using xalanc::XalanTransformer;
#endif
// OpenSSL
--- a/xsec/samples/simpleEncrypt.cpp
+++ b/xsec/samples/simpleEncrypt.cpp
@@ -48,7 +48,7 @@
#ifdef XSEC_HAVE_XALAN
#include
-XALAN_USING_XALAN(XalanTransformer)
+using xalanc::XalanTransformer;
#endif
XERCES_CPP_NAMESPACE_USE
--- a/xsec/samples/simpleHMAC.cpp
+++ b/xsec/samples/simpleHMAC.cpp
@@ -49,7 +49,7 @@
#ifdef XSEC_HAVE_XALAN
#include
-XALAN_USING_XALAN(XalanTransformer)
+using xalanc::XalanTransformer;
#endif
XERCES_CPP_NAMESPACE_USE
--- a/xsec/samples/simpleValidate.cpp
+++ b/xsec/samples/simpleValidate.cpp
@@ -52,7 +52,7 @@ XERCES_CPP_NAMESPACE_USE
#ifdef XSEC_HAVE_XALAN
#include
-XALAN_USING_XALAN(XalanTransformer)
+using xalanc::XalanTransformer;
#endif
char docToValidate [4096] = "\
--- a/xsec/tools/checksig/checksig.cpp
+++ b/xsec/tools/checksig/checksig.cpp
@@ -83,8 +83,8 @@ using std::endl;
#include
#include
-XALAN_USING_XALAN(XPathEvaluator)
-XALAN_USING_XALAN(XalanTransformer)
+using xalanc::XPathEvaluator;
+using xalanc::XalanTransformer;
#endif
--- a/xsec/tools/cipher/cipher.cpp
+++ b/xsec/tools/cipher/cipher.cpp
@@ -93,8 +93,8 @@ using std::ostream;
#include
#include
-XALAN_USING_XALAN(XPathEvaluator)
-XALAN_USING_XALAN(XalanTransformer)
+using xalanc::XPathEvaluator;
+using xalanc::XalanTransformer;
#endif
--- a/xsec/tools/siginf/siginf.cpp
+++ b/xsec/tools/siginf/siginf.cpp
@@ -86,8 +86,8 @@ using std::ostream;
#include
#include
-XALAN_USING_XALAN(XPathEvaluator)
-XALAN_USING_XALAN(XalanTransformer)
+using xalanc::XPathEvaluator;
+using xalanc::XalanTransformer;
#else
--- a/xsec/tools/templatesign/templatesign.cpp
+++ b/xsec/tools/templatesign/templatesign.cpp
@@ -95,8 +95,8 @@
#include
#include
-XALAN_USING_XALAN(XPathEvaluator)
-XALAN_USING_XALAN(XalanTransformer)
+using xalanc::XPathEvaluator;
+using xalanc::XalanTransformer;
#endif
--- a/xsec/tools/txfmout/txfmout.cpp
+++ b/xsec/tools/txfmout/txfmout.cpp
@@ -84,8 +84,8 @@ using std::ofstream;
#include
#include
-XALAN_USING_XALAN(XPathEvaluator)
-XALAN_USING_XALAN(XalanTransformer)
+using xalanc::XPathEvaluator;
+using xalanc::XalanTransformer;
#else
--- a/xsec/tools/xklient/xklient.cpp
+++ b/xsec/tools/xklient/xklient.cpp
@@ -122,8 +122,8 @@ using std::ostream;
#include
#include
-XALAN_USING_XALAN(XPathEvaluator)
-XALAN_USING_XALAN(XalanTransformer)
+using xalanc::XPathEvaluator;
+using xalanc::XalanTransformer;
#endif
--- a/xsec/tools/xtest/xtest.cpp
+++ b/xsec/tools/xtest/xtest.cpp
@@ -63,8 +63,8 @@
#include
#include
-XALAN_USING_XALAN(XPathEvaluator)
-XALAN_USING_XALAN(XalanTransformer)
+using xalanc::XPathEvaluator;
+using xalanc::XalanTransformer;
#endif
--- a/xsec/transformers/TXFMXPath.cpp
+++ b/xsec/transformers/TXFMXPath.cpp
@@ -48,25 +48,25 @@
#endif
// Xalan namespace usage
-XALAN_USING_XALAN(XPathProcessorImpl)
-XALAN_USING_XALAN(XercesDOMSupport)
-XALAN_USING_XALAN(XercesParserLiaison)
-XALAN_USING_XALAN(XercesDocumentWrapper)
-XALAN_USING_XALAN(XercesWrapperNavigator)
-XALAN_USING_XALAN(XPathEvaluator)
-XALAN_USING_XALAN(XPathFactoryDefault)
-XALAN_USING_XALAN(XPathConstructionContextDefault)
-XALAN_USING_XALAN(XalanDocument)
-XALAN_USING_XALAN(XalanNode)
-XALAN_USING_XALAN(XalanDOMChar)
-XALAN_USING_XALAN(XPathEnvSupportDefault)
-XALAN_USING_XALAN(XObjectFactoryDefault)
-XALAN_USING_XALAN(XPathExecutionContextDefault)
-XALAN_USING_XALAN(ElementPrefixResolverProxy)
-XALAN_USING_XALAN(XPath)
-XALAN_USING_XALAN(NodeRefListBase)
-XALAN_USING_XALAN(XSLTResultTarget)
-XALAN_USING_XALAN(XSLE
Bug#977461: marked as done (gcc-1[01]-offload-amdgcn,gcc-1[01]-hppa64-linux-gnu: shipping unversioned binaries causes file conflicts)
Your message dated Wed, 16 Dec 2020 20:48:46 + with message-id and subject line Bug#977461: fixed in gcc-11 11-20201216-2 has caused the Debian Bug report #977461, regarding gcc-1[01]-offload-amdgcn,gcc-1[01]-hppa64-linux-gnu: shipping unversioned binaries causes file conflicts 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.) -- 977461: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977461 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gcc-10-offload-amdgcn,gcc-11-offload-amdgcn,gcc-10-hppa64-linux-gnu,gcc-11-hppa64-linux-gnu Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: found -1 10.2.1-1 Control: found -1 11-20201208-1 Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fails because it tries to overwrite other packages files. >From the attached log (scroll to the bottom...): Preparing to unpack .../gcc-11-offload-amdgcn_11-20201208-1_amd64.deb ... Unpacking gcc-11-offload-amdgcn (11-20201208-1) ... dpkg: error processing archive /var/cache/apt/archives/gcc-11-offload-amdgcn_11-20201208-1_amd64.deb (--unpack): trying to overwrite '/usr/amdgcn-amdhsa/bin/ar', which is also in package gcc-10-offload-amdgcn 10.2.1-1 Errors were encountered while processing: /var/cache/apt/archives/gcc-11-offload-amdgcn_11-20201208-1_amd64.deb These unversioned files are in conflict between the gcc versions: usr/amdgcn-amdhsa/bin/ar usr/amdgcn-amdhsa/bin/as usr/amdgcn-amdhsa/bin/ld usr/amdgcn-amdhsa/bin/nm usr/amdgcn-amdhsa/bin/ranlib usr/bin/hppa64-linux-gnu-lto-dump Maybe the unversioned binaries should be managed by unversioned packages from gcc-defaults instead. cheers, Andreas gcc-10-offload-amdgcn=10.2.1-1_gcc-11-offload-amdgcn=11-20201208-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: gcc-11 Source-Version: 11-20201216-2 Done: Matthias Klose We believe that the bug you reported is fixed in the latest version of gcc-11, 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 977...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthias Klose (supplier of updated gcc-11 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 16 Dec 2020 21:28:34 +0100 Source: gcc-11 Architecture: source Version: 11-20201216-2 Distribution: experimental Urgency: medium Maintainer: Debian GCC Maintainers Changed-By: Matthias Klose Closes: 977408 977409 977461 Changes: gcc-11 (11-20201216-2) experimental; urgency=medium . * GCC snapshot, taken from the trunk (20201216) * Rely on the upstream GNU versioned symbols for libstdc++6. * Bump phobos soname for GCC 11. * Add an autopkg test for linking libphobos. * Build gnat again, without building libgnat_util. * Build the gcn offload compiler using LLVM 11, and work around the broken as in LLVM 11. See also LLVM Bug 48201 for this issue and https://reviews.llvm.org/D73999 for the patch causing the issue. * Remove hsa offload packaging bits. * For LTO builds, configure with --enable-link-serialization instead of --enable-link-mutex. * Package additional gnat files. * Update the gm2 packaging. * Add conflicts with binary packages built from gcc-10. * Build libhwasan (AArch64 only). * Don't strip the sanitizer libraries, these are only used for debugging. LP: #1894166. * Explicitly configure with --disable-cet when building for older releases. * Don't run the libgphobos-link test on powerpc architectures. * Install libstdc++6 gdb pretty printer files in /usr/share/gcc (unversioned). * Don't mark the libgcc-sN cross packages with XB-Important/Protected: yes. * Relax the libc-dev dependencies for kfreebsd. * Limit checking when configuring with --enable-checking=extra,rtl. * Apply proposed patch for PR bootstrap/95582. * Enable profiled builds, LTO build for 64bit architectures. * Add -doc conflicts with GC
Bug#977409: marked as done (libgm2-17: contains only libraries with SOVERSION 15)
Your message dated Wed, 16 Dec 2020 20:48:46 + with message-id and subject line Bug#977409: fixed in gcc-11 11-20201216-2 has caused the Debian Bug report #977409, regarding libgm2-17: contains only libraries with SOVERSION 15 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.) -- 977409: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977409 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libgm2-17 Version: 11-20201208-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package ships -rw-r--r-- root/root 31064 2020-12-08 14:08 ./usr/lib/x86_64-linux-gnu/libm2cor.so.15.0.0 -rw-r--r-- root/root189592 2020-12-08 14:08 ./usr/lib/x86_64-linux-gnu/libm2iso.so.15.0.0 -rw-r--r-- root/root 56168 2020-12-08 14:08 ./usr/lib/x86_64-linux-gnu/libm2log.so.15.0.0 -rw-r--r-- root/root 13968 2020-12-08 14:08 ./usr/lib/x86_64-linux-gnu/libm2min.so.15.0.0 -rw-r--r-- root/root172720 2020-12-08 14:08 ./usr/lib/x86_64-linux-gnu/libm2pim.so.15.0.0 lrwxrwxrwx root/root 0 2020-12-08 14:08 ./usr/lib/x86_64-linux-gnu/libm2cor.so.15 -> libm2cor.so.15.0.0 lrwxrwxrwx root/root 0 2020-12-08 14:08 ./usr/lib/x86_64-linux-gnu/libm2iso.so.15 -> libm2iso.so.15.0.0 lrwxrwxrwx root/root 0 2020-12-08 14:08 ./usr/lib/x86_64-linux-gnu/libm2log.so.15 -> libm2log.so.15.0.0 lrwxrwxrwx root/root 0 2020-12-08 14:08 ./usr/lib/x86_64-linux-gnu/libm2min.so.15 -> libm2min.so.15.0.0 lrwxrwxrwx root/root 0 2020-12-08 14:08 ./usr/lib/x86_64-linux-gnu/libm2pim.so.15 -> libm2pim.so.15.0.0 which is inconsistent with being renamed to libgm2-17. It also causes file conflicts with libgm2-15 in sid. Andreas --- End Message --- --- Begin Message --- Source: gcc-11 Source-Version: 11-20201216-2 Done: Matthias Klose We believe that the bug you reported is fixed in the latest version of gcc-11, 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 977...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthias Klose (supplier of updated gcc-11 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 16 Dec 2020 21:28:34 +0100 Source: gcc-11 Architecture: source Version: 11-20201216-2 Distribution: experimental Urgency: medium Maintainer: Debian GCC Maintainers Changed-By: Matthias Klose Closes: 977408 977409 977461 Changes: gcc-11 (11-20201216-2) experimental; urgency=medium . * GCC snapshot, taken from the trunk (20201216) * Rely on the upstream GNU versioned symbols for libstdc++6. * Bump phobos soname for GCC 11. * Add an autopkg test for linking libphobos. * Build gnat again, without building libgnat_util. * Build the gcn offload compiler using LLVM 11, and work around the broken as in LLVM 11. See also LLVM Bug 48201 for this issue and https://reviews.llvm.org/D73999 for the patch causing the issue. * Remove hsa offload packaging bits. * For LTO builds, configure with --enable-link-serialization instead of --enable-link-mutex. * Package additional gnat files. * Update the gm2 packaging. * Add conflicts with binary packages built from gcc-10. * Build libhwasan (AArch64 only). * Don't strip the sanitizer libraries, these are only used for debugging. LP: #1894166. * Explicitly configure with --disable-cet when building for older releases. * Don't run the libgphobos-link test on powerpc architectures. * Install libstdc++6 gdb pretty printer files in /usr/share/gcc (unversioned). * Don't mark the libgcc-sN cross packages with XB-Important/Protected: yes. * Relax the libc-dev dependencies for kfreebsd. * Limit checking when configuring with --enable-checking=extra,rtl. * Apply proposed patch for PR bootstrap/95582. * Enable profiled builds, LTO build for 64bit architectures. * Add -doc conflicts with GCC 10. Closes: #977408. * Don't install the lto-dump binary in the hppa64 package. Closes: #977461. * Let the gcn offload compilers conflict, both shipping the linker tools,
Bug#977408: marked as done (libstdc++-11-doc: missing Conflicts: libstdc++-10-doc)
Your message dated Wed, 16 Dec 2020 20:48:46 + with message-id and subject line Bug#977408: fixed in gcc-11 11-20201216-2 has caused the Debian Bug report #977408, regarding libstdc++-11-doc: missing Conflicts: libstdc++-10-doc 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.) -- 977408: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977408 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libstdc++-11-doc Version: 11-20201208-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. 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 .../libstdc++-11-doc_11-20201208-1_all.deb ... Unpacking libstdc++-11-doc (11-20201208-1) ... dpkg: error processing archive /var/cache/apt/archives/libstdc++-11-doc_11-20201208-1_all.deb (--unpack): trying to overwrite '/usr/share/man/man3/C++Intro.3cxx.gz', which is also in package libstdc++-10-doc 10.2.1-1 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/libstdc++-11-doc_11-20201208-1_all.deb You should consider adding Conflicts+Replaces+Provides on some (internally used) virtual package to avoid running into this problem again in the future. cheers, Andreas libstdc++-10-doc=10.2.1-1_libstdc++-11-doc=11-20201208-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: gcc-11 Source-Version: 11-20201216-2 Done: Matthias Klose We believe that the bug you reported is fixed in the latest version of gcc-11, 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 977...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthias Klose (supplier of updated gcc-11 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 16 Dec 2020 21:28:34 +0100 Source: gcc-11 Architecture: source Version: 11-20201216-2 Distribution: experimental Urgency: medium Maintainer: Debian GCC Maintainers Changed-By: Matthias Klose Closes: 977408 977409 977461 Changes: gcc-11 (11-20201216-2) experimental; urgency=medium . * GCC snapshot, taken from the trunk (20201216) * Rely on the upstream GNU versioned symbols for libstdc++6. * Bump phobos soname for GCC 11. * Add an autopkg test for linking libphobos. * Build gnat again, without building libgnat_util. * Build the gcn offload compiler using LLVM 11, and work around the broken as in LLVM 11. See also LLVM Bug 48201 for this issue and https://reviews.llvm.org/D73999 for the patch causing the issue. * Remove hsa offload packaging bits. * For LTO builds, configure with --enable-link-serialization instead of --enable-link-mutex. * Package additional gnat files. * Update the gm2 packaging. * Add conflicts with binary packages built from gcc-10. * Build libhwasan (AArch64 only). * Don't strip the sanitizer libraries, these are only used for debugging. LP: #1894166. * Explicitly configure with --disable-cet when building for older releases. * Don't run the libgphobos-link test on powerpc architectures. * Install libstdc++6 gdb pretty printer files in /usr/share/gcc (unversioned). * Don't mark the libgcc-sN cross packages with XB-Important/Protected: yes. * Relax the libc-dev dependencies for kfreebsd. * Limit checking when configuring with --enable-checking=extra,rtl. * Apply proposed patch for PR bootstrap/95582. * Enable profiled builds, LTO build for 64bit architectures. * Add -doc conflicts with GCC 10. Closes: #977408. * Don't install the lto-dump binary in the hppa64 package. Closes: #977461. * Let the g
Bug#957758: restbed: ftbfs with GCC-10
[Matthias Klose] > /<>/source/corvusoft/restbed/response.cpp: In member function > ‘void restbed::Response::get_header(const string&, long long int&, long long > int) const’: > /<>/source/corvusoft/restbed/response.cpp:146:23: error: ISO C++ > forbids declaration of ‘invalid_argument’ with no type [-fpermissive] > 146 | catch ( const invalid_argument& ) > | ^~~~ Could it be that the code need to use std::invalid_argument? -- Happy hacking Petter Reinholdtsen
Bug#977260: marked as done (all autopkg tests fail with boost1.74)
Your message dated Wed, 16 Dec 2020 20:39:04 + with message-id and subject line Bug#977260: fixed in svgpp 1.3.0+dfsg1-4 has caused the Debian Bug report #977260, regarding all autopkg tests fail with boost1.74 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.) -- 977260: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977260 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:svgpp Version: 1.3.0+dfsg1-3 Severity: serious Tags: sid bullseye all autopkg tests fail with boost1.74, see https://ci.debian.net/data/autopkgtest/unstable/amd64/s/svgpp/8696315/log.gz autopkgtest [09:09:49]: summary build1 FAIL stderr: In file included from /usr/include/boost/config/header_deprecated.hpp:18, build2 FAIL stderr: In file included from /usr/include/boost/config/header_deprecated.hpp:18, build3 FAIL stderr: In file included from /usr/include/boost/config/header_deprecated.hpp:18, --- End Message --- --- Begin Message --- Source: svgpp Source-Version: 1.3.0+dfsg1-4 Done: Anton Gladky We believe that the bug you reported is fixed in the latest version of svgpp, 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 977...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Anton Gladky (supplier of updated svgpp 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, 16 Dec 2020 21:02:33 +0100 Source: svgpp Architecture: source Version: 1.3.0+dfsg1-4 Distribution: unstable Urgency: medium Maintainer: Anton Gladky Changed-By: Anton Gladky Closes: 977260 Changes: svgpp (1.3.0+dfsg1-4) unstable; urgency=medium . * [aef0c7e] Fix autopkgtests with new boost. (Closes: #977260) * [1491fca] Update watch file format version to 4. Checksums-Sha1: a341ff967d7f488cc8c8a0213979ea6972c145d1 2099 svgpp_1.3.0+dfsg1-4.dsc cb552c9bd3dc9877b1bd1b996b183b82e0ad3aad 5808 svgpp_1.3.0+dfsg1-4.debian.tar.xz 948f060904795655fcc4d24f0cb52b3c973975e8 8420 svgpp_1.3.0+dfsg1-4_source.buildinfo Checksums-Sha256: faf97996b13155d49065bc07f8083f543f22d6f792a59af74cd15aaf86bdd05f 2099 svgpp_1.3.0+dfsg1-4.dsc 8037a54d2d74c9def1e272a7dcc94e40a6967312c77ad9f5c3a040bb782f6bde 5808 svgpp_1.3.0+dfsg1-4.debian.tar.xz c674440c8efd5092efe2d6174ac9966310ec445db096355ffa2259df0871efe8 8420 svgpp_1.3.0+dfsg1-4_source.buildinfo Files: df476f8193a8efdd5762da17882d71fb 2099 libs optional svgpp_1.3.0+dfsg1-4.dsc d83796d8988903cf4e7b00d4610ead25 5808 libs optional svgpp_1.3.0+dfsg1-4.debian.tar.xz d5b8d7e6b3e836f214fd8c4a9c130a8a 8420 libs optional svgpp_1.3.0+dfsg1-4_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEu71F6oGKuG/2fnKF0+Fzg8+n/wYFAl/aZ+UACgkQ0+Fzg8+n /wZrwQ//U9YxsM+3Gb6aKU4hwjn5kWbGose/UBxOjmaZujHzBaYwBKHx7B0/lQtk Sm4XOW+cy6HIWtETfqKIVBvW13hTYmyafNUlSJGC70FnXpqcY9AtOWHbw1gLkUKS K1QToJNcMnkqXZFLj07US6b3LWyo2+tuAhOqUD9lNEISeLBkU4fZ53Y0IwzSt+yQ dNeTd5bURFs7/ylhUu+0iC0u28HUozgZ5avrL54I/o8fCF46UtluD8ItpG758yPQ 79d7mygoXtpGGsinkQrz+oibbcVMfr4gVPNWbAtPUCK1Hks9UgRUxQoYyZDG0K9O eGJQ+jeiBtBzkKZHuuBu1Hhh3s1K3xbWqvVtCfHWQOqzq4+Bjhz81AUtVmRLYjVL xo5/lBuKtQzNg/lbOH5uOGsPh+FY9WkxUJoYojXBWZawuAOu45pELb803gwMq0Ub DsGCmtvIGwb322v3b2qVGBfNadFViQD4O2YOMou6xd3cY+fmpWIqWp8RoT9LFPKK bJ4CGRT77VGSFgWckdWs2NgTvkGf1Mrv8QdcTYC7N+M7hpRr7pJbrejkavIDpRVk uXK8qAlyaC+lzbXXwnmqv7kgQo2pcZmVnWwGyMy3o7zk9o8HAyNRhoD79QGIgGMK F0TaR0WMgKeqxsfk1ClwMH3iTYhIc2cE7+NOi+txQYUHB111Dkk= =HHjX -END PGP SIGNATURE End Message ---
Processed: logtools: diff for NMU version 0.13e+nmu1
Processing control commands: > tags 957499 + patch Bug #957499 [src:logtools] logtools: ftbfs with GCC-10 Added tag(s) patch. > tags 957499 + pending Bug #957499 [src:logtools] logtools: ftbfs with GCC-10 Added tag(s) pending. -- 957499: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957499 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#957499: logtools: diff for NMU version 0.13e+nmu1
Control: tags 957499 + patch Control: tags 957499 + pending -- Dear maintainer, I've prepared an NMU for logtools (versioned as 0.13e+nmu1) and uploaded it to DELAYED/2. Please feel free to tell me if I should cancel it. -- Regards Sudip diff -Nru logtools-0.13e/changes.txt logtools-0.13e+nmu1/changes.txt --- logtools-0.13e/changes.txt 2016-12-25 15:11:11.0 + +++ logtools-0.13e+nmu1/changes.txt 2020-12-16 20:22:13.0 + @@ -1,3 +1,11 @@ +logtools (0.13e+nmu1) unstable; urgency=medium + + * Non-maintainer upload. + * Fix ftbfs with GCC-10. (Closes: #957499) +- Add the missing header files. + + -- Sudip Mukherjee Wed, 16 Dec 2020 20:22:13 + + logtools (0.13e) unstable; urgency=medium * Fixes build problems with latest STL. Closes: #849126 diff -Nru logtools-0.13e/clfdomainsplit.cpp logtools-0.13e+nmu1/clfdomainsplit.cpp --- logtools-0.13e/clfdomainsplit.cpp 2016-12-25 15:08:38.0 + +++ logtools-0.13e+nmu1/clfdomainsplit.cpp 2020-12-16 20:13:55.0 + @@ -6,6 +6,7 @@ #include #include #include +#include #include "logtools.h" using namespace std; diff -Nru logtools-0.13e/clfmerge.cpp logtools-0.13e+nmu1/clfmerge.cpp --- logtools-0.13e/clfmerge.cpp 2016-12-25 14:50:06.0 + +++ logtools-0.13e+nmu1/clfmerge.cpp2020-12-16 20:12:02.0 + @@ -5,6 +5,7 @@ #include #include #include +#include #include "logtools.h" diff -Nru logtools-0.13e/debian/changelog logtools-0.13e+nmu1/debian/changelog --- logtools-0.13e/debian/changelog 2016-12-25 15:11:11.0 + +++ logtools-0.13e+nmu1/debian/changelog2020-12-16 20:22:13.0 + @@ -1,3 +1,11 @@ +logtools (0.13e+nmu1) unstable; urgency=medium + + * Non-maintainer upload. + * Fix ftbfs with GCC-10. (Closes: #957499) +- Add the missing header files. + + -- Sudip Mukherjee Wed, 16 Dec 2020 20:22:13 + + logtools (0.13e) unstable; urgency=medium * Fixes build problems with latest STL. Closes: #849126
Processed: Bug#977243 marked as pending in ceph
Processing control commands: > tag -1 pending Bug #977243 [src:ceph] ceph FTBFS with Boost 1.74 Added tag(s) pending. -- 977243: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977243 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#977243: marked as pending in ceph
Control: tag -1 pending Hello, Bug #977243 in ceph 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/ceph-team/ceph/-/commit/4bc646487beaa402c27e9596b7569aafde1f30c3 Add upstream patch for libboost 1.74 (Closes: #977243). (this message was generated automatically) -- Greetings https://bugs.debian.org/977243
Processed: please package 0.30.0
Processing control commands: > block 975535 by -1 Bug #975535 [src:elpy] elpy's autopkg tests fail with Python 3.9 975535 was blocked by: 977558 975535 was not blocking any bugs. Added blocking bug(s) of 975535: 977563 -- 975535: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975535 977563: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977563 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: closing 975187
Processing commands for cont...@bugs.debian.org: > close 975187 0.1.15-2 Bug #975187 [src:rust-libmount] rust-libmount: FTBFS: build-dependency not installable: librust-nix-0.16+default-dev Marked as fixed in versions rust-libmount/0.1.15-2. Bug #975187 [src:rust-libmount] rust-libmount: FTBFS: build-dependency not installable: librust-nix-0.16+default-dev Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 975187: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975187 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#975943: Patch
Processing control commands: > tag -1 patch Bug #975943 [raspi-firmware] raspi-firmware: arm_64bit is missing and linux-image-arm64 unbootable Added tag(s) patch. -- 975943: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975943 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#975943: Patch
Control: tag -1 patch Just submitted a MR which fixes this issue: https://salsa.debian.org/debian/raspi-firmware/-/merge_requests/18 signature.asc Description: This is a digitally signed message part.
Bug#977222: marked as done (dolfin: FTBFS: error: ‘min_element’ is not a member of ‘std’; did you mean ‘tuple_element’?)
Your message dated Wed, 16 Dec 2020 19:18:27 + with message-id and subject line Bug#977222: fixed in dolfin 2019.2.0~git20200629.946dbd3+lfs-4 has caused the Debian Bug report #977222, regarding dolfin: FTBFS: error: ‘min_element’ is not a member of ‘std’; did you mean ‘tuple_element’? 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.) -- 977222: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977222 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: dolfin Version: 2019.2.0~git20200629.946dbd3+lfs-3 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org dolfin failed to build with: | cd "/<>/obj-x86_64-linux-gnu/dolfin" && /usr/bin/c++ -DDOLFIN_VERSION=\"2019.2.0.dev0\" -DHAS_CHOLMOD -DHAS_HDF5 -DHAS_MPI -DHAS_PETSC -DHAS_SCOTCH -DHAS_SLEPC -DHAS_UMFPACK -DHAS_ZLIB -DNDEBUG -Ddolfin_EXPORTS -I"/<>" -I"/<>/obj-x86_64-linux-gnu" -isystem /usr/lib/python3/dist-packages/ffc/backends/ufc -isystem /usr/include/eigen3 -isystem /usr/include/hdf5/openmpi -isystem /usr/include/suitesparse -isystem /usr/include/scotch -isystem /usr/lib/x86_64-linux-gnu/openmpi/include/openmpi -isystem /usr/lib/x86_64-linux-gnu/openmpi/include -isystem /usr/lib/petscdir/petsc3.14/x86_64-linux-gnu-real/include -isystem /usr/lib/slepcdir/slepc3.14/x86_64-linux-gnu-real/include -fpermissive -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -O2 -g -DNDEBUG -fPIC -std=c++11 -o CMakeFiles/dolfin.dir/geometry/MeshPointIntersection.cpp.o -c "/<>/dolfin/geometry/MeshPointIntersection.cpp" | /<>/dolfin/geometry/IntersectionConstruction.cpp: In static member function ‘static std::vector dolfin::IntersectionConstruction::intersection_segment_segment_2d(const dolfin::Point&, const dolfin::Point&, const dolfin::Point&, const dolfin::Point&)’: | /<>/dolfin/geometry/IntersectionConstruction.cpp:442:24: error: ‘min_element’ is not a member of ‘std’; did you mean ‘tuple_element’? | 442 | const auto it = std::min_element(oo.begin(), oo.end()); | |^~~ | |tuple_element | make[4]: *** [dolfin/CMakeFiles/dolfin.dir/build.make:1203: dolfin/CMakeFiles/dolfin.dir/geometry/IntersectionConstruction.cpp.o] Error 1 https://buildd.debian.org/status/fetch.php?pkg=dolfin&arch=amd64&ver=2019.2.0%7Egit20200629.946dbd3%2Blfs-3%2Bb2&stamp=1607782416&raw=0 Cheers -- Sebastian Ramacher signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: dolfin Source-Version: 2019.2.0~git20200629.946dbd3+lfs-4 Done: Anton Gladky We believe that the bug you reported is fixed in the latest version of dolfin, 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 977...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Anton Gladky (supplier of updated dolfin 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, 15 Dec 2020 22:52:05 +0100 Source: dolfin Architecture: source Version: 2019.2.0~git20200629.946dbd3+lfs-4 Distribution: unstable Urgency: medium Maintainer: Debian Science Team Changed-By: Anton Gladky Closes: 977222 Changes: dolfin (2019.2.0~git20200629.946dbd3+lfs-4) unstable; urgency=medium . * Team upload. * [7286d2a] Fix FTBFS. (Closes: #977222) * [47cdea3] Ignore quilt dir * [c8d8285] Remove unused patch * [8e0289b] Trim trailing whitespace. * [a251c1d] Use secure copyright file specification URI. * [c6c315f] debian/copyright: use spaces rather than tabs to start continuation lines. * [327629b] Remove unnecessary get-orig-source-target. * [615ba90] Drop transition for old debug package migration. * [d47166b] Respect CPPFLAGS Checksums-Sha1: be32e861dc855aaa2bdd11496687f75ecbf5056a 3829 dolfin_2019.2.0~git20200629.946dbd3+lfs-4.dsc 911eaccca4e631eb8c65b097ac1c449da899a9e9 36588 dolfin_2019.2.0~git20200629.946dbd3+lfs-4.debian.tar.xz 86eee90dcf1137d15a90c165babf0d5d1db8fb14 12896 dolfin_2019.2.0~git20200629.946dbd3+lfs-4_source.buildinfo Checksums-S
Processed: python-jedi: please package 0.17.2
Processing control commands: > block 975535 by -1 Bug #975535 [src:elpy] elpy's autopkg tests fail with Python 3.9 975535 was not blocked by any bugs. 975535 was not blocking any bugs. Added blocking bug(s) of 975535: 977558 -- 975535: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975535 977558: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977558 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#976578: marked as done (golang-github-labstack-gommon: FTBFS on arm64,ppc64el (arch:all-only src pkg): dh_auto_test: error: cd obj-aarch64-linux-gnu && go test -vet=off -v -p 4 github.com/labstack
Your message dated Wed, 16 Dec 2020 18:33:26 + with message-id and subject line Bug#976578: fixed in golang-github-labstack-gommon 0.2.6-2 has caused the Debian Bug report #976578, regarding golang-github-labstack-gommon: FTBFS on arm64,ppc64el (arch:all-only src pkg): dh_auto_test: error: cd obj-aarch64-linux-gnu && go test -vet=off -v -p 4 github.com/labstack/gommon github.com/labstack/gommon/bytes github.com/labstack/gommon/color github.com/labstack/gommon/email github.com/labstack/gommon/log github.com/labstack/gommon/random returned exit code 1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 976578: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976578 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: golang-github-labstack-gommon Version: 0.2.6-1 Severity: serious Justification: FTBFS on arm64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201205 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on arm64 (I don't know if it also fails on amd64). Relevant part (hopefully): > debian/rules build > dh build --buildsystem=golang --with=golang >dh_update_autotools_config -O--buildsystem=golang >dh_autoreconf -O--buildsystem=golang >dh_auto_configure -O--buildsystem=golang >dh_auto_build -O--buildsystem=golang > cd obj-aarch64-linux-gnu && go install -trimpath -v -p 4 > github.com/labstack/gommon github.com/labstack/gommon/bytes > github.com/labstack/gommon/color github.com/labstack/gommon/email > github.com/labstack/gommon/log github.com/labstack/gommon/random > github.com/labstack/gommon > internal/unsafeheader > internal/cpu > runtime/internal/sys > runtime/internal/atomic > math/bits > runtime/internal/math > internal/bytealg > unicode/utf8 > math > internal/race > sync/atomic > unicode > runtime > internal/testlog > golang.org/x/sys/internal/unsafeheader > container/list > crypto/internal/subtle > crypto/subtle > unicode/utf16 > vendor/golang.org/x/crypto/cryptobyte/asn1 > internal/nettrace > runtime/cgo > vendor/golang.org/x/crypto/internal/subtle > encoding > internal/reflectlite > sync > internal/singleflight > math/rand > errors > sort > io > internal/oserror > strconv > vendor/golang.org/x/net/dns/dnsmessage > syscall > bytes > reflect > strings > hash > crypto > regexp/syntax > crypto/internal/randutil > bufio > internal/syscall/unix > time > internal/syscall/execenv > crypto/hmac > regexp > crypto/rc4 > vendor/golang.org/x/crypto/hkdf > html > internal/fmtsort > encoding/binary > internal/poll > context > github.com/labstack/gommon/random > github.com/valyala/bytebufferpool > golang.org/x/sys/unix > crypto/cipher > crypto/sha512 > os > crypto/ed25519/internal/edwards25519 > crypto/aes > fmt > crypto/des > crypto/md5 > crypto/sha1 > crypto/sha256 > encoding/base64 > path/filepath > github.com/labstack/gommon/bytes > math/big > github.com/mattn/go-isatty > encoding/hex > github.com/mattn/go-colorable > encoding/pem > github.com/labstack/gommon/color > io/ioutil > net > net/url > vendor/golang.org/x/crypto/chacha20 > vendor/golang.org/x/crypto/poly1305 > vendor/golang.org/x/crypto/curve25519 > vendor/golang.org/x/crypto/chacha20poly1305 > encoding/json > text/template/parse > crypto/elliptic > encoding/asn1 > crypto/rand > crypto/dsa > crypto/ed25519 > text/template > crypto/rsa > vendor/golang.org/x/crypto/cryptobyte > crypto/x509/pkix > log > crypto/ecdsa > html/template > mime > github.com/valyala/fasttemplate > path > github.com/labstack/gommon/log > net/textproto > crypto/x509 > net/mail > crypto/tls > net/smtp > github.com/labstack/gommon/email >dh_auto_test -O--buildsystem=golang > cd obj-aarch64-linux-gnu && go test -vet=off -v -p 4 > github.com/labstack/gommon github.com/labstack/gommon/bytes > github.com/labstack/gommon/color github.com/labstack/gommon/email > github.com/labstack/gommon/log github.com/labstack/gommon/random > ? github.com/labstack/gommon [no test files] > === RUN TestBytesFormat > --- PASS: TestBytesFormat (0.00s) > === RUN TestBytesParseErrors > --- PASS: TestBytesParseErrors (0.00s) > === RUN TestFloats > --- PASS: TestFloats (0.00s) > === RUN TestBytesParse > bytes_test.go:146: > Error Trace:bytes_test.go:146 > Error: Should be true > Test: TestBytesParse > bytes_test.go:150: > Error Trace:bytes_test.go:150 > Error: Should be true > Test: TestBytesParse > --- FAIL: TestBytesParse (0.00s) > FAIL > FAI
Bug#957996: xppaut: diff for NMU version 6.11b+1.dfsg-1.1
Control: tags 957996 + patch Control: tags 957996 + pending -- Dear maintainer, I've prepared an NMU for xppaut (versioned as 6.11b+1.dfsg-1.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should cancel it. -- Regards Sudip diff -Nru xppaut-6.11b+1.dfsg/debian/changelog xppaut-6.11b+1.dfsg/debian/changelog --- xppaut-6.11b+1.dfsg/debian/changelog2012-02-13 03:23:30.0 + +++ xppaut-6.11b+1.dfsg/debian/changelog2020-12-16 18:12:16.0 + @@ -1,3 +1,10 @@ +xppaut (6.11b+1.dfsg-1.1) unstable; urgency=medium + + * Non-maintainer upload. + * Fix ftbfs with GCC-10. (Closes: #957996) + + -- Sudip Mukherjee Wed, 16 Dec 2020 18:12:16 + + xppaut (6.11b+1.dfsg-1) unstable; urgency=low [ Jakub Nowacki ] diff -Nru xppaut-6.11b+1.dfsg/debian/patches/fix_gcc-10.patch xppaut-6.11b+1.dfsg/debian/patches/fix_gcc-10.patch --- xppaut-6.11b+1.dfsg/debian/patches/fix_gcc-10.patch 1970-01-01 01:00:00.0 +0100 +++ xppaut-6.11b+1.dfsg/debian/patches/fix_gcc-10.patch 2020-12-16 18:11:49.0 + @@ -0,0 +1,21 @@ +Description: Fix ftbfs with GCC-10 + + Use -fcommon with CFLAGS + +Author: Sudip Mukherjee +Bug-Debian: https://bugs.debian.org/957996 +Forwarded: no + +--- + +--- xppaut-6.11b+1.dfsg.orig/Makefile xppaut-6.11b+1.dfsg/Makefile +@@ -36,7 +36,7 @@ AUTLIBS= -lm + #CFLAGS= -g -O -m32 -DNON_UNIX_STDIO -DAUTO -DCVODE_YES -DHAVEDLL -DMYSTR1=$(MAJORVER) -DMYSTR2=$(MINORVER) -I/usr/X11R6/include + #CFLAGS= -g -O -m64 -DNOERRNO -DNON_UNIX_STDIO -DAUTO -DCVODE_YES -DHAVEDLL -DMYSTR1=$(MAJORVER) -DMYSTR2=$(MINORVER) -I/usr/include/X11 + +-CFLAGS = -g -pedantic -O -DNOERRNO -DNON_UNIX_STDIO -DAUTO -DCVODE_YES -DHAVEDLL -DMYSTR1=$(MAJORVER) -DMYSTR2=$(MINORVER) -I/usr/include/X11 ++CFLAGS = -g -pedantic -fcommon -O -DNOERRNO -DNON_UNIX_STDIO -DAUTO -DCVODE_YES -DHAVEDLL -DMYSTR1=$(MAJORVER) -DMYSTR2=$(MINORVER) -I/usr/include/X11 + #LDFLAGS= -m64 -L/usr/lib -L/usr/lib64 + LDFLAGS= -L/usr/lib + LIBS= -lX11 -lm -ldl diff -Nru xppaut-6.11b+1.dfsg/debian/patches/series xppaut-6.11b+1.dfsg/debian/patches/series --- xppaut-6.11b+1.dfsg/debian/patches/series 2012-02-13 03:23:30.0 + +++ xppaut-6.11b+1.dfsg/debian/patches/series 2020-12-16 18:10:37.0 + @@ -1,2 +1,3 @@ 010_makefile.diff 040_menudrive_c.diff +fix_gcc-10.patch
Processed: xppaut: diff for NMU version 6.11b+1.dfsg-1.1
Processing control commands: > tags 957996 + patch Bug #957996 [src:xppaut] xppaut: ftbfs with GCC-10 Added tag(s) patch. > tags 957996 + pending Bug #957996 [src:xppaut] xppaut: ftbfs with GCC-10 Added tag(s) pending. -- 957996: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957996 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#976578 marked as pending in golang-github-labstack-gommon
Processing control commands: > tag -1 pending Bug #976578 [src:golang-github-labstack-gommon] golang-github-labstack-gommon: FTBFS on arm64,ppc64el (arch:all-only src pkg): dh_auto_test: error: cd obj-aarch64-linux-gnu && go test -vet=off -v -p 4 github.com/labstack/gommon github.com/labstack/gommon/bytes github.com/labstack/gommon/color github.com/labstack/gommon/email github.com/labstack/gommon/log github.com/labstack/gommon/random returned exit code 1 Added tag(s) pending. -- 976578: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976578 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#976578: marked as pending in golang-github-labstack-gommon
Control: tag -1 pending Hello, Bug #976578 in golang-github-labstack-gommon 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/go-team/packages/golang-github-labstack-gommon/-/commit/33d34e03906aa1789afe652f41557a73d145f6cd Pull+modify Upstream PR to fix arm64 FTBFS (Closes: #976578) (this message was generated automatically) -- Greetings https://bugs.debian.org/976578
Bug#977461: marked as done (gcc-1[01]-offload-amdgcn,gcc-1[01]-hppa64-linux-gnu: shipping unversioned binaries causes file conflicts)
Your message dated Wed, 16 Dec 2020 18:03:29 + with message-id and subject line Bug#977461: fixed in gcc-11 11-20201216-1 has caused the Debian Bug report #977461, regarding gcc-1[01]-offload-amdgcn,gcc-1[01]-hppa64-linux-gnu: shipping unversioned binaries causes file conflicts 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.) -- 977461: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977461 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gcc-10-offload-amdgcn,gcc-11-offload-amdgcn,gcc-10-hppa64-linux-gnu,gcc-11-hppa64-linux-gnu Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: found -1 10.2.1-1 Control: found -1 11-20201208-1 Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fails because it tries to overwrite other packages files. >From the attached log (scroll to the bottom...): Preparing to unpack .../gcc-11-offload-amdgcn_11-20201208-1_amd64.deb ... Unpacking gcc-11-offload-amdgcn (11-20201208-1) ... dpkg: error processing archive /var/cache/apt/archives/gcc-11-offload-amdgcn_11-20201208-1_amd64.deb (--unpack): trying to overwrite '/usr/amdgcn-amdhsa/bin/ar', which is also in package gcc-10-offload-amdgcn 10.2.1-1 Errors were encountered while processing: /var/cache/apt/archives/gcc-11-offload-amdgcn_11-20201208-1_amd64.deb These unversioned files are in conflict between the gcc versions: usr/amdgcn-amdhsa/bin/ar usr/amdgcn-amdhsa/bin/as usr/amdgcn-amdhsa/bin/ld usr/amdgcn-amdhsa/bin/nm usr/amdgcn-amdhsa/bin/ranlib usr/bin/hppa64-linux-gnu-lto-dump Maybe the unversioned binaries should be managed by unversioned packages from gcc-defaults instead. cheers, Andreas gcc-10-offload-amdgcn=10.2.1-1_gcc-11-offload-amdgcn=11-20201208-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: gcc-11 Source-Version: 11-20201216-1 Done: Matthias Klose We believe that the bug you reported is fixed in the latest version of gcc-11, 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 977...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthias Klose (supplier of updated gcc-11 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 16 Dec 2020 18:38:05 +0100 Source: gcc-11 Architecture: source Version: 11-20201216-1 Distribution: experimental Urgency: medium Maintainer: Debian GCC Maintainers Changed-By: Matthias Klose Closes: 977408 977409 977461 Changes: gcc-11 (11-20201216-1) experimental; urgency=medium . * GCC snapshot, taken from the trunk (20201216) * Rely on the upstream GNU versioned symbols for libstdc++6. * Bump phobos soname for GCC 11. * Add an autopkg test for linking libphobos. * Build gnat again, without building libgnat_util. * Build the gcn offload compiler using LLVM 11, and work around the broken as in LLVM 11. See also LLVM Bug 48201 for this issue and https://reviews.llvm.org/D73999 for the patch causing the issue. * Remove hsa offload packaging bits. * For LTO builds, configure with --enable-link-serialization instead of --enable-link-mutex. * Package additional gnat files. * Update the gm2 packaging. * Add conflicts with binary packages built from gcc-10. * Build libhwasan (AArch64 only). * Don't strip the sanitizer libraries, these are only used for debugging. LP: #1894166. * Explicitly configure with --disable-cet when building for older releases. * Don't run the libgphobos-link test on powerpc architectures. * Install libstdc++6 gdb pretty printer files in /usr/share/gcc (unversioned). * Don't mark the libgcc-sN cross packages with XB-Important/Protected: yes. * Relax the libc-dev dependencies for kfreebsd. * Limit checking when configuring with --enable-checking=extra,rtl. * Apply proposed patch for PR bootstrap/95582. * Enable profiled builds, LTO build for 64bit architectures. * Add -doc conflicts with GC
Bug#977409: marked as done (libgm2-17: contains only libraries with SOVERSION 15)
Your message dated Wed, 16 Dec 2020 18:03:29 + with message-id and subject line Bug#977409: fixed in gcc-11 11-20201216-1 has caused the Debian Bug report #977409, regarding libgm2-17: contains only libraries with SOVERSION 15 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.) -- 977409: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977409 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libgm2-17 Version: 11-20201208-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package ships -rw-r--r-- root/root 31064 2020-12-08 14:08 ./usr/lib/x86_64-linux-gnu/libm2cor.so.15.0.0 -rw-r--r-- root/root189592 2020-12-08 14:08 ./usr/lib/x86_64-linux-gnu/libm2iso.so.15.0.0 -rw-r--r-- root/root 56168 2020-12-08 14:08 ./usr/lib/x86_64-linux-gnu/libm2log.so.15.0.0 -rw-r--r-- root/root 13968 2020-12-08 14:08 ./usr/lib/x86_64-linux-gnu/libm2min.so.15.0.0 -rw-r--r-- root/root172720 2020-12-08 14:08 ./usr/lib/x86_64-linux-gnu/libm2pim.so.15.0.0 lrwxrwxrwx root/root 0 2020-12-08 14:08 ./usr/lib/x86_64-linux-gnu/libm2cor.so.15 -> libm2cor.so.15.0.0 lrwxrwxrwx root/root 0 2020-12-08 14:08 ./usr/lib/x86_64-linux-gnu/libm2iso.so.15 -> libm2iso.so.15.0.0 lrwxrwxrwx root/root 0 2020-12-08 14:08 ./usr/lib/x86_64-linux-gnu/libm2log.so.15 -> libm2log.so.15.0.0 lrwxrwxrwx root/root 0 2020-12-08 14:08 ./usr/lib/x86_64-linux-gnu/libm2min.so.15 -> libm2min.so.15.0.0 lrwxrwxrwx root/root 0 2020-12-08 14:08 ./usr/lib/x86_64-linux-gnu/libm2pim.so.15 -> libm2pim.so.15.0.0 which is inconsistent with being renamed to libgm2-17. It also causes file conflicts with libgm2-15 in sid. Andreas --- End Message --- --- Begin Message --- Source: gcc-11 Source-Version: 11-20201216-1 Done: Matthias Klose We believe that the bug you reported is fixed in the latest version of gcc-11, 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 977...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthias Klose (supplier of updated gcc-11 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 16 Dec 2020 18:38:05 +0100 Source: gcc-11 Architecture: source Version: 11-20201216-1 Distribution: experimental Urgency: medium Maintainer: Debian GCC Maintainers Changed-By: Matthias Klose Closes: 977408 977409 977461 Changes: gcc-11 (11-20201216-1) experimental; urgency=medium . * GCC snapshot, taken from the trunk (20201216) * Rely on the upstream GNU versioned symbols for libstdc++6. * Bump phobos soname for GCC 11. * Add an autopkg test for linking libphobos. * Build gnat again, without building libgnat_util. * Build the gcn offload compiler using LLVM 11, and work around the broken as in LLVM 11. See also LLVM Bug 48201 for this issue and https://reviews.llvm.org/D73999 for the patch causing the issue. * Remove hsa offload packaging bits. * For LTO builds, configure with --enable-link-serialization instead of --enable-link-mutex. * Package additional gnat files. * Update the gm2 packaging. * Add conflicts with binary packages built from gcc-10. * Build libhwasan (AArch64 only). * Don't strip the sanitizer libraries, these are only used for debugging. LP: #1894166. * Explicitly configure with --disable-cet when building for older releases. * Don't run the libgphobos-link test on powerpc architectures. * Install libstdc++6 gdb pretty printer files in /usr/share/gcc (unversioned). * Don't mark the libgcc-sN cross packages with XB-Important/Protected: yes. * Relax the libc-dev dependencies for kfreebsd. * Limit checking when configuring with --enable-checking=extra,rtl. * Apply proposed patch for PR bootstrap/95582. * Enable profiled builds, LTO build for 64bit architectures. * Add -doc conflicts with GCC 10. Closes: #977408. * Don't install the lto-dump binary in the hppa64 package. Closes: #977461. * Let the gcn offload compilers conflict, both shipping the linker tools,
Bug#977408: marked as done (libstdc++-11-doc: missing Conflicts: libstdc++-10-doc)
Your message dated Wed, 16 Dec 2020 18:03:29 + with message-id and subject line Bug#977408: fixed in gcc-11 11-20201216-1 has caused the Debian Bug report #977408, regarding libstdc++-11-doc: missing Conflicts: libstdc++-10-doc 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.) -- 977408: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977408 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libstdc++-11-doc Version: 11-20201208-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. 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 .../libstdc++-11-doc_11-20201208-1_all.deb ... Unpacking libstdc++-11-doc (11-20201208-1) ... dpkg: error processing archive /var/cache/apt/archives/libstdc++-11-doc_11-20201208-1_all.deb (--unpack): trying to overwrite '/usr/share/man/man3/C++Intro.3cxx.gz', which is also in package libstdc++-10-doc 10.2.1-1 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/libstdc++-11-doc_11-20201208-1_all.deb You should consider adding Conflicts+Replaces+Provides on some (internally used) virtual package to avoid running into this problem again in the future. cheers, Andreas libstdc++-10-doc=10.2.1-1_libstdc++-11-doc=11-20201208-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: gcc-11 Source-Version: 11-20201216-1 Done: Matthias Klose We believe that the bug you reported is fixed in the latest version of gcc-11, 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 977...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matthias Klose (supplier of updated gcc-11 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 16 Dec 2020 18:38:05 +0100 Source: gcc-11 Architecture: source Version: 11-20201216-1 Distribution: experimental Urgency: medium Maintainer: Debian GCC Maintainers Changed-By: Matthias Klose Closes: 977408 977409 977461 Changes: gcc-11 (11-20201216-1) experimental; urgency=medium . * GCC snapshot, taken from the trunk (20201216) * Rely on the upstream GNU versioned symbols for libstdc++6. * Bump phobos soname for GCC 11. * Add an autopkg test for linking libphobos. * Build gnat again, without building libgnat_util. * Build the gcn offload compiler using LLVM 11, and work around the broken as in LLVM 11. See also LLVM Bug 48201 for this issue and https://reviews.llvm.org/D73999 for the patch causing the issue. * Remove hsa offload packaging bits. * For LTO builds, configure with --enable-link-serialization instead of --enable-link-mutex. * Package additional gnat files. * Update the gm2 packaging. * Add conflicts with binary packages built from gcc-10. * Build libhwasan (AArch64 only). * Don't strip the sanitizer libraries, these are only used for debugging. LP: #1894166. * Explicitly configure with --disable-cet when building for older releases. * Don't run the libgphobos-link test on powerpc architectures. * Install libstdc++6 gdb pretty printer files in /usr/share/gcc (unversioned). * Don't mark the libgcc-sN cross packages with XB-Important/Protected: yes. * Relax the libc-dev dependencies for kfreebsd. * Limit checking when configuring with --enable-checking=extra,rtl. * Apply proposed patch for PR bootstrap/95582. * Enable profiled builds, LTO build for 64bit architectures. * Add -doc conflicts with GCC 10. Closes: #977408. * Don't install the lto-dump binary in the hppa64 package. Closes: #977461. * Let the g
Bug#975169: litecoin: FTBFS: qt/trafficgraphwidget.cpp:55:9: error: invalid use of incomplete type ‘class QPainterPath’
Dear Maintainer, after adding #include in qt/trafficgraphwidget.cpp, litecoin builds fine in a pbuilder sid chroot. Kind Regards
Bug#977552: gnutls28: Time bomb in testpkcs11.sh triggered
Source: gnutls28 Version: 3.6.15-1 Severity: serious Tags: upstream ftbfs Justification: fails to build from source Forwarded: https://gitlab.com/gnutls/gnutls/-/issues/1135 autopkgtests and build fail now due to an expired certificate Not After : Dec 13 08:24:54 2020 GMT cu Andreas
Bug#976915: service-wrapper-java: FTBFS on ppc64el: [exec] wrapper.c:(.text+0x3598): undefined reference to `pow'
On Wed, Dec 16, 2020 at 04:43:55PM +0100, Emmanuel Bourg wrote: > Le 13/12/2020 à 00:38, Markus Koschany a écrit : > > > In this case I believe the RC severity is correct because the arch:any or > > jni > > version of the package FTBFS on ppc64el. We should try to fix the problem on > > ppc64el or, if upstream doesn't support ppc64el, remove the architecture > > from > > the list of supported architectures in debian/control. > > As a side note, if we keep getting issues with service-wrapper-java I > wonder if we could scrap it, systemd is now able to provide similar > auto-restart features for services. Good idea. The only r-dep I see is i2p, and the popcon graphs [2,3] appear to match pretty closely. I am adding mha...@debian.org to the thread. Perhaps we can update i2p and and drop service-wrapper from bullseye. Cheers, tony [1] https://tracker.debian.org/pkg/i2p [2] https://qa.debian.org/popcon.php?package=service-wrapper-java [3] https://qa.debian.org/popcon.php?package=i2p signature.asc Description: PGP signature
Bug#970580: marked as done (licenseutils: Memory access error)
Your message dated Wed, 16 Dec 2020 17:33:40 + with message-id and subject line Bug#970580: fixed in licenseutils 0.0.9-4 has caused the Debian Bug report #970580, regarding licenseutils: Memory access error 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.) -- 970580: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970580 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: licenseutils Version: 0.0.9-3+b1: Severity: grave I want to work out the different tools checking the license for packaging as described at https://wiki.debian.org/CopyrightReviewTools At the first start I got licensing gpl: got unexpected response code 302 from www.gnu.org/licenses/gpl.txt I also tested more options and get "Memory access error" No option gives a result -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (400, 'testing'), (300, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: 5.8.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Kind regards -- Mechtilde Stehmann ## Debian Developer ## PGP encryption welcome ## F0E3 7F3D C87A 4998 2899 39E7 F287 7BBA 141A AD7F signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: licenseutils Source-Version: 0.0.9-4 Done: Mattia Rizzolo We believe that the bug you reported is fixed in the latest version of licenseutils, 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 970...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mattia Rizzolo (supplier of updated licenseutils 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, 16 Dec 2020 17:47:31 +0100 Source: licenseutils Architecture: source Version: 0.0.9-4 Distribution: unstable Urgency: medium Maintainer: Mattia Rizzolo Changed-By: Mattia Rizzolo Closes: 970580 Changes: licenseutils (0.0.9-4) unstable; urgency=medium . [ Debian Janitor ] * Use secure URI in Homepage field. * Bump debhelper from old 11 to 12. * Set upstream metadata fields: Bug-Submit, Repository, Repository-Browse. . [ Mattia Rizzolo ] * Bump Standards-Version to 4.5.1, no changes needed. * Bump debhelper compat level to 13. * Bump watchfile to version 4. * Fix lintian override so that it matches again after lintian changes. * Add patch to prevent a segfault when trying to download license files that have been redirected. Closes: #970580 Thanks to handsome_feng for the patch Checksums-Sha1: 5a87bbeed92eff0aa82527082900f4ce4658da46 1959 licenseutils_0.0.9-4.dsc 96857a64de2e93982ad6f48b7633773a65c23465 5436 licenseutils_0.0.9-4.debian.tar.xz 24aec1b2706a3e2a326de9cd95b96f96db0a9d7a 8393 licenseutils_0.0.9-4_amd64.buildinfo Checksums-Sha256: 7d65bb42d68060f871225997c22e4c50cd9e3a11b54f9c3e9a11f30a724cb4b2 1959 licenseutils_0.0.9-4.dsc 78a4bb87dd0dad47a702ad2e5d4947c5536b791f4107f4e21c883e87c1d42c33 5436 licenseutils_0.0.9-4.debian.tar.xz 8b0b89262fdfaabf4991fbe1ba5457f66071b6ac1266c9709bd76abb4918def5 8393 licenseutils_0.0.9-4_amd64.buildinfo Files: bf70d572c8890c2752c90a6f1b7a26db 1959 devel optional licenseutils_0.0.9-4.dsc 22338828308036cfcc7e898f11bf6b64 5436 devel optional licenseutils_0.0.9-4.debian.tar.xz ae250eb6690258c7804ef9fdd2a1cdf6 8393 devel optional licenseutils_0.0.9-4_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEi3hoeGwz5cZMTQpICBa54Yx2K60FAl/aPqUACgkQCBa54Yx2 K63S5g//fGz2p7E/uVvpwuNhQky4OEO3EUH3ayv21Rj3flprDfjUXmq/wUhFXwAD 7x4lNgsqXwIFROsMFwgBsH5ynvRvrQQY2uqyxZg4qyEs4MwJBl7AZdHfseVvHcK4 kPilnPPr0lXQJ2fWDMJCrTbGpObSE+K+soORN43Ttb6/6EuWELd8zIyUzTT/B/if lICX6xrEvjmWDkJsjGIr8eJQTnFdc5XtHMSQT9DT8O5p38+QjCvSlk9iPw6Utlew L7cE3zdY1P5KiAh4cMpGdBMmeWxvrjx4bEJMQBxsHFlg+aQcwf1UN8ytp3UodBhX k6RAuRd1IiXdfy81vykGkMiKsCFwU6YV7Zs21TRs0Zvxuf3ifzn1yQO+aTx84fcO ad0MisGifDJC9E99tNRV+Hlt/UZiKJOXYEP5PfyNJTgIKfVqnXGTFOM2MlGeWzXu +7l0HiU01PSo6a9d39OCwgsEc
Processed: xfractint: diff for NMU version 20.4.10-2.1
Processing control commands: > tags 966184 + patch Bug #966184 [src:xfractint] xfractint: FTBFS with GCC 10: multiple definition of ... due to -fno-common Added tag(s) patch. > tags 966184 + pending Bug #966184 [src:xfractint] xfractint: FTBFS with GCC 10: multiple definition of ... due to -fno-common Added tag(s) pending. -- 966184: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966184 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#966184: xfractint: diff for NMU version 20.4.10-2.1
Control: tags 966184 + patch Control: tags 966184 + pending -- Dear maintainer, I've prepared an NMU for xfractint (versioned as 20.4.10-2.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should cancel it. -- Regards Sudip diff -u xfractint-20.4.10/debian/changelog xfractint-20.4.10/debian/changelog --- xfractint-20.4.10/debian/changelog +++ xfractint-20.4.10/debian/changelog @@ -1,3 +1,11 @@ +xfractint (20.4.10-2.1) unstable; urgency=medium + + * Non-maintainer upload. + * Fix FTBFS with GCC 10. (Closes: #966184) +- Use -fcommon with CFLAGS. + + -- Sudip Mukherjee Wed, 16 Dec 2020 17:16:36 + + xfractint (20.4.10-2) unstable; urgency=low * replace/conflict with fractxtra. Closes: #604975 only in patch2: unchanged: --- xfractint-20.4.10.orig/Makefile +++ xfractint-20.4.10/Makefile @@ -118,7 +118,7 @@ ifeq ($(AS),/usr/bin/nasm) -CFLAGS = -I$(HFD) $(DEFINES) -g -DBIG_ANSI_C -DLINUX -DNASM -fno-builtin +CFLAGS = -I$(HFD) $(DEFINES) -g -DBIG_ANSI_C -DLINUX -DNASM -fno-builtin -fcommon #CFLAGS = -I. -D_CONST $(DEFINES) #CFLAGS = -I$(HFD) $(DEFINES) -g -DBIG_ANSI_C -DLINUX \ # -march=$(ARCH) -DNASM -fno-builtin @@ -126,7 +126,7 @@ else -CFLAGS = -I$(HFD) $(DEFINES) -g -DBIG_ANSI_C -DLINUX -fno-builtin +CFLAGS = -I$(HFD) $(DEFINES) -g -DBIG_ANSI_C -DLINUX -fno-builtin -fcommon #CFLAGS = -I$(HFD) $(DEFINES) -g -DBIG_ANSI_C -DLINUX \ # -march=$(ARCH) -fno-builtin #CFLAGS = -I. $(DEFINES) -g -DBIG_ANSI_C -DLINUX -Os -fno-builtin
Bug#973171: marked as done (dhcpcanon: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.9 3.8" returned exit code 13)
Your message dated Wed, 16 Dec 2020 17:18:50 +
with message-id
and subject line Bug#973171: fixed in scapy 2.4.4-3
has caused the Debian Bug report #973171,
regarding dhcpcanon: FTBFS: dh_auto_test: error: pybuild --test --test-pytest
-i python{version} -p "3.9 3.8" returned exit code 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.)
--
973171: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973171
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dhcpcanon
Version: 0.8.5-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_build
> I: pybuild base:217: /usr/bin/python3.9 setup.py build
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.9_dhcpcanon/build/dhcpcanon
> copying dhcpcanon/__init__.py ->
> /<>/.pybuild/cpython3_3.9_dhcpcanon/build/dhcpcanon
> copying dhcpcanon/clientscript.py ->
> /<>/.pybuild/cpython3_3.9_dhcpcanon/build/dhcpcanon
> copying dhcpcanon/_version.py ->
> /<>/.pybuild/cpython3_3.9_dhcpcanon/build/dhcpcanon
> copying dhcpcanon/constants.py ->
> /<>/.pybuild/cpython3_3.9_dhcpcanon/build/dhcpcanon
> copying dhcpcanon/conflog.py ->
> /<>/.pybuild/cpython3_3.9_dhcpcanon/build/dhcpcanon
> copying dhcpcanon/dhcpcap.py ->
> /<>/.pybuild/cpython3_3.9_dhcpcanon/build/dhcpcanon
> copying dhcpcanon/dhcpcaplease.py ->
> /<>/.pybuild/cpython3_3.9_dhcpcanon/build/dhcpcanon
> copying dhcpcanon/dhcpcaputils.py ->
> /<>/.pybuild/cpython3_3.9_dhcpcanon/build/dhcpcanon
> copying dhcpcanon/dhcpcapfsm.py ->
> /<>/.pybuild/cpython3_3.9_dhcpcanon/build/dhcpcanon
> copying dhcpcanon/dhcpcanon.py ->
> /<>/.pybuild/cpython3_3.9_dhcpcanon/build/dhcpcanon
> copying dhcpcanon/netutils.py ->
> /<>/.pybuild/cpython3_3.9_dhcpcanon/build/dhcpcanon
> copying dhcpcanon/timers.py ->
> /<>/.pybuild/cpython3_3.9_dhcpcanon/build/dhcpcanon
> running egg_info
> creating dhcpcanon.egg-info
> writing dhcpcanon.egg-info/PKG-INFO
> writing dependency_links to dhcpcanon.egg-info/dependency_links.txt
> writing entry points to dhcpcanon.egg-info/entry_points.txt
> writing requirements to dhcpcanon.egg-info/requires.txt
> writing top-level names to dhcpcanon.egg-info/top_level.txt
> writing manifest file 'dhcpcanon.egg-info/SOURCES.txt'
> reading manifest file 'dhcpcanon.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> no previously-included directories found matching 'docs/build'
> writing manifest file 'dhcpcanon.egg-info/SOURCES.txt'
> I: pybuild base:217: /usr/bin/python3 setup.py build
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.8_dhcpcanon/build/dhcpcanon
> copying dhcpcanon/__init__.py ->
> /<>/.pybuild/cpython3_3.8_dhcpcanon/build/dhcpcanon
> copying dhcpcanon/clientscript.py ->
> /<>/.pybuild/cpython3_3.8_dhcpcanon/build/dhcpcanon
> copying dhcpcanon/_version.py ->
> /<>/.pybuild/cpython3_3.8_dhcpcanon/build/dhcpcanon
> copying dhcpcanon/constants.py ->
> /<>/.pybuild/cpython3_3.8_dhcpcanon/build/dhcpcanon
> copying dhcpcanon/conflog.py ->
> /<>/.pybuild/cpython3_3.8_dhcpcanon/build/dhcpcanon
> copying dhcpcanon/dhcpcap.py ->
> /<>/.pybuild/cpython3_3.8_dhcpcanon/build/dhcpcanon
> copying dhcpcanon/dhcpcaplease.py ->
> /<>/.pybuild/cpython3_3.8_dhcpcanon/build/dhcpcanon
> copying dhcpcanon/dhcpcaputils.py ->
> /<>/.pybuild/cpython3_3.8_dhcpcanon/build/dhcpcanon
> copying dhcpcanon/dhcpcapfsm.py ->
> /<>/.pybuild/cpython3_3.8_dhcpcanon/build/dhcpcanon
> copying dhcpcanon/dhcpcanon.py ->
> /<>/.pybuild/cpython3_3.8_dhcpcanon/build/dhcpcanon
> copying dhcpcanon/netutils.py ->
> /<>/.pybuild/cpython3_3.8_dhcpcanon/build/dhcpcanon
> copying dhcpcanon/timers.py ->
> /<>/.pybuild/cpython3_3.8_dhcpcanon/build/dhcpcanon
> running egg_info
> writing dhcpcanon.egg-info/PKG-INFO
> writing dependency_links to dhcpcanon.egg-info/dependency_links.txt
> writing entry points to dhcpcanon.egg-info/entry_points.txt
> writing requirements to dhcpcanon.egg-info/requires.txt
> writing top-level names to dhcpcanon.egg-info/top_level.txt
> reading manifest file 'dhcpcanon.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> no previously-included directories found matching 'docs/build'
> writing manifest file 'dhcpcanon.egg-info/SOURCES.txt'
> PYTHONPATH=. sphinx-build -N -bhtml docs/source/ build/html # HTML generator
> Running Sphinx v3.2.1
> making output directory... done
> WARNING: html_static
Bug#975845: marked as done (ruby-redis: FTBFS: ERROR: Test "ruby2.7" failed.)
Your message dated Wed, 16 Dec 2020 17:04:41 + with message-id and subject line Bug#975845: fixed in ruby-redis 4.2.5-1 has caused the Debian Bug report #975845, regarding ruby-redis: FTBFS: ERROR: Test "ruby2.7" failed. to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 975845: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975845 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-redis Version: 4.2.2-2 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201125 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /usr/bin/ruby2.7 /usr/bin/gem2deb-test-runner > > ┌──┐ > │ Checking Rubygems dependency resolution on ruby2.7 > │ > └──┘ > > GEM_PATH=/<>/debian/ruby-redis/usr/share/rubygems-integration/all:/<>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/2.7.0:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0 > ruby2.7 -e gem\ \"redis\" > > ┌──┐ > │ Run tests for ruby2.7 from debian/ruby-tests.rake > │ > └──┘ > > RUBYLIB=. > GEM_PATH=/<>/debian/ruby-redis/usr/share/rubygems-integration/all:/<>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/2.7.0:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0 > ruby2.7 -S rake -f debian/ruby-tests.rake > /usr/bin/ruby2.7 -w -I"test" > "/usr/share/rubygems-integration/all/gems/rake-13.0.1/lib/rake/rake_test_loader.rb" > "test/bitpos_test.rb" "test/blocking_commands_test.rb" "test/client_test.rb" > "test/cluster_abnormal_state_test.rb" > "test/cluster_blocking_commands_test.rb" > "test/cluster_client_internals_test.rb" > "test/cluster_client_key_hash_tags_test.rb" > "test/cluster_client_options_test.rb" > "test/cluster_client_pipelining_test.rb" > "test/cluster_client_replicas_test.rb" "test/cluster_client_slots_test.rb" > "test/cluster_client_transactions_test.rb" > "test/cluster_commands_on_cluster_test.rb" > "test/cluster_commands_on_connection_test.rb" > "test/cluster_commands_on_geo_test.rb" > "test/cluster_commands_on_hashes_test.rb" > "test/cluster_commands_on_hyper_log_log_test.rb" > "test/cluster_commands_on_keys_test.rb" > "test/cluster_commands_on_lists_test.rb" > "test/cluster_commands_on_pub_sub_test.rb" > "test/cluster_commands_on_scripting_test.rb" > "test/cluster_commands_on_server_test.rb" > "test/cluster_commands_on_sets_test.rb" > "test/cluster_commands_on_sorted_sets_test.rb" > "test/cluster_commands_on_streams_test.rb" > "test/cluster_commands_on_strings_test.rb" > "test/cluster_commands_on_transactions_test.rb" > "test/cluster_commands_on_value_types_test.rb" "test/command_map_test.rb" > "test/commands_on_geo_test.rb" "test/commands_on_hashes_test.rb" > "test/commands_on_hyper_log_log_test.rb" "test/commands_on_lists_test.rb" > "test/commands_on_sets_test.rb" "test/commands_on_sorted_sets_test.rb" > "test/commands_on_streams_test.rb" "test/commands_on_strings_test.rb" > "test/commands_on_value_types_test.rb" "test/connection_handling_test.rb" > "test/connection_test.rb" "test/distributed_blocking_commands_test.rb" > "test/distributed_commands_on_hashes_test.rb" > "test/distributed_commands_on_hyper_log_log_test.rb" > "test/distributed_commands_on_lists_test.rb" > "test/distributed_commands_on_sets_test.rb" > "test/distributed_commands_on_sorted_sets_test.rb" > "test/distributed_commands_on_strings_test.rb" > "test/distributed_commands_on_value_types_test.rb" > "test/distributed_commands_requiring_clustering_test.rb" > "test/distributed_connection_handling_test.rb" > "test/distributed_internals_test.rb" "test/distributed_key_tags_test.rb" > "test/distributed_persistence_control_commands_test.rb" > "test/distributed_publish_subscribe_test.rb" > "test/distributed_remote_server_control_comm
Processed: Bug#970580 marked as pending in licenseutils
Processing control commands: > tag -1 pending Bug #970580 [licenseutils] licenseutils: Memory access error Added tag(s) pending. -- 970580: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970580 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#970580: marked as pending in licenseutils
Control: tag -1 pending Hello, Bug #970580 in licenseutils 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/debian/licenseutils/-/commit/094384f75e270a30cf9cd58f60065585d2b02cd0 Add patch to prevent a segfault when trying to download license files that have been redirected Closes: #970580 Thanks: handsome_feng for the patch Signed-off-by: Mattia Rizzolo (this message was generated automatically) -- Greetings https://bugs.debian.org/970580
Bug#977551: gprbuild's autopkg tests fail
Package: src:gprbuild Version: 2021.0.0.0778b109-3 Severity: serious Tags: sid bullseye two tests fail: autopkgtest [18:06:29]: test gpr-wrapper: [--- ==Messages for file: /tmp/autopkgtest-lxc.a8l7fm0h/downtmp/autopkgtest_tmp/p.gpr 1. with "gpr.gpr"; | >>> imported project file "gpr.gpr" not found gprbuild: "p.gpr" processing failed autopkgtest [18:06:30]: test gpr-wrapper: ---] autopkgtest [18:06:30]: test gpr-wrapper: - - - - - - - - - - results - - - - - - - - - - gpr-wrapper FAIL non-zero exit status 4 autopkgtest [18:06:30]: test gpr-wrapper: - - - - - - - - - - stderr - - - - - - - - - - gprbuild: "p.gpr" processing failed autopkgtest [18:07:44]: test examples: [--- cp: cannot stat '/usr/share/doc/gprbuild/examples': No such file or directory autopkgtest [18:07:46]: test examples: ---] autopkgtest [18:07:46]: test examples: - - - - - - - - - - results - - - - - - - - - - examples FAIL non-zero exit status 1 autopkgtest [18:07:46]: test examples: - - - - - - - - - - stderr - - - - - - - - - - cp: cannot stat '/usr/share/doc/gprbuild/examples': No such file or directory
Bug#977134: marked as done (qtmir-tests: Cannot fulfill the dependencies)
Your message dated Wed, 16 Dec 2020 16:19:36 + with message-id and subject line Bug#977134: fixed in qtmir 0.6.1-5 has caused the Debian Bug report #977134, regarding qtmir-tests: Cannot fulfill the dependencies to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 977134: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977134 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: qtmir-tests Version: 0.6.1-4 Severity: serious The following packages have unmet dependencies: qtmir-tests : Depends: autopilot-qt5 but it is not installable Depends: python3-autopilot but it is not installable Depends: qtdeclarative5-qtmir-plugin but it is not installable --- End Message --- --- Begin Message --- Source: qtmir Source-Version: 0.6.1-5 Done: Mike Gabriel We believe that the bug you reported is fixed in the latest version of qtmir, 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 977...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mike Gabriel (supplier of updated qtmir package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 16 Dec 2020 16:32:50 +0100 Source: qtmir Architecture: source Version: 0.6.1-5 Distribution: unstable Urgency: medium Maintainer: Debian UBports Team Changed-By: Mike Gabriel Closes: 977134 Changes: qtmir (0.6.1-5) unstable; urgency=medium . * debian/control: + Replace D (qtmir-tests): qtdeclarative5-qtmir-plugin by qml-module-qtmir, drop from D (qtmir-tests): autopilot-qt5 and python3-autopilot. (Closes: #977134). + Bump Standards-Version: to 4.5.1. No changes needed. * debian/qtmir-tests.install: + Drop DATADIR/qtmir/benachmarks/* from qtmir-tests bin:pkg. * debian/patches: + Add 2003_disable-benchmarks.patch. No autopilot in Debian, so let's build qtmir without dependency on it (i.e. without benchmarks). Checksums-Sha1: 8120c91d223fd4671a619e613e3574da92bb56c4 3123 qtmir_0.6.1-5.dsc 2ab68a12cca2e2e08a9fecd9a3ada0a8c55fe286 41308 qtmir_0.6.1-5.debian.tar.xz 3ac7ffec57dcf112ba77da8c6e91f77539a3e6b8 15189 qtmir_0.6.1-5_source.buildinfo Checksums-Sha256: 2e5e65991697eb33ba6c0e2e1573ff1e6ca3e89eddb830659c37eeae9d64cf13 3123 qtmir_0.6.1-5.dsc 76244f7c25053dd9bfc032b9d2ad23619e14d8db13ef6f9943f3ae4e336fa84b 41308 qtmir_0.6.1-5.debian.tar.xz a2ea29924b5f982a69e1b08da7b48ad72cf43e5ba1c72fbe3cfb82f1b4d46635 15189 qtmir_0.6.1-5_source.buildinfo Files: 0c9d41dcc522024534b91aff15791df1 3123 libs optional qtmir_0.6.1-5.dsc 7e912bb41d3181f7167206176d170bb5 41308 libs optional qtmir_0.6.1-5.debian.tar.xz aeb072bb077dc2d1e4c368c20bd78137 15189 libs optional qtmir_0.6.1-5_source.buildinfo -BEGIN PGP SIGNATURE- iQJJBAEBCAAzFiEEm/uu6GwKpf+/IgeCmvRrMCV3GzEFAl/aLPcVHHN1bndlYXZl ckBkZWJpYW4ub3JnAAoJEJr0azAldxsxc7cP+wYTBeGZULCOFMxDLCjZS9ZdWDQZ 7zpMr19oclxgxMKkZVQjolUjF/zOxxJUsR/L5DKy1wK90QXzTRaNoL+nM+tFfobi BAd6T9DoClSGPIM/INR8045g4vrbMgew1a1pTL6VOa0Icfhyg6geiPhIij2nM0fq mkUs8HIvDFJHTukz2tBGBLKAK00b0jZo6/bgpmJ+KnBQwxD3iD4ws9w36Kh9PLTI S9nIiox1CWwtpY5zEBilCU9sUGYOrhVvtyNxb631jd2J6nOfytforonwdVKR4TFM MSjaGLZ0v4SQaA511psHcKumZqPo67e/ZYrWmLG9H5xMnMrgPmXv7ID/H0iRSx7w CNkKgVCtBf+1FvkoE5s+CUmjRqHWVqAG9MEcwGRu75GTviundcpwXxDceh6+DTwb jqMfelEmQL6Nhxidk5RVqF/2vufUtjgjx7Ga2t8BCFCnzyapS+hIq+ArIWCwnjat wuWFe4zjXW58PR0S+dpHEo2lss7Fo6USckP4hFHtATQSdvS5+jZh87SBsHSU+gqN KkqjfN/4PXYOqQfXl/tL7z2HSN+F2xJdwfd354lsgANwUw9v6Cl26EmUVY6Xx6h5 5tDTNhpvFqjAp6V5BspsBX3U/IUtuqCSsUcdepnB/TKIycdTk3h+r+4HXDIBhnbe lvh5G6WbRxH+gki8 =i+AZ -END PGP SIGNATURE End Message ---
Processed: bug 976939 is forwarded to https://github.com/golang/go/issues/43222
Processing commands for cont...@bugs.debian.org: > forwarded 976939 https://github.com/golang/go/issues/43222 Bug #976939 [src:golang-golang-x-arch] golang-golang-x-arch: FTBFS on ppc64el (arch:all-only src pkg): dh_auto_test: error: cd obj-powerpc64le-linux-gnu && go test -vet=off -v -p 160 golang.org/x/arch/arm/armasm golang.org/x/arch/arm64/arm64asm golang.org/x/arch/ppc64/ppc64asm golang.org/x/arch/x86/x86asm golang.org/x/arch/x86/x86csv golang.org/x/arch/x86/xeddata returned exit code 1 Set Bug forwarded-to-address to 'https://github.com/golang/go/issues/43222'. > thanks Stopping processing here. Please contact me if you need assistance. -- 976939: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976939 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#977550: libxmlada's autopkg tests fail
Package: src:libxmlada Version: 21.0.0-2 Severity: serious Tags: sid bullseye see at https://ci.debian.net/data/autopkgtest/testing/amd64/libx/libxmlada/8859011/log.gz autopkgtest [19:16:13]: test link-with-shared: [--- gprbuild: raised CONSTRAINT_ERROR : gpr-proc.adb:696 discriminant check failed autopkgtest [19:16:14]: test link-with-shared: ---] autopkgtest [19:16:14]: test link-with-shared: - - - - - - - - - - results - - - - - - - - - - link-with-shared FAIL non-zero exit status 4 autopkgtest [19:16:15]: test link-with-shared: - - - - - - - - - - stderr - - - - - - - - - - gprbuild: raised CONSTRAINT_ERROR : gpr-proc.adb:696 discriminant check failed
Bug#976915: service-wrapper-java: FTBFS on ppc64el: [exec] wrapper.c:(.text+0x3598): undefined reference to `pow'
Le 13/12/2020 à 00:38, Markus Koschany a écrit : > In this case I believe the RC severity is correct because the arch:any or jni > version of the package FTBFS on ppc64el. We should try to fix the problem on > ppc64el or, if upstream doesn't support ppc64el, remove the architecture from > the list of supported architectures in debian/control. As a side note, if we keep getting issues with service-wrapper-java I wonder if we could scrap it, systemd is now able to provide similar auto-restart features for services. Emmanuel Bourg
Bug#977549: bpftrace: all programs fail with Segmentation fault
Package: bpftrace
Version: 0.11.3-3
Severity: grave
Justification: renders package unusable
Any attempt of running bpftrace programs fails on my sid workstation:
$ sudo bpftrace -e 'kprobe:do_nanosleep { printf("PID %d sleeping\n", pid); }'
Two passes with the same argument (-tti) attempted to be registered!
Segmentation fault
The issue isn't limited to kprobes, uprobes fail too:
$ sudo bpftrace -e 'uprobe:/bin/bash:readline { printf("Hello\n") }'
Two passes with the same argument (-tti) attempted to be registered!
Segmentation fault
Even bpftrace -V fails, though with a different error:
$ sudo bpftrace -V
bpftrace v0.11.3
free(): double free detected in tcache 2
Aborted
I'm running linux-image-5.9.0-4-amd64 5.9.11-1 and libllvm11
1:11.0.0-5+b1.
Bug#974210: marked as done (pytorch's autopkg tests fail)
Your message dated Wed, 16 Dec 2020 14:52:04 + with message-id and subject line Bug#974210: fixed in pytorch 1.7.1-1 has caused the Debian Bug report #974210, regarding pytorch's autopkg tests fail to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 974210: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974210 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:pytorch Version: 1.6.0-5 Severity: serious Tags: sid bullseye https://ci.debian.net/packages/p/pytorch these look all like: autopkgtest [23:22:49]: test 41_of_47__pytest__test_namedtensor: cd test/ ; python3 run_test.py -pt -i test_namedtensor -v autopkgtest [23:22:49]: test 41_of_47__pytest__test_namedtensor: [--- Traceback (most recent call last): File "run_test.py", line 17, in from torch.utils import cpp_extension File "/usr/lib/python3/dist-packages/torch/utils/cpp_extension.py", line 8, in import setuptools ModuleNotFoundError: No module named 'setuptools' Please also build the package for all supported python3 versions. --- End Message --- --- Begin Message --- Source: pytorch Source-Version: 1.7.1-1 Done: Mo Zhou We believe that the bug you reported is fixed in the latest version of pytorch, 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 974...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mo Zhou (supplier of updated pytorch 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, 16 Dec 2020 20:58:19 +0800 Source: pytorch Architecture: source Version: 1.7.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Deep Learning Team Changed-By: Mo Zhou Closes: 974210 977533 Changes: pytorch (1.7.1-1) unstable; urgency=medium . * New upstream version 1.7.1 * Disable OpenMPI in the distributed functionality of pytorch. + Regenerate Autopkgtest control file after removing OpenMPI support. + Explicitly specify USE_MPI=OFF in d/rules. * Add missing runtime deps to autopkgtest and refresh. - Autopkgtest: allow several tests to fail. (Closes: #974210) + Revamp of the python part of autopkgtest and add the missing B-Ds. * Get rid of the symbols control file. (Closes: #977533) Checksums-Sha1: acbdd2160b93b77ff1541ba4ac345edd9c1d1629 3040 pytorch_1.7.1-1.dsc 02b3d412b055abd1184c30eacb988980677d93b5 13012087 pytorch_1.7.1.orig.tar.gz e62313647c2597a7d411fa8de06706d3f1c83253 55072 pytorch_1.7.1-1.debian.tar.xz edd45d8eb0756af8ed7521c336b62c7ec3cc0823 20461 pytorch_1.7.1-1_source.buildinfo Checksums-Sha256: 893ac766299d6b2b48880fd728bd66d33d2ddebd8c46d4b4964239a3b898eee1 3040 pytorch_1.7.1-1.dsc fc8d6aaf0bdedd4221617be8d47ac39af57605bdcc814fabc28739427b55e9c7 13012087 pytorch_1.7.1.orig.tar.gz 68308c34c764693708f56171a790c994e339c4f194794e52113ee64147d620c0 55072 pytorch_1.7.1-1.debian.tar.xz f95fffc23177f8723761328cfdb3b2239a1272a839b79e417a028ab4b019b5e1 20461 pytorch_1.7.1-1_source.buildinfo Files: 242bc7b6f9a14995ade211c8602b4f57 3040 science optional pytorch_1.7.1-1.dsc d534e1eeb3d806d5f75b75b25d18a331 13012087 science optional pytorch_1.7.1.orig.tar.gz dd3c3b642b247f28857be786b1ab6bb8 55072 science optional pytorch_1.7.1-1.debian.tar.xz ce9f91b210aa26a63a892db9260e4759 20461 science optional pytorch_1.7.1-1_source.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEEY4vHXsHlxYkGfjXeYmRes19oaooFAl/aCsoRHGx1bWluQGRl Ymlhbi5vcmcACgkQYmRes19oaopq8g/+OtqKjtnbNFT81s66TZ4i/MneaTix5Avc i0kjRNumklhh63nF42O5qvc8Z5CjgKYJ/2MPXR0euE7wuVUySSw+W7RsY3qOGw2i SaAfSeajqmFsNpKFvRQlUyoFYINlYBzTu96SPfaKYo9Jp+5FLrvJaZso6XpXCTPk m0ERjuWdy6z/F5hugHl7tZGYmsAwEvKpJs1rKoueqqFAtMQsN8UBT6lu0L7OoPup nKsUclr7a/0UWEWSBBxNuCkDyJp63xZU6ujBElKWRIcxXuOwXIgGKGXybI1/OeOn vyxPuKRkbrcDncstX8pmlhUtg620PZQI8AIREtcDKgsTJ0KKrcVpTtEuC9hMyfNt N4VIR2JEMu4vOuU8qIQ1VvzOh+Mh2ba+iUfhREzQI6MMWydJd2tAEcWc37u4suK0 giKBoJYy9iROL5Ra/+rvW/8U5L4VxAKZNSqMLYnLKrQ7qz59s4EGt4xmLoEj9hjV n8x5b2bAmBtv6XD7Oju5DXyRGx7y5A3T8VLleJI9d2f7TcUgMl0nQJRtLOZdd/7K 3zoZ3uffK7zHD9uM0gEAiqIgOvGrWGN5wFLg+kM31Xk2ymCmjhzlKTDkI2xWoLg+ r2NIGKLiPaayI7EJ4naoTwcHE8O7mYBpXx/yfQtyAUkIfxluRCZxoXR0m0V26gMx nY
Processed: severity of 976926 is important
Processing commands for cont...@bugs.debian.org: > severity 976926 important Bug #976926 [src:golang-github-coreos-bbolt] golang-github-coreos-bbolt: FTBFS on ppc64el (arch:all-only src pkg): dh_auto_test: error: cd obj-powerpc64le-linux-gnu && go test -vet=off -v -p 160 -short go.etcd.io/bbolt returned exit code 1 Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 976926: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976926 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#976926: golang-github-coreos-bbolt: FTBFS on ppc64el (arch:all-only src pkg): dh_auto_test: error: cd obj-powerpc64le-linux-gnu && go test -vet=off -v -p 160 -short go.etcd.io/bbolt returned exit
Control: severity -1 import On Sun, Dec 13, 2020 at 2:15 AM Andreas Henriksson wrote: > > Hello! > > On Wed, Dec 09, 2020 at 10:03:39AM +0100, Lucas Nussbaum wrote: > > Source: golang-github-coreos-bbolt > > Version: 1.3.5-1 > > Severity: serious > > Justification: FTBFS on ppc64el > > Tags: bullseye sid ftbfs > > Usertags: ftbfs-20201209 ftbfs-bullseye ftbfs-ppc64el > > > > Hi, > > > > During a rebuild of all packages in sid, your package failed to build > > on ppc64el. At the same time, it did not fail on amd64. > [...] > > > === RUN TestBucket_Stats > > > bucket_test.go:1222: unexpected BranchPageN: 0 > > > --- FAIL: TestBucket_Stats (9.56s) > [...] > > Apparently bbolt is a fork of boltdb, so please see my comments > on the equivalent bug report againt boltdb: > https://bugs.debian.org/976907 > > > Relevant part: > It seems the test-suite makes assumptions related to calculations that > involve os.Getpagesize() (which gives 4096 on amd64 and 65536 on > ppc64el, which is 16 times larger). > Changing the 500 number to 8000 (16 times larger) in > TestBucket_Stats(...) (in bucket_test.go:1143) gives the expected > BranchPageN == 1 (however after that it then says > "unexpected LeafPageN: 6" with this modification). > > In my opinion it's pretty clear that these are test-suite only > issues and not issues in the actual product. > > > I would thus personally just disable the test-suite on !amd64 if no > porter is interested in fixing the testsuite (unless we agree this > issue simply can be downgraded to non-RC). I prefer to downgrade the severity. Just the test, not the library itself is broken. -- Shengjing Zhu
Bug#976918: memkind: FTBFS on ppc64el: GetArenaTest.test_TC_MEMKIND_ThreadHash failed
On Wed, Dec 09, 2020 at 01:27:11PM +0100, Adam Borowski wrote: > On Wed, Dec 09, 2020 at 09:39:08AM +0100, Lucas Nussbaum wrote: > > Source: memkind > > Version: 1.10.1-1 > > > During a rebuild of all packages in sid, your package failed to build > > on ppc64el. At the same time, it did not fail on amd64. > > > [ RUN ] GetArenaTest.test_TC_MEMKIND_ThreadHash > > > test/get_arena_test.cpp:67: Failure > > > Expected: (max_collisions) <= (collisions_limit), actual: 10 vs 5 > > > [ FAILED ] GetArenaTest.test_TC_MEMKIND_ThreadHash (184 ms) > > I can't seem to reproduce, both on plummer (ppc64el, 16 threads) and at home > (amd64, 64 threads); ran 10 and 20 attempts respectively. Hi Lucas! Is that fail reproducible for you? I have a possible fix, but have no way of verifying it -- the package builds successfully on all machines I have access to, and did build fine on buildds (no major changes to toolchain since then). Meow! -- ⢀⣴⠾⠻⢶⣦⠀ .--[ Makefile ] ⣾⠁⢠⠒⠀⣿⡁ # beware of races ⢿⡄⠘⠷⠚⠋⠀ all: pillage burn ⠈⠳⣄ `
Bug#977235: marked as done (sentencepiece FTBFS on armel/mipsel: undefined reference to `__atomic_fetch_add_8')
Your message dated Wed, 16 Dec 2020 12:56:36 + with message-id and subject line Bug#977235: fixed in sentencepiece 0.1.94-2 has caused the Debian Bug report #977235, regarding sentencepiece FTBFS on armel/mipsel: undefined reference to `__atomic_fetch_add_8' 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.) -- 977235: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977235 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: sentencepiece Version: 0.1.94-1 Severity: serious Tags: ftbfs patch https://buildd.debian.org/status/package.php?p=sentencepiece ... /usr/bin/c++ -O3 -Wall -fPIC -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-z,now -rdynamic CMakeFiles/spm_export_vocab.dir/spm_export_vocab_main.cc.o -o spm_export_vocab -Wl,-rpath,/<>/obj-arm-linux-gnueabi/src: libsentencepiece.so.0.0.0 -lpthread /usr/bin/ld: libsentencepiece.so.0.0.0: undefined reference to `__atomic_fetch_add_8' collect2: error: ld returned 1 exit status make[4]: *** [src/CMakeFiles/spm_export_vocab.dir/build.make:107: src/spm_export_vocab] Error 1 Fix/Workaround: --- debian/rules.old2020-12-12 21:58:13.187467694 + +++ debian/rules2020-12-12 21:59:46.848833951 + @@ -12,6 +12,9 @@ DPKG_EXPORT_BUILDFLAGS = 1 include /usr/share/dpkg/buildflags.mk +ifneq (,$(filter $(DEB_HOST_ARCH), armel mipsel m68k powerpc sh4)) + export DEB_LDFLAGS_MAINT_APPEND += -Wl,--no-as-needed -latomic -Wl,--as-needed +endif %: dh $@ --with python3 --buildsystem=cmake --- End Message --- --- Begin Message --- Source: sentencepiece Source-Version: 0.1.94-2 Done: Kentaro Hayashi We believe that the bug you reported is fixed in the latest version of sentencepiece, 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 977...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Kentaro Hayashi (supplier of updated sentencepiece package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 16 Dec 2020 21:18:15 +0900 Source: sentencepiece Architecture: source Version: 0.1.94-2 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Kentaro Hayashi Closes: 977235 Changes: sentencepiece (0.1.94-2) unstable; urgency=medium . * Fix FTBFS on armel/mipsel (Closes: #977235) Checksums-Sha1: 66fdf2e2236e1054f27474eaaae9d97a24efa6a8 2357 sentencepiece_0.1.94-2.dsc db85fceaca9dac65df1f5aee9d768de6331065d8 9180 sentencepiece_0.1.94-2.debian.tar.xz cb2c78c1c1d77dda1b7ae4aaca339739fa7649d6 8499 sentencepiece_0.1.94-2_source.buildinfo Checksums-Sha256: cf8c1f4d3d5346c46cad18e58f5883675c1b415232a8841520c722f8eeb7646b 2357 sentencepiece_0.1.94-2.dsc 22cec5b16f2b9b87ca3b2ec680a88b10c1ae6d3009ccae521d8d1a105864922e 9180 sentencepiece_0.1.94-2.debian.tar.xz 60da371f5eecf9aab6e3a65a0ebf356265560de20f824e639a63b0814dd64752 8499 sentencepiece_0.1.94-2_source.buildinfo Files: 7814afb2ee56d45f61e015c450c90749 2357 science optional sentencepiece_0.1.94-2.dsc c11c49a658e5e35bf0a004503b9e6cde 9180 science optional sentencepiece_0.1.94-2.debian.tar.xz 079e4f985cd09d6c9ba09a2ce95af8cd 8499 science optional sentencepiece_0.1.94-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEcZ6y2T2+nE0h+6Bk9/t1xWbtIOMFAl/Z/iMACgkQ9/t1xWbt IOPXOw/9FK3nBfAl58tYeyOXTTuqWDllIpFQEHOVmGyhw39mN2f+P+z9RnSJP71J GJllmz9MOvLeAgtoRQmyXcIrt7c8dH1HBnyH6tnTbqOVN1ZsoirU5+0DVqbUVTJs KEGLcazKvH9ALN6SsHwv8+CCMAmCwDrUqBphqmzX0PGOWdxYgBLmjEiQf/bGi1Qu 9gQV/L/0XeczXF2NF9fm4Zi30V2NijZ4ERWLmUmRtwvO1FeowRZLjOSR6qsT0tFc DAHGltjVI2o+Vp4a1+W757FsWMQ0Gkam4EZe6X/D63E1cvJUvUFgafU1WURid3mG gSI0P098PP2NkVyIRX7+k9jAZ9BplKvVtR36SEPK7TWKk8WVzvOdLGaUAGUmpV/N Vq0cDvssGIXMn4k1+I5cIspahiosW4G/heKCk50+FtBleiEZfh+DLOj8KtZ5ndjn ZLpOCYaAK/2m61/tsA3s6ZC1cFipqumBInHv8ld+LIiiO3YP97FzUwCArzVixkN+ hZm1iE8caiJb+DfiQ0f3YIkAdvegAtmkOJ00uaGKVurbxYjKj5MdVGkG9fzi+Trb EKgpjub/EKTWvenuV28AoAsROd3RCLCpkz3f2JUmV5m+OnoSQe4id1wGsC55XLzF ibBnnMlbd2VJXwI8gTxo7dlKI9aKr/dHj1iBIUWN+YSbUsQBI/4= =g8Bz -END PGP SIGNATURE End Message ---
Processed: tagging 975242
Processing commands for cont...@bugs.debian.org: > # reproducible in buster but not in stretch > tags 975242 + buster bullseye sid Bug #975242 [openjade] segfault on all architectures if recompiled as of today Added tag(s) bullseye, buster, and sid. > thanks Stopping processing here. Please contact me if you need assistance. -- 975242: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975242 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: re: mrpt: ftbfs with libjsoncpp 1.9.4
Processing commands for cont...@bugs.debian.org:
> notfound 976420 1:12.1.4-1
Bug #976420 {Done: =?utf-8?q?Jos=C3=A9_Luis_Blanco_Claraco?=
} [src:mrpt] mrpt: ftbfs with libjsoncpp/experimental
The source 'mrpt' and version '1:12.1.4-1' do not appear to match any binary
packages
No longer marked as found in versions mrpt/1:12.1.4-1.
> found 976420 1:2.1.4-1
Bug #976420 {Done: =?utf-8?q?Jos=C3=A9_Luis_Blanco_Claraco?=
} [src:mrpt] mrpt: ftbfs with libjsoncpp/experimental
Marked as found in versions mrpt/1:2.1.4-1.
> close 976420 1:2.1.5-1
Bug #976420 {Done: =?utf-8?q?Jos=C3=A9_Luis_Blanco_Claraco?=
} [src:mrpt] mrpt: ftbfs with libjsoncpp/experimental
Ignoring request to alter fixed versions of bug #976420 to the same values
previously set
Bug #976420 {Done: =?utf-8?q?Jos=C3=A9_Luis_Blanco_Claraco?=
} [src:mrpt] mrpt: ftbfs with libjsoncpp/experimental
Bug 976420 is already marked as done; not doing anything.
> retitle 976420 mrpt: ftbfs with libjsoncpp 1.9.4
Bug #976420 {Done: =?utf-8?q?Jos=C3=A9_Luis_Blanco_Claraco?=
} [src:mrpt] mrpt: ftbfs with libjsoncpp/experimental
Changed Bug title to 'mrpt: ftbfs with libjsoncpp 1.9.4' from 'mrpt: ftbfs with
libjsoncpp/experimental'.
> severity 976420 serious
Bug #976420 {Done: =?utf-8?q?Jos=C3=A9_Luis_Blanco_Claraco?=
} [src:mrpt] mrpt: ftbfs with libjsoncpp 1.9.4
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
976420: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976420
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#975705: marked as pending in cura
https://salsa.debian.org/3dprinting-team/cura/-/commit/871fcb258aa11077c3a6e16651fbcb44953e932e did not build cf. https://salsa.debian.org/3dprinting-team/cura/-/pipelines/205268 Best regards Heinrich
Bug#975843: marked as done (sopt: FTBFS: core.h:270: undefined reference to `fmt::v6::internal::assert_fail(char const*, int, char const*)')
Your message dated Wed, 16 Dec 2020 09:33:53 + with message-id and subject line Bug#975843: fixed in sopt 3.0.1-11 has caused the Debian Bug report #975843, regarding sopt: FTBFS: core.h:270: undefined reference to `fmt::v6::internal::assert_fail(char const*, int, char const*)' 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.) -- 975843: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975843 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: sopt Version: 3.0.1-10 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201125 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /usr/bin/ld: CMakeFiles/common_catch_main_object.dir/common_catch_main.cc.o: > in function `std::make_unsigned::type > fmt::v6::internal::to_unsigned(long)': > /usr/include/fmt/core.h:270: undefined reference to > `fmt::v6::internal::assert_fail(char const*, int, char const*)' > /usr/bin/ld: warning: creating DT_TEXTREL in a PIE > collect2: error: ld returned 1 exit status The full build log is available from: http://qa-logs.debian.net/2020/11/25/sopt_3.0.1-10_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Source: sopt Source-Version: 3.0.1-11 Done: Ole Streicher We believe that the bug you reported is fixed in the latest version of sopt, 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 975...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ole Streicher (supplier of updated sopt 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, 16 Dec 2020 10:00:24 +0100 Source: sopt Architecture: source Version: 3.0.1-11 Distribution: unstable Urgency: medium Maintainer: Debian Astro Team Changed-By: Ole Streicher Closes: 975843 Changes: sopt (3.0.1-11) unstable; urgency=medium . [ Shengjing Zhu ] * Add patch to fix FTBFS with spdlog (Closes: #975843) . [ Ole Streicher ] * Fix e-mail address of uploader for 3.0.1-9 * Push Standards-Version to 4.5.1. No changes needed * Push dh-compat to 13 * Add "Rules-Requires-Root: no" to d/control * Use Expat short name instead MIT in d/copyright Checksums-Sha1: 2a32bc35dad848ca3a7d0df5c5df28d14216e754 2101 sopt_3.0.1-11.dsc 1a0e25ffcc2d5c231b83c6e8480bd599ffed71b6 8240 sopt_3.0.1-11.debian.tar.xz Checksums-Sha256: bd2c0c97259eb526e619a6b3887d7172fe00ca97acc0b35bc8d56af7bba5ada8 2101 sopt_3.0.1-11.dsc 989ddfcefde749638b97f0cafcf267b21db0e0f5042e829ae98473d82e3964f5 8240 sopt_3.0.1-11.debian.tar.xz Files: 4fb63ffaf5901e9276cf328c91d3f4da 2101 science optional sopt_3.0.1-11.dsc 34795e16dd65951cb9589b06d75e79a7 8240 science optional sopt_3.0.1-11.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEuvxshffLFD/utvsVcRWv0HcQ3PcFAl/Z0KYACgkQcRWv0HcQ 3PfYVg/9FnElzvXdxCCMNBiSxq8uYvNuyQTKQp41ugFumOtOZ66G5zzQCVFVkCij yPNsUR8koDml3087fwn6FBluq82mikS2ry/1hh/NQHY6L0DMQEaxjkRBUgNzwWDb KluhTCwfMJoCj+r+bAYxm9zTmLg7BI92cz3O8b5ym8c7+2s2KazOtUqXIK57UphN 1iBaCyvvqr4h6CiX+H7rEtV7TP92uyJBf1ROEsUd/fz3ZyWtzJQZI275lj/qQ+Xa YrpjOxDBMcMLVlJluUWaCCb4bAoyYirQDEiaecLj18PICvlzwUgBTUbgDIP3WC3P BkpRmxCKGLP4ap7GXfddvpo+U8tgo1BtiO0508K9V3q8rWryfsSN54reZck4ZMb7 Tis1Uf4rxwhB1rmZhuKy8R8DBG3A4LX8Fs8xHjfdBNq+eReDReJvBi5+lD7ZmbXB dT3uhDkeePojCwyM7zB2rfqklq7OyT000N+c8nMt7gaqAXsA2HOPhkDk4GlZWg6x Vu55ZXnIlRDAvZnZnPP6EW75p9alT2SIWRwmbDyaKvDBqxiEpRi6DKA7CesGncmY baj/vGwLkfEYflAgJa8G4C3YctgQMxo+AKGKYH6nV04Md7wXXqf56l0MmOlscRDj T9qof8r6MZbganDyZmO4cBS2+DxLh/bAyRpxg5RT1DRLuCkV5eU= =ClMs -END PGP SIGNATURE End Message ---
Bug#973605: marked as done (odoo: Multiple privacy-breach-generic (fetching data from an external website at runtime))
Your message dated Wed, 16 Dec 2020 08:39:40 +
with message-id
and subject line Bug#973605: fixed in odoo 14.0.0+dfsg.2-1
has caused the Debian Bug report #973605,
regarding odoo: Multiple privacy-breach-generic (fetching data from an external
website at runtime)
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.)
--
973605: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973605
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: odoo
Version: 14.0.0+dfsg-1
Severity: serious
Here's the corresponding lintian excerpt:
W: odoo: privacy-breach-generic
usr/lib/python3/dist-packages/odoo/addons/digest/data/digest_data.xml [https://www.odoo.com/digest/static/src/img/google_play.png"; />]
(https://www.odoo.com/digest/static/src/img/google_play.png)
W: odoo: privacy-breach-generic
usr/lib/python3/dist-packages/odoo/addons/digest/data/digest_data.xml [https://www.odoo.com/web/image/24717933/odoo-mobile.png"; alt="odoo mobile"
/>] (https://www.odoo.com/web/image/24717933/odoo-mobile.png)
W: odoo: privacy-breach-generic
usr/lib/python3/dist-packages/odoo/addons/event/data/email_template_data.xml
[http://maps.googleapis.com/maps/api/staticmap?autoscale=1&size=598x200&maptype=roadmap&format=png&visual_refresh=true&markers=size:mid%7ccolor:0xa5117d%7clabel:%7c${location}";
style="vertical-align:bottom; width: 100%;" alt="google maps"/>]
(http://maps.googleapis.com/maps/api/staticmap?autoscale=1&size=598x200&maptype=roadmap&format=png&visual_refresh=true&markers=size:mid%7ccolor:0xa5117d%7clabel:%7c${location})
W: odoo: privacy-breach-generic
usr/lib/python3/dist-packages/odoo/addons/survey/data/survey_demo_quiz.xml
[]
(//www.youtube.com/embed/7y4t6yv5l1k?autoplay=0&rel=0)
W: odoo: privacy-breach-generic
usr/lib/python3/dist-packages/odoo/addons/test_assetsbundle/views/views.xml
[http://test.external.link/style1.css"/>]
(http://test.external.link/style1.css)
W: odoo: privacy-breach-generic
usr/lib/python3/dist-packages/odoo/addons/test_assetsbundle/views/views.xml
[http://test.external.link/style2.css"/>]
(http://test.external.link/style2.css)
W: odoo: privacy-breach-generic
usr/lib/python3/dist-packages/odoo/addons/test_assetsbundle/views/views.xml
[
