Bug#998892: marked as done (vdr-plugin-fritzbox: Please drop the stale build dependency on libcommoncpp2-dev)
Your message dated Wed, 22 Dec 2021 07:34:16 + with message-id and subject line Bug#998892: fixed in vdr-plugin-fritzbox 1.5.4-1 has caused the Debian Bug report #998892, regarding vdr-plugin-fritzbox: Please drop the stale build dependency on libcommoncpp2-dev to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 998892: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998892 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: vdr-plugin-fritzbox Version: 1.5.3-9 Severity: serious Tags: bookworm sid Control: block 984096 by -1 Control: block 998889 by -1 vdr-plugin-fritzbox is the only remaining package build depending on libcommoncpp2-dev, but HISTORY says: 2013-12-01: Version 1.5.3 - New dependency boost::asio, dropped dependency to commoncpp Please drop the stale build dependency on libcommoncpp2-dev. Severity of this bug is RC since libcommoncpp2 will likely soon be removed from testing. --- End Message --- --- Begin Message --- Source: vdr-plugin-fritzbox Source-Version: 1.5.4-1 Done: Tobias Grimm We believe that the bug you reported is fixed in the latest version of vdr-plugin-fritzbox, 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 998...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Tobias Grimm (supplier of updated vdr-plugin-fritzbox 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, 20 Dec 2021 16:27:39 +0100 Source: vdr-plugin-fritzbox Architecture: source Version: 1.5.4-1 Distribution: unstable Urgency: medium Maintainer: Debian VDR Team Changed-By: Tobias Grimm Closes: 933084 998892 Changes: vdr-plugin-fritzbox (1.5.4-1) unstable; urgency=medium . [ Helmut Grohne ] * Fix FTCBFS: Use the host architecture pkg-config. (Closes: #933084) . [ Tobias Grimm ] * New upstream version 1.5.4 * Drop libcommoncpp2-dev build dependency (Closes: #998892) * Update patches * Disable building tests * Update debian/watch to version 4 Checksums-Sha1: 755378007bf6a21c50d98212d17082a37ed14ea2 2214 vdr-plugin-fritzbox_1.5.4-1.dsc 7b7d64a5837e6595b77ca503a15ecfcb1c01090f 1072094 vdr-plugin-fritzbox_1.5.4.orig.tar.gz f211f4512f74654edfcc94ea73b19412aef919c9 4720 vdr-plugin-fritzbox_1.5.4-1.debian.tar.xz 43f78f120fde1c879ed6f772e8e752e5975b79ba 6923 vdr-plugin-fritzbox_1.5.4-1_amd64.buildinfo Checksums-Sha256: 60b25c5df639e4836e5a9f55f96a48c117d0159ebe8bb2db9a21f8f4092b8f8a 2214 vdr-plugin-fritzbox_1.5.4-1.dsc 115c9711e259beb05c648d71ded345748efee44280e79a34c3ef77017c97e75b 1072094 vdr-plugin-fritzbox_1.5.4.orig.tar.gz bce962cf5b2c45e3b3ad18317ffdcd00332955ee1fad5e666bc4cf4592628c74 4720 vdr-plugin-fritzbox_1.5.4-1.debian.tar.xz b198f5f9bd2540589d73e6dd258ffa2748f419d25ed2754a49cb97959b0252a2 6923 vdr-plugin-fritzbox_1.5.4-1_amd64.buildinfo Files: d73b54726e5f956fb82a11ced5276279 2214 video optional vdr-plugin-fritzbox_1.5.4-1.dsc 1c6b9f692c24302f625c3650d362c275 1072094 video optional vdr-plugin-fritzbox_1.5.4.orig.tar.gz e038403cb692edae826330ec4924e57e 4720 video optional vdr-plugin-fritzbox_1.5.4-1.debian.tar.xz 140ef4d1ec1dd634a1a097a6ef1a8f84 6923 video optional vdr-plugin-fritzbox_1.5.4-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEV6STX5IhiI/eNxSi1i5PWwQTkLwFAmHC0eMACgkQ1i5PWwQT kLyRQw/6A9lgE+AgN4swarILNRmtKkeTCAcb4tJxAqscTD0OyaDvD03WefH7OZ6Y 8BSfRhyYpZ87jlaePaYIpmY0Cgjork6qaxcUw7phDyDN/CoOGNrPBBaNj3RufpBe qWgSw0ghCRuWK5n/cHatJ+9EU+so+Sk7FmgFAvOLS78Y6cZWLiuShh71U5zL7K06 HgIgbRPUbu0mugtnfzL2PbWEcs0+7fA1+bYfWRVhqiK/5Hu59Dmm17Dbi0slcQKp 6ghxi+txn9vJboDY8Z58xCUUGrBjlCD1YJwkxnuF2i3F9FcvlTFt+iOZeX5NOSfV N2AhkYYv/7LP74QbgY+FYe6kdGHtiT2mUJlVAE/c24ZPKVhLMOz7D/dI2v5oQgX/ 7GmDO7eaZ16mtYVTsGCAYF8s/AutAJ0aLT0mB/FZBfaDc7Ktan0Mpz8yTqLy4UYW XHrg1JWcdvzxKyaASvyBJhc+8Lz5sBvXxsSBIrc1mPbnZFOJAVYueXvFo0GhuGbc Che3YPtfUY4h0Ieq6G+CNEU1m6oRpybuGJAk3I5plHQnd46R7pZu6wKBCKjwtSiU hlCFPonNyVelu4OhuZhEdK+uWiWsRxHe1lIG4vkXUDt1X8IM4HKqnwhqX3VG+wxb OF79XZsNieCak1i6k6XwXcDbiboC3NRIYq1rEEMVe/+ZPQ8VscM= =mcg5 -END PGP SIGNATURE End Message ---
Bug#1002312: gnu-smalltalk-browser: Smalltalk browser fails to start
Package: gnu-smalltalk-browser Version: 3.2.5-1.3+b3 Severity: grave Justification: renders package unusable X-Debbugs-Cc: be...@fams.de Dear Maintainer, * What led up to the situation? Tried to run the GNU Smalltalk Browser application. * What exactly did you do (or not do) that was effective (or ineffective)? Installed the gst-smalltalk-browser package and run 'gst-browser' from the command line. * What was the outcome of this action? Got the following error message: a Smalltalk Stream:2: Aborted a Smalltalk Stream:2: Error occurred while not in byte code interpreter!! /lib/libgst.so.7(+0x74607)[0x7f429c214607] /lib/x86_64-linux-gnu/libc.so.6(+0x3cef0)[0x7f429c017ef0] /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x141)[0x7f429c017e71] /lib/x86_64-linux-gnu/libc.so.6(abort+0x112)[0x7f429c001536] /lib/libgst.so.7(+0x10c04)[0x7f429c1b0c04] /lib/x86_64-linux-gnu/libsigsegv.so.2(+0x129c)[0x7f429bfd629c] /lib/x86_64-linux-gnu/libc.so.6(+0x3cef0)[0x7f429c017ef0] /lib/x86_64-linux- gnu/libgobject-2.0.so.0(g_type_check_is_value_type+0x1e)[0x7f427a1d4a7e] /lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0x216bae)[0x7f427a4cbbae] /lib/x86_64-linux- gnu/libgtk-x11-2.0.so.0(gtk_list_store_new+0xa8)[0x7f427a3e8cf8] Aborted Application stopped. * What outcome did you expect instead? Starting the GNU Smalltalk browser. * Other related information. This seems to be to https://stackoverflow.com/questions/52766461/gst-browser- fails-to-start though the bug is different from the ones linked from there. libgtk2.0-dev and libgtk2.0-0 are both installed, which are referenced as a solution to the problem. -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.15.0-2-amd64 (SMP w/12 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gnu-smalltalk-browser depends on: ii gnu-smalltalk 3.2.5-1.3+b3 ii gnu-smalltalk-common 3.2.5-1.3 ii libgtk2-gst 3.2.5-1.3+b3 gnu-smalltalk-browser recommends no packages. gnu-smalltalk-browser suggests no packages. -- no debconf information
Bug#1002251: marked as done (libmessage-passing-zeromq-perl: FTBFS: Can't locate JSON.pm in @INC)
Your message dated Wed, 22 Dec 2021 06:48:29 + with message-id and subject line Bug#1002251: fixed in libmessage-passing-zeromq-perl 0.010-3 has caused the Debian Bug report #1002251, regarding libmessage-passing-zeromq-perl: FTBFS: Can't locate JSON.pm in @INC 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.) -- 1002251: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002251 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libmessage-passing-zeromq-perl Version: 0.010-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211220 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > true > true > true > true > true > true > true > true > true > PERL_DL_NONLAZY=1 "/usr/bin/perl" "-MExtUtils::Command::MM" "-MTest::Harness" > "-e" "undef *Test::Harness::Switches; test_harness(1, 'inc', 'blib/lib', > 'blib/arch')" t/*.t > t/00_compile.t .. > ok 1 - use Message::Passing::ZeroMQ; > ok 2 - use Message::Passing::Input::ZeroMQ; > ok 3 - use Message::Passing::Output::ZeroMQ; > 1..3 > ok > t/input.t ... > ok 1 > ok 2 > ok 3 > 1..3 > ok > Can't locate JSON.pm in @INC (you may need to install the JSON module) (@INC > contains: /<>/inc /<>/blib/lib > /<>/blib/arch /etc/perl > /usr/local/lib/x86_64-linux-gnu/perl/5.32.1 /usr/local/share/perl/5.32.1 > /usr/lib/x86_64-linux-gnu/perl5/5.32 /usr/share/perl5 > /usr/lib/x86_64-linux-gnu/perl-base /usr/lib/x86_64-linux-gnu/perl/5.32 > /usr/share/perl/5.32 /usr/local/lib/site_perl .) at t/output.t line 6. > BEGIN failed--compilation aborted at t/output.t line 6. > t/output.t .. > Dubious, test returned 2 (wstat 512, 0x200) > No subtests run > t/pushpull.t > ok 1 > 1..1 > ok > Can't locate JSON.pm in @INC > BEGIN failed--compilation aborted at t/stress.t line 5. > t/stress.t .. > Dubious, test returned 2 (wstat 512, 0x200) > No subtests run > t/version.t . > ok 1 - ZMQ is a sane major version: 4 > 1..1 > ok > > Test Summary Report > --- > t/output.t(Wstat: 512 Tests: 0 Failed: 0) > Non-zero exit status: 2 > Parse errors: No plan found in TAP output > t/stress.t(Wstat: 512 Tests: 0 Failed: 0) > Non-zero exit status: 2 > Parse errors: No plan found in TAP output > Files=6, Tests=8, 4 wallclock secs ( 0.02 usr 0.01 sys + 0.59 cusr 0.07 > csys = 0.69 CPU) > Result: FAIL > Failed 2/6 test programs. 0/8 subtests failed. > make[1]: *** [Makefile:775: test_dynamic] Error 255 The full build log is available from: http://qa-logs.debian.net/2021/12/20/libmessage-passing-zeromq-perl_0.010-2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: libmessage-passing-zeromq-perl Source-Version: 0.010-3 Done: Damyan Ivanov We believe that the bug you reported is fixed in the latest version of libmessage-passing-zeromq-perl, 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 1002...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Damyan Ivanov (supplier of updated libmessage-passing-zeromq-perl 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, 22 Dec 2021 06:28:30 + Source: libmessage-passing-zeromq-perl Architecture: source Version: 0.010-3 Distribution: unstable Urgency: medium Maintainer: Debian Perl Group Changed-By: Damyan Ivanov Closes: 1002251 Changes: libmessage-passing-zeromq-perl (0.010-3) unstable; urgency=medium . * Team upload . [ Salvatore Bonaccorso ] * Update Vcs-* headers for switch to salsa.debian.org . [ gregor herrmann ] * debian/*:
Processed: bug 987959 is forwarded to https://github.com/merces/libpe/issues/34
Processing commands for cont...@bugs.debian.org:
> forwarded 987959 https://github.com/merces/libpe/issues/34
Bug #987959 {Done: Petter Reinholdtsen } [pev] pev: peres
affected by off-by-one error in libpe
Changed Bug forwarded-to-address to 'https://github.com/merces/libpe/issues/34'
from 'tps://github.com/merces/libpe/issues/34'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
987959: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987959
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1002292: marked as done (node-babel7: ships /usr/share/nodejs/babel-plugin-add-module-exports/*, already in node-babel-plugin-add-module-exports)
Your message dated Wed, 22 Dec 2021 06:21:45 + with message-id and subject line Bug#1002292: fixed in node-babel7 7.16.6+ds1+~cs214.259.181-1 has caused the Debian Bug report #1002292, regarding node-babel7: ships /usr/share/nodejs/babel-plugin-add-module-exports/*, already in node-babel-plugin-add-module-exports 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.) -- 1002292: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002292 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: node-babel7 Version: 7.16.6+~cs215.259.185-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install because it tries to overwrite other packages filea. If node-babel-plugin-add-module-exports is to be merged into node-babel7, please RM it and add corresponding Breaks+Replaces, otherwise use the already packaged copy. >From the attached log (scroll to the bottom...): Preparing to unpack .../node-babel7_7.16.6+~cs215.259.185-2_all.deb ... Unpacking node-babel7 (7.16.6+~cs215.259.185-2) ... dpkg: error processing archive /var/cache/apt/archives/node-babel7_7.16.6+~cs215.259.185-2_all.deb (--unpack): trying to overwrite '/usr/share/nodejs/babel-plugin-add-module-exports/lib/index.js', which is also in package node-babel-plugin-add-module-exports 1.0.4+dfsg1~cs5.8.0-2 Errors were encountered while processing: /var/cache/apt/archives/node-babel7_7.16.6+~cs215.259.185-2_all.deb cheers, Andreas node-babel-plugin-add-module-exports=1.0.4+dfsg1~cs5.8.0-2_node-babel7=7.16.6+~cs215.259.185-2.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: node-babel7 Source-Version: 7.16.6+ds1+~cs214.259.181-1 Done: Yadd We believe that the bug you reported is fixed in the latest version of node-babel7, 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 1002...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yadd (supplier of updated node-babel7 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, 22 Dec 2021 06:45:58 +0100 Source: node-babel7 Binary: node-babel7 node-babel7-runtime node-babel7-standalone Architecture: source all Version: 7.16.6+ds1+~cs214.259.181-1 Distribution: experimental Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Yadd Description: node-babel7 - Babel command line node-babel7-runtime - Babel modular runtime helpers node-babel7-standalone - Standalone build of Babel for use in browsers and other non-Node. Closes: 1002292 Changes: node-babel7 (7.16.6+ds1+~cs214.259.181-1) experimental; urgency=medium . * Team upload * Drop embedded node-babel-plugin-add-module-exports adn repack (Closes: #1002292) Checksums-Sha1: fbc33a55c63840983a7f0ff6ae63130b65a5600c 20961 node-babel7_7.16.6+ds1+~cs214.259.181-1.dsc f13cf6a90208592012f79dba9cc2c4252cab18b0 1936 node-babel7_7.16.6+ds1+~cs214.259.181.orig-babel-check-duplicated-nodes.tar.xz c72b24d90a0f79281d858640d879d86fdde2a5cd 1960 node-babel7_7.16.6+ds1+~cs214.259.181.orig-babel-helper-bindify-decorators.tar.xz 196029444b0a0f27db933481df43dfc8cbe9fa9e 2160 node-babel7_7.16.6+ds1+~cs214.259.181.orig-babel-helper-call-delegate.tar.xz eae8a07e05a996e70afb2fd4e08dce8efccc43ae 23920 node-babel7_7.16.6+ds1+~cs214.259.181.orig-babel-helper-define-polyfill-provider.tar.xz 458b2e3b874303df60e8d2c547d4c56190cf7c6d 2116 node-babel7_7.16.6+ds1+~cs214.259.181.orig-babel-helper-explode-class.tar.xz 140d80a99e6c277276ce53e016800c3d68663f8d 8336 node-babel7_7.16.6+ds1+~cs214.259.181.orig-babel-plugin-dynamic-import-node.tar.xz 7f157868a530016834caa93f70c8f567709d4c34 14944 node-babel7_7.16.6+ds1+~cs214.259.181.orig-babel-plugin-polyfill-corejs2.tar.xz 4163e1f31145e8f51c7a38fbedce56286baf5ed2 24468 node-babel7_7.16.6+ds1+~cs214.259.181.orig-babel-plugin-polyfill-corejs3.tar.xz 295af59006612e95590c83b72837a5d8361a2f15 2700 node-babel7_7.16.6+ds1+~cs214.259.181.orig-babel-plugin-polyfill-regenerator.tar.xz 6aeb3c41f0dd48ed4a30205f0ca73b6a134ed66a 1496
Bug#1002253: marked as done (libatomic-queue: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below)
Your message dated Wed, 22 Dec 2021 06:03:31 + with message-id and subject line Bug#1002253: fixed in libatomic-queue 0.0+git20211209.7db4cea-1 has caused the Debian Bug report #1002253, regarding libatomic-queue: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below 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.) -- 1002253: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002253 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libatomic-queue Version: 0.0+git20201108.d9d66b6-4 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211220 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_strip || true > strip: debian/libatomic-queue-dev/usr/lib/x86_64-linux-gnu/libatomic_queue.a: > sorry: copying thin archives is not currently supported: invalid operation > dh_strip: error: strip --strip-debug --remove-section=.comment > --remove-section=.note --enable-deterministic-archives -R .gnu.lto_\* -R > .gnu.debuglto_\* -N __gnu_lto_slim -N __gnu_lto_v1 > debian/libatomic-queue-dev/usr/lib/x86_64-linux-gnu/libatomic_queue.a > returned exit code 1 > dh_strip: error: Aborting due to earlier error > make[1]: Leaving directory '/<>' >dh_makeshlibs -a > dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols > file: see diff output below > dpkg-gensymbols: warning: debian/libatomic-queue0/DEBIAN/symbols doesn't > match completely debian/libatomic-queue0.symbols > --- debian/libatomic-queue0.symbols > (libatomic-queue0_0.0+git20201108.d9d66b6-4_amd64) > +++ dpkg-gensymbolse_rJT5 2021-12-20 18:33:18.140152038 + > @@ -88,7 +88,7 @@ > > _ZNSt5dequeINSt8__detail9_StateSeqINSt7__cxx1112regex_traitsIcSaIS5_EE12emplace_backIJS5_EEEvDpOT_@Base > 0.0+git20201007.df79403 > > _ZNSt5dequeINSt8__detail9_StateSeqINSt7__cxx1112regex_traitsIcSaIS5_EE16_M_push_back_auxIJRKS5_EEEvDpOT_@Base > 0.0+git20201007.df79403 > > _ZNSt5dequeINSt8__detail9_StateSeqINSt7__cxx1112regex_traitsIcSaIS5_EE17_M_reallocate_mapEmb@Base > 0.0+git20201007.df79403 > - > _ZNSt5dequeINSt8__detail9_StateSeqINSt7__cxx1112regex_traitsIcSaIS5_EE9push_backERKS5_@Base > 0.0+git20201007.df79403 > +#MISSING: 0.0+git20201108.d9d66b6-4# > _ZNSt5dequeINSt8__detail9_StateSeqINSt7__cxx1112regex_traitsIcSaIS5_EE9push_backERKS5_@Base > 0.0+git20201007.df79403 > _ZNSt5dequeIlSaIlEE16_M_push_back_auxIJRKlEEEvDpOT_@Base > 0.0+git20201007.df79403 > > _ZNSt6vectorIN12atomic_queue15CpuTopologyInfoESaIS1_EE17_M_realloc_insertIJRKS1_EEEvN9__gnu_cxx17__normal_iteratorIPS1_S3_EEDpOT_@Base > 0.0+git20201007.df79403 > > _ZNSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EE17_M_realloc_insertIJRKS5_EEEvN9__gnu_cxx17__normal_iteratorIPS5_S7_EEDpOT_@Base > 0.0+git20201007.df79403 > @@ -235,6 +235,6 @@ > _ZZNSt19_Sp_make_shared_tag5_S_tiEvE5__tag@Base 0.0+git20201007.df79403 > #MISSING: 0.0+git20201108.d9d66b6-3# > _ZZNSt8__detail9_CompilerINSt7__cxx1112regex_traitsIcEEE18_M_expression_termILb0ELb0EEEbRSt4pairIbcERNS_15_BracketMatcherIS3_XT_EXT0_NKUlcE_clEc@Base > 0.0+git20201108.d9d66b6 > #MISSING: 0.0+git20201108.d9d66b6-3# > _ZZNSt8__detail9_CompilerINSt7__cxx1112regex_traitsIcEEE18_M_expression_termILb0ELb1EEEbRSt4pairIbcERNS_15_BracketMatcherIS3_XT_EXT0_NKUlcE_clEc@Base > 0.0+git20201108.d9d66b6 > - > _ZZNSt8__detail9_CompilerINSt7__cxx1112regex_traitsIcEEE18_M_expression_termILb1ELb0EEEbRSt4pairIbcERNS_15_BracketMatcherIS3_XT_EXT0_NKUlcE_clEc@Base > 0.0+git20201007.df79403 > - > _ZZNSt8__detail9_CompilerINSt7__cxx1112regex_traitsIcEEE18_M_expression_termILb1ELb1EEEbRSt4pairIbcERNS_15_BracketMatcherIS3_XT_EXT0_NKUlcE_clEc@Base > 0.0+git20201007.df79403 > +#MISSING: 0.0+git20201108.d9d66b6-4# > _ZZNSt8__detail9_CompilerINSt7__cxx1112regex_traitsIcEEE18_M_expression_termILb1ELb0EEEbRSt4pairIbcERNS_15_BracketMatcherIS3_XT_EXT0_NKUlcE_clEc@Base > 0.0+git20201007.df79403 > +#MISSING: 0.0+git20201108.d9d66b6-4# > _ZZNSt8__detail9_CompilerINSt7__cxx1112regex_traitsIcEEE18_M_expression_termILb1ELb1EEEbRSt4pairIbcERNS_15_BracketMatcherIS3_XT_EXT0_NKUlcE_clEc@Base > 0.0+git20201007.df79403 > pthread_create@Base 0.0+git20201007.df79403 > dh_makeshlibs: error: failing due to earlier errors > make: *** [debian/rules:17: binary] Error 25 The full build log is available from:
Processed: unarchiving 987959, bug 987959 is forwarded to tps://github.com/merces/libpe/issues/34 ...
Processing commands for cont...@bugs.debian.org:
> unarchive 987959
Bug #987959 {Done: Petter Reinholdtsen } [pev] pev: peres
affected by off-by-one error in libpe
Unarchived Bug 987959
> forwarded 987959 tps://github.com/merces/libpe/issues/34
Bug #987959 {Done: Petter Reinholdtsen } [pev] pev: peres
affected by off-by-one error in libpe
Set Bug forwarded-to-address to 'tps://github.com/merces/libpe/issues/34'.
> tags 987959 + upstream
Bug #987959 {Done: Petter Reinholdtsen } [pev] pev: peres
affected by off-by-one error in libpe
Added tag(s) upstream.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
987959: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987959
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Bug#1002292 marked as pending in node-babel
Processing control commands: > tag -1 pending Bug #1002292 [node-babel7] node-babel7: ships /usr/share/nodejs/babel-plugin-add-module-exports/*, already in node-babel-plugin-add-module-exports Added tag(s) pending. -- 1002292: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002292 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1002292: marked as pending in node-babel
Control: tag -1 pending Hello, Bug #1002292 in node-babel reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-babel/-/commit/e4e5e5a5a2d21822627e020817584d0aa53b2277 Drop embedded node-babel-plugin-add-module-exports Closes: #1002292 (this message was generated automatically) -- Greetings https://bugs.debian.org/1002292
Bug#1002060: [Debian-zh-dev] Bug#1002060: liblunar-date-doc: missing Breaks+Replaces: liblunar-date-dev (<< 3)
Hi, 在 2021/12/22 02:31, Boyuan Yang 写道: Hi, Using the filename "changelog-upstream" is not a standard practice. Why not just keep using the old filename /usr/share/doc/liblunar-date-dev/changelog? The upstream NEWS file is the upstream changelog in fact, I rename it before: NEWS => usr/share/doc/liblunar-date-dev/changelog At upstream current version, there is no file named Changelog in it's top level directory. But I has a little worry about that upstream add this Changelog file again in the next. If in this situation, rename NEWS to "changelog-upstream" will avoid conflict. As email title said, using Breaks+Replaces: liblunar-date-dev (<< 3) would be enough. Anyway, let's use standard practice at first. Do it in salsa and upload to mentors.d.n, welcome to review and upload. Thanks, -- 肖盛文 xiao sheng wen Faris Xiao 微信(wechat)：atzlinux 《铜豌豆 Linux》https://www.atzlinux.com 基于 Debian 的 Linux 中文 桌面 操作系统 Debian QA page: https://qa.debian.org/developer.php?login=atzlinux%40sina.com GnuPG Public Key: 0x00186602339240CB OpenPGP_0x00186602339240CB.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature
Bug#1000923: marked as done (ghdl: FTBFS with llvm-toolchain-13)
Your message dated Wed, 22 Dec 2021 03:33:31 + with message-id and subject line Bug#1000923: fixed in ghdl 1.0.0+dfsg-6 has caused the Debian Bug report #1000923, regarding ghdl: FTBFS with llvm-toolchain-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.) -- 1000923: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000923 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ghdl Severity: important Dear Maintainer, As part of the effort to limit the number of llvm packages in the archive, it would be great if you could upgrade to -13 (or -12). Bookworm won't ship with llvm-toolchain-11 llvm-defaults is now pointing to -13. Thanks, Sylvestre --- End Message --- --- Begin Message --- Source: ghdl Source-Version: 1.0.0+dfsg-6 Done: Andreas Bombe We believe that the bug you reported is fixed in the latest version of ghdl, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1000...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Bombe (supplier of updated ghdl 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, 22 Dec 2021 03:50:59 +0100 Source: ghdl Architecture: source Version: 1.0.0+dfsg-6 Distribution: unstable Urgency: medium Maintainer: Debian Electronics Team Changed-By: Andreas Bombe Closes: 1000923 Changes: ghdl (1.0.0+dfsg-6) unstable; urgency=medium . * Add llvm13.0.patch to allow building with LLVM 13.0 (Closes: #1000923) * Change versioning patch to the more general variant that was upstreamed * Refresh llvm11.1.0.patch * Add Forwarded tags to Debian patches Checksums-Sha1: 22bbf91cbabc60f60f533275fe72f4bef9129080 2546 ghdl_1.0.0+dfsg-6.dsc 1390964d0106156001a8598e3d52cc120b2fae75 21720 ghdl_1.0.0+dfsg-6.debian.tar.xz 167822396644206f5a5dd80d25f17115a94c6a41 9868 ghdl_1.0.0+dfsg-6_amd64.buildinfo Checksums-Sha256: 385bcaec4c4294f920f22aa42bdb53378e2c219ac060785428d12113a0d4e76e 2546 ghdl_1.0.0+dfsg-6.dsc b1bfff0f0514cbf4eca852748e248208d8db895935efe0a476797fb208de732d 21720 ghdl_1.0.0+dfsg-6.debian.tar.xz da48e499cab467fbdccf22c440eab567960e1bb3ad0a05e5f751492dbba069d6 9868 ghdl_1.0.0+dfsg-6_amd64.buildinfo Files: 4156a813a19b7d12144f45faf2bd10e6 2546 electronics optional ghdl_1.0.0+dfsg-6.dsc 2c678f36408df491c24822ebcb551244 21720 electronics optional ghdl_1.0.0+dfsg-6.debian.tar.xz 909e6f74fa6f1c2ca2366519b35b1b8e 9868 electronics optional ghdl_1.0.0+dfsg-6_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE/fJ3FAtt+ejNyKmCMWRwWx2jHUwFAmHClncACgkQMWRwWx2j HUyGQRAAyWubxutr3+NLNB2KcI41nxMxVr8F/72eciM4E068AOS1uuFsM902Iq7o +ec14DSzJKfu/nBbb335T6POplfkul9ovPaATC5H9pvbyFLFJeOcYn5Fsh4wnVy7 JiIyyArqcruChwQRl1KrCpXp+K2Nj0g9hHvRg/AAE1p+n4a+ow+wFeGh4SEoMK1Q sJlr9UlC4JOvls9PlPcSQDq+rdDHZY0RHqQhwsQoZ3tU48wyhu5C90X+Z8liEfHF mBvpSH9iPmBfvLoqH0qthFyHKqZpNGAqj4Qi6+Y3GR9/d36TOAtExbo0IWfK/rOe i7g3VdB2hmAlQ7t3T5IhJtDQN0i9eJsRBlbn+e6rCRR2/FeXD63ss/IIehbRsCaV 2ixifLfzx5X5dIickyLgr94d48Wz904tE258lMmyNG+ZGRoxUZCwFk3t3TMJv52N QljMXCmiQXgYfFJ20iklzPtFfQ6D+a2bR9xeLwLq3jF1xqLpJxvt4jf3i895mAax j7SxD8bK4oTUJe33ta+4VbuqmdzHPeGn2sxtiNS6m1NFtkv03g6C6C6Qlf2ftmX5 AM4DF2+QEjzeL3zqVAWhKaqeW2T626TJOm7u6WDT4EtSRduOdtTFR1yTHEVa8thI Ajyd00gNdy1WAMXGBRCk0LfO3er/HZVrr3EebAunR5tY1YpGSGA= =tCWa -END PGP SIGNATURE End Message ---
Bug#1002193: package-update-indicator: FTBFS: package-update-indicator.c:25:10: fatal error: gtk/gtk.h: No such file or directory
Howdy, Can you retry that build? I'm not getting any error during build, but recently there was a problem with one of the development headers this package depends on, it did not depend on all packages listed in the .pc file. Can you ensure you try with libayatana-appindicator3-dev 0.5.90-5? -4 was broken. Thanks, ~Unit 193 Unit193 @ Libera Unit193 @ OFTC
Bug#1002060: liblunar-date-doc: missing Breaks+Replaces: liblunar-date-dev (<< 3)
Hi Andreas, 在 2021/12/22 03:53, Andreas Beckmann 写道: Hi, another issue I noticed in liblunar-date-3.0-1: It is missing a corresponding Breaks to the existing Replaces. Without it the following sequence install liblunar-date-2.0-0 install liblunar-date-3.0-1 remove liblunar-date-3.0-1 will result in liblunar-date-2.0-0 having lost all its lunar-date.mo files, while dpkg considers it correctly installed. I used Replaces before, so dpkg considers liblunar-date-2.0-0 correctly installed after liblunar-date-3.0-1 removed. If liblunar-date-2.0-0 lost all its lunar-date.mo files, the liblunar-date-2.0-0 will become not completeness, so liblunar-date-2.0-0 and liblunar-date-3.0-1 should not to co-install in the same system. Add a corresponding Breaks to the existing Replaces is better. I would also recommend to use Breaks+Replaces: liblunar-date-2.0-0 (<< 3) in case lunar-date needs to be updated in stable at some point, because the (<= 2.4.0-8) will no longer be sufficient in this case. Andreas It's a very experienced recommend. Even that lunar-date in stable has seldom chance to update. Do it in salsa git. Thanks again! -- 肖盛文 xiao sheng wen Faris Xiao 微信(wechat)：atzlinux 《铜豌豆 Linux》https://www.atzlinux.com 基于 Debian 的 Linux 中文 桌面 操作系统 Debian QA page: https://qa.debian.org/developer.php?login=atzlinux%40sina.com GnuPG Public Key: 0x00186602339240CB OpenPGP_0x00186602339240CB.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature
Bug#1002253: Help with possibly broken ar archive
Andreas Tille writes: > I've never seen this before and I wonder whether this is something > I should be concerned about before uploading. Yes, it looks like the build system is set up to produce "thin" archives that can't stand on their own; please try patching the Makefile to drop the T flag from LINK.A (line 72). -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
Processed: tagging 1002281
Processing commands for cont...@bugs.debian.org: > tags 1002281 + confirmed Bug #1002281 [src:polymake] polymake: FTBFS: /<>/apps/polytope/rules/slack_ideal.rules:37: testcase 1 expected: regular return got: EXCEPTION: no more rules available to compute 'GENERATORS' Added tag(s) confirmed. > thanks Stopping processing here. Please contact me if you need assistance. -- 1002281: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002281 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1002243: marked as done (deepin-voice-recorder: FTBFS: Project ERROR: Unknown module(s) in QT: multimedia)
Your message dated Tue, 21 Dec 2021 20:17:42 -0500 with message-id <22d779fad8014a2a4d4c5a6f6486b43cadc140f0.ca...@debian.org> and subject line Re: [Pkg-deepin-devel] Bug#1002243: deepin-voice-recorder: FTBFS: Project ERROR: Unknown module(s) in QT: multimedia has caused the Debian Bug report #1002243, regarding deepin-voice-recorder: FTBFS: Project ERROR: Unknown module(s) in QT: multimedia 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.) -- 1002243: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002243 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: deepin-voice-recorder Version: 5.0.0-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211220 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_auto_configure -- DEFINES+="VERSION=5.0.0" > qmake -makefile "QMAKE_CFLAGS_RELEASE=-g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2" > "QMAKE_CFLAGS_DEBUG=-g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > -D_FORTIFY_SOURCE=2" "QMAKE_CXXFLAGS_RELEASE=-g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2" > "QMAKE_CXXFLAGS_DEBUG=-g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > -D_FORTIFY_SOURCE=2" "QMAKE_LFLAGS_RELEASE=-Wl,-z,relro -Wl,-z,now" > "QMAKE_LFLAGS_DEBUG=-Wl,-z,relro -Wl,-z,now" QMAKE_STRIP=: PREFIX=/usr > DEFINES\+=VERSION=5.0.0 > Info: creating stash file /<>/.qmake.stash > WARNING: Project ERROR: Unknown module(s) in QT: multimedia > Updating 'translations/deepin-voice-recorder_zh_CN.ts'... > Found 9 source text(s) (0 new and 9 already existing) > WARNING: Project ERROR: Unknown module(s) in QT: multimedia > Updating '/<>/translations/deepin-voice-recorder_zh_CN.qm'... > Generated 9 translation(s) (9 finished and 0 unfinished) > Project ERROR: Unknown module(s) in QT: multimedia > dh_auto_configure: error: qmake -makefile "QMAKE_CFLAGS_RELEASE=-g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2" > "QMAKE_CFLAGS_DEBUG=-g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > -D_FORTIFY_SOURCE=2" "QMAKE_CXXFLAGS_RELEASE=-g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2" > "QMAKE_CXXFLAGS_DEBUG=-g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > -D_FORTIFY_SOURCE=2" "QMAKE_LFLAGS_RELEASE=-Wl,-z,relro -Wl,-z,now" > "QMAKE_LFLAGS_DEBUG=-Wl,-z,relro -Wl,-z,now" QMAKE_STRIP=: PREFIX=/usr > DEFINES\+=VERSION=5.0.0 returned exit code 3 > make[1]: *** [debian/rules:27: override_dh_auto_configure] Error 25 The full build log is available from: http://qa-logs.debian.net/2021/12/20/deepin-voice-recorder_5.0.0-2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Version: 5.0.0-3 This bug is fixed in the latest upload (5.0.0-3) Thanks, Boyuan 在 2021-12-21星期二的 17:43 +0100，Lucas Nussbaum写道： > Source: deepin-voice-recorder > Version: 5.0.0-2 > Severity: serious > Justification: FTBFS > Tags: bookworm sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-20211220 ftbfs-bookworm > > Hi, > > During a rebuild of all packages in sid, your package failed to build > on amd64. > > > Relevant part (hopefully): > > make[1]: Entering directory '/<>' > > dh_auto_configure -- DEFINES+="VERSION=5.0.0" > > qmake -makefile "QMAKE_CFLAGS_RELEASE=-g -O2 -ffile-prefix- > > map=/<>=. -fstack-protector-strong -Wformat -Werror=format- > > security -Wdate-time -D_FORTIFY_SOURCE=2" "QMAKE_CFLAGS_DEBUG=-g -O2 - > > ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat - > > Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2" > >
Bug#1000680: python3-aiohttp: fails to import, "TypeError: function() argument 'code' must be code, not str"
Hi, 在 2021-11-28星期日的 20:51 +0100，Piotr Ożarowski写道： > [Boyuan Yang, 2021-11-28] > > Thanks for the info and sorry for the breakage; obviously I should have > > uploaded it into Experimental first. I am looking into fixing the issue > > (ideally through upgrade of all related packages) but this may take some > > time. > > If you already have a solution, it would be even better. > > I already fixed it by upgrading aiohttp. It needs 2 NEW packages that I > packaged and uploaded, one of them is already accepted, second it > waiting for review. Unfortunately I uploaded my previous build (tagged > 1~exp1 in the git repo, but uploaded -1 so version in unstable needs > aiosignal ASAP - I asked one of the ftp-masters if it's possible to > check it sooner and hopefully unstable will be fixed soon) All related packages (finally!) migrated to Testing; now we can consider this bug to be fully solved. Cheers, Boyuan signature.asc Description: This is a digitally signed message part
Bug#1002186: rumur: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j4 check ARGS\+=--verbose ARGS\+=-j4 returned exit code 2
Thanks for reporting! It looks like there are now libc calls to `newfstatat` which is not in Rumur’s sandbox’s list of safe allowed syscalls. I’ll fix this upstream and then package a new release for Debian.
Bug#997381: python-pgpy: FTBFS: AttributeError: 'Sphinx' object has no attribute 'add_stylesheet'
Hello,
On Sat 23 Oct 2021 at 09:50PM +02, Lucas Nussbaum wrote:
>> make[2]: Entering directory '/<>/docs'
>> sphinx-build -b html -d build/doctrees source build/html
>> Running Sphinx v4.2.0
>>
>> Exception occurred:
>> File "/<>/docs/source/_ext/progress.py", line 147, in setup
>> app.add_stylesheet('progress.css')
>> AttributeError: 'Sphinx' object has no attribute 'add_stylesheet'
>> The full traceback has been saved in /tmp/sphinx-err-olciwe_g.log, if you
>> want to report the issue to the developers.
>> Please also report this if it was a user error, so that a better error
>> message can be provided next time.
>> A bug report can be filed in the tracker at
>> . Thanks!
>> make[2]: *** [Makefile:53: html] Error 2
>
>
> The full build log is available from:
> http://qa-logs.debian.net/2021/10/23/python-pgpy_0.5.3-3_unstable.log
I've looked at upstream's docs and add_stylesheet has simply been
renamed to add_css_file, so the fix for this bug is simple.
I haven't done an NMU because the test suite is failing for other
reasons.
--
Sean Whitton
signature.asc
Description: PGP signature
Processed: block 997609 with 1000435
Processing commands for cont...@bugs.debian.org:
> block 997609 with 1000435
Bug #997609 {Done: Stefano Rivera } [src:deap] deap:
FTBFS: error in deap setup command: use_2to3 is invalid.
997609 was not blocked by any bugs.
997609 was not blocking any bugs.
Added blocking bug(s) of 997609: 1000435
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
997609: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997609
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: closing 1002135, closing 1002152, closing 1002162, closing 1002195
Processing commands for cont...@bugs.debian.org: > # all fixed in spdlog > close 1002135 Bug #1002135 [src:hinge] hinge: FTBFS: libfmt-dev : Breaks: libspdlog-dev (< 1:1.9.2+ds-0.1) but 1:1.8.5+ds-3 is to be installed Marked Bug as done > close 1002152 Bug #1002152 [src:rapmap] rapmap: FTBFS: libfmt-dev : Breaks: libspdlog-dev (< 1:1.9.2+ds-0.1) but 1:1.8.5+ds-3 is to be installed Marked Bug as done > close 1002162 Bug #1002162 [src:waybar] waybar: FTBFS: libfmt-dev : Breaks: libspdlog-dev (< 1:1.9.2+ds-0.1) but 1:1.8.5+ds-3 is to be installed Marked Bug as done > close 1002195 Bug #1002195 [src:cherrytree] cherrytree: FTBFS: libfmt-dev : Breaks: libspdlog-dev (< 1:1.9.2+ds-0.1) but 1:1.8.5+ds-3 is to be installed Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1002135: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002135 1002152: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002152 1002162: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002162 1002195: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002195 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1002135: closing 1002135, closing 1002152, closing 1002162, closing 1002195
# all fixed in spdlog close 1002135 close 1002152 close 1002162 close 1002195 thanks
Processed: tagging 1002290
Processing commands for cont...@bugs.debian.org: > tags 1002290 - moreinfo Bug #1002290 [dh-python] dh_python3 needing contextvars -- not a problem with my package, then? Bug #1002182 [dh-python] qutebrowser: FTBFS: AttributeError: 'NoneType' object has no attribute 'split' Removed tag(s) moreinfo. Removed tag(s) moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 1002182: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002182 1002290: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002290 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1002182: qutebrowser: FTBFS: AttributeError: 'NoneType' object has no attribute 'split'
Processing control commands: > reassign -1 dh-python Bug #1002182 [src:qutebrowser] qutebrowser: FTBFS: AttributeError: 'NoneType' object has no attribute 'split' Bug reassigned from package 'src:qutebrowser' to 'dh-python'. No longer marked as found in versions qutebrowser/2.4.0-1. Ignoring request to alter fixed versions of bug #1002182 to the same values previously set > forcemerge 1002290 -1 Bug #1002290 [dh-python] dh_python3 needing contextvars -- not a problem with my package, then? Bug #1002182 [dh-python] qutebrowser: FTBFS: AttributeError: 'NoneType' object has no attribute 'split' Severity set to 'grave' from 'serious' Marked as found in versions dh-python/5.20211217. Bug #1002290 [dh-python] dh_python3 needing contextvars -- not a problem with my package, then? Added tag(s) sid, confirmed, bookworm, ftbfs, and moreinfo. Merged 1002182 1002290 > found -1 5.20211213 Bug #1002182 [dh-python] qutebrowser: FTBFS: AttributeError: 'NoneType' object has no attribute 'split' Bug #1002290 [dh-python] dh_python3 needing contextvars -- not a problem with my package, then? Marked as found in versions dh-python/5.20211213. Marked as found in versions dh-python/5.20211213. > found -1 5.20211217 Bug #1002182 [dh-python] qutebrowser: FTBFS: AttributeError: 'NoneType' object has no attribute 'split' Bug #1002290 [dh-python] dh_python3 needing contextvars -- not a problem with my package, then? Ignoring request to alter found versions of bug #1002182 to the same values previously set Ignoring request to alter found versions of bug #1002290 to the same values previously set > affects -1 + qutebrowser python-anyio Bug #1002182 [dh-python] qutebrowser: FTBFS: AttributeError: 'NoneType' object has no attribute 'split' Bug #1002290 [dh-python] dh_python3 needing contextvars -- not a problem with my package, then? Added indication that 1002182 affects qutebrowser and python-anyio Added indication that 1002290 affects qutebrowser and python-anyio -- 1002182: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002182 1002290: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002290 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1002182: qutebrowser: FTBFS: AttributeError: 'NoneType' object has no attribute 'split'
Control: reassign -1 dh-python
Control: forcemerge 1002290 -1
Control: found -1 5.20211213
Control: found -1 5.20211217
Control: affects -1 + qutebrowser python-anyio
Hi Florian,
thanks for your analysis of what I found out about the recent
dh-python changes!
I tried to extract the IMHO relevant parts for the dh-python
developers from the mails in this bug report so far:
Lucas Nussbaum wrote:
> I: dh_python3 fs:511: removing qutebrowser-2.4.0-py3.9.egg-info
> (qutebrowser-2.4.0.egg-info is already available)
> I: dh_python3 pydist:313: Cannot find package that provides dataclasses.
> Please add package that provides it to Build-Depends or add "dataclasses
> python3-dataclasses" line to debian/py3dist-overrides or add proper
> dependency to Depends by hand and ignore this info.
> Traceback (most recent call last):
> File "/usr/bin/dh_python3", line 280, in
> main()
> File "/usr/bin/dh_python3", line 201, in main
> dependencies.parse(stats, options)
> File "/usr/share/dh-python/dhpython/depends.py", line 242, in parse
> deps = parse_pydep(self.impl, fn, bdep=self.bdep, **section_options)
> File "/usr/share/dh-python/dhpython/pydist.py", line 522, in parse_pydep
> for part in dependency.split(','))
> AttributeError: 'NoneType' object has no attribute 'split'
> make: *** [debian/rules:6: binary] Error 1
Florian Bruhin wrote:
> That seems like a false-positive: The dataclasses backport is only
> required for Python 3.6, but Debian sets "Depends: python3 (>= 3.7)"
> already.
[…]
> That smells like a bug in dh-python.
I wrote:
> I tried downgrading dh-python until it no more FTBFS. It doesn't FTBFS
> with dh-python 5.2024 and the first version it FTBFS is 5.20211213.
[…]
> Full [changelog] entry […] at
> https://packages.qa.debian.org/d/dh-python/news/20211214T010008Z.html
>
> Florian: Any idea which of these might have broken this?
Florian Bruhin wrote:
> It's "Add support for environment markers.". Environment markers are
> basically conditional dependencies, e.g. for a given Python version or
> OS only.
>
> The crash happens here:
> https://salsa.debian.org/python-team/tools/dh-python/-/blob/5.20211217/dhpython/pydist.py#L522
> because "dependency" is None.
>
> That's coming from here:
> https://salsa.debian.org/python-team/tools/dh-python/-/blob/5.20211217/dhpython/pydist.py#L516
> i.e. is the return value of "guess_deps".
>
> Looking at that, we spot our error message about dataclasses:
> https://salsa.debian.org/python-team/tools/dh-python/-/blob/5.20211217/dhpython/pydist.py#L313-317
>
> ...but also a strange commented out "return pname" which has been around
> for 7 years:
> https://salsa.debian.org/python-team/tools/dh-python/-/commit/de7db9bd0021cee65e477f11cd69cfd93350bd2e
>
> Due to the commented out return, the function ends and implicitly
> returns None.
>
> The code which crashes due to that None value is very recent:
> https://salsa.debian.org/python-team/tools/dh-python/-/commit/832f01c9c7da22a1d00887d8ce0e6be9893bdf3e
>
> So I suppose it would be good if someone could forward this do
> dh-python, I use the Debian bugtracker too seldom to know what the best
> way to do this would be (but if preferable, I can open a new bug).
Done herewith: Reassigned the bug to dh-python and marked it as found
in the according versions. See the first few lines of this mail.
> > And is the suggestion to add "dataclasses python3-dataclasses" line to
> > debian/py3dist-overrides something we should simply do or is this an
> > issue which we should make the dh-python maintainers aware of? I must
> > admit, I still don't understand what this is dh-python argues about.
> > Maybe someone has some more Python insight for a non-pythonista?
>
> Perhaps both. So what dh-python seems to be doing here is to look at
> the dependencies declared in a "requirements.txt" (a somewhat common
> way to specify dependencies for Python projects) and check whether the
> Debian packaging mirrors those requirements as well. Here is the line in
> question:
>
> https://github.com/qutebrowser/qutebrowser/blob/v2.4.0/requirements.txt#L5
>
> So this declares that qutebrowser needs the "dataclasses" backport for
> Python versions older than 3.7 (it still supports Python 3.6, though
> that will change as soon as 3.0.0 is finished:
> https://github.com/qutebrowser/qutebrowser/issues/6905).
>
> However, the Debian package for qutebrowser declares
> "Depends: python3 (>= 3.7)", so that dependency actually is irrelevant
> for Debian.
>
> Should dh-python handle that case? Well, maybe, but it sure shouldn't
> crash.
I hope this is enough context for the dh-python developers to
understand what's the issue.
Actually I just found out that someone else reported this against
dh-python already later today, see https://bugs.debian.org/1002290 —
trying to merge the bug reports.
Regards, Axel
--
,''`. | Axel Beckert , https://people.debian.org/~abe/
: :' : | Debian Developer,
Bug#1002161: marked as done (python-fsquota: FTBFS: src/FsQuota.c:16:10: fatal error: Python.h: No such file or directory)
Your message dated Tue, 21 Dec 2021 21:19:39 +
with message-id
and subject line Bug#1002161: fixed in python-fsquota 0.1.0+dfsg1-3
has caused the Debian Bug report #1002161,
regarding python-fsquota: FTBFS: src/FsQuota.c:16:10: fatal error: Python.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.)
--
1002161: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002161
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-fsquota
Version: 0.1.0+dfsg1-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211220 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> x86_64-linux-gnu-gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g
> -fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat
> -Werror=format-security -g -fwrapv -O2 -g -O2
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -I.
> -I/usr/include/tirpc -I/usr/include/python3.10 -c src/FsQuota.c -o
> build/temp.linux-x86_64-3.10/src/FsQuota.o
> src/FsQuota.c:16:10: fatal error: Python.h: No such file or directory
>16 | #include "Python.h"
> | ^~
> compilation terminated.
> error: command '/usr/bin/x86_64-linux-gnu-gcc' failed with exit code 1
> E: pybuild pybuild:355: build: plugin distutils failed with: exit code=1:
> /usr/bin/python3.10 setup.py build
> I: pybuild base:237: /usr/bin/python3 setup.py build
> Using hints/linux.h for myconfig.h
> Configured to use tirpc library instead of rpcsvc
> running build
> running build_ext
> building 'FsQuota' extension
> creating build/temp.linux-x86_64-3.9
> creating build/temp.linux-x86_64-3.9/src
> x86_64-linux-gnu-gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g
> -fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat
> -Werror=format-security -g -fwrapv -O2 -g -O2
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -I.
> -I/usr/include/tirpc -I/usr/include/python3.9 -c src/FsQuota.c -o
> build/temp.linux-x86_64-3.9/src/FsQuota.o
> x86_64-linux-gnu-gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g
> -fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat
> -Werror=format-security -g -fwrapv -O2 -g -O2
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -I.
> -I/usr/include/tirpc -I/usr/include/python3.9 -c src/linuxapi.c -o
> build/temp.linux-x86_64-3.9/src/linuxapi.o
> x86_64-linux-gnu-gcc -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions -g
> -fwrapv -O2 -Wl,-z,relro -Wl,-z,now -g -O2
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2
> build/temp.linux-x86_64-3.9/src/FsQuota.o
> build/temp.linux-x86_64-3.9/src/linuxapi.o -ltirpc -o
> /<>/.pybuild/cpython3_3.9_fsquota/build/FsQuota.cpython-39-x86_64-linux-gnu.so
> dh_auto_build: error: pybuild --build -i python{version} -p "3.10 3.9"
> returned exit code 13
> make: *** [debian/rules:9: binary] Error 25
The full build log is available from:
http://qa-logs.debian.net/2021/12/20/python-fsquota_0.1.0+dfsg1-2_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: python-fsquota
Source-Version: 0.1.0+dfsg1-3
Done: Philipp Huebner
We believe that the bug you reported is fixed in the latest version of
python-fsquota, 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 1002...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Philipp Huebner (supplier of updated python-fsquota
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it
Bug#1002204: marked as done (navit: FTBFS: speech_speech_dispatcher.c:41:5: error: format not a string literal and no format arguments [-Werror=format-security])
Your message dated Tue, 21 Dec 2021 21:05:18 + with message-id and subject line Bug#1002204: fixed in navit 0.5.6+dfsg.1-1 has caused the Debian Bug report #1002204, regarding navit: FTBFS: speech_speech_dispatcher.c:41:5: error: format not a string literal and no format arguments [-Werror=format-security] to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1002204: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002204 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: navit Version: 0.5.5+dfsg.1-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211220 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > cd /<>/obj-x86_64-linux-gnu/navit/map/garmin && /usr/bin/gcc > -DBIN_DIR=\"bin\" -DIMAGE_DIR=\"share/navit/icons\" -DLIB_DIR=\"lib/navit\" > -DLOCALE_DIR=\"share/locale\" -DMAN_DIR=\"share/man/man1\" > -DSHARE_DIR=\"share/navit\" -DTEXTURE_DIR=\"share/navit/textures\" > -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include > -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include > -I/usr/include/freetype2 -I/usr/include/atk-1.0 -I/usr/include/gdk-pixbuf-2.0 > -I/usr/include/cairo -I/usr/include/harfbuzz -I/usr/include/pango-1.0 > -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/SDL > -I/<>/obj-x86_64-linux-gnu -I/<> > -I/<>/navit -I/<>/obj-x86_64-linux-gnu/navit > -I/<>/navit/support -I/<>/navit/font/freetype > -I/<>/navit/graphics/gtk_drawing_area > -I/<>/navit/gui/gtk -I/<>/navit/vehicle/gpsd > -I/<>/navit/binding/dbus -I/<>/navit/speech/dbus > -I/<>/navit/speech/cmdline > -I/<>/navit/vehicle/gpsd_dbus > -I/<>/navit/speech/speech_dispatcher > -I/<>/navit/map/garmin -I/<>/navit/graphics/null > -I/<>/navit/osd/core -I/<>/navit/vehicle/demo > -I/<>/navit/vehicle/file -I/<>/navit/vehicle/null > -I/<>/navit/gui/internal -I/<>/navit/map/binfile > -I/<>/navit/map/filter -I/<>/navit/map/mg > -I/<>/navit/map/shapefile -I/<>/navit/map/textfile > -I/<>/navit/map/csv -I/<>/navit/traffic/dummy > -I/<>/navit/traffic/null -I/<>/navit/fib-1.1 > -I/<>/obj-x86_64-linux-gnu/navit/map/garmin -isystem > /usr/include/gtk-2.0 -g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > -D_FORTIFY_SOURCE=2 "-DNDEBUG" -Wall -Wno-unused-parameter > -Wno-sign-compare -Wno-missing-field-initializers -Wundef -Wcast-align > -Wpointer-arith -Wextra -Wdate-time -Wmissing-prototypes > -Wstrict-prototypes -Wformat-security -Werror=format-security > -fstack-protector-strong -D_FORTIFY_SOURCE=2 -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -DNDEBUG -fPIC -MD > -MT navit/map/garmin/CMakeFiles/gentypes.dir/gentypes.c.o -MF > CMakeFiles/gentypes.dir/gentypes.c.o.d -o > CMakeFiles/gentypes.dir/gentypes.c.o -c > /<>/navit/map/garmin/gentypes.c > In file included from > /<>/navit/speech/speech_dispatcher/speech_speech_dispatcher.c:32: > /<>/navit/speech.h:36:48: warning: ‘enum attr_type’ declared > inside parameter list will not be visible outside of this definition or > declaration >36 | int speech_get_attr(struct speech *this_, enum attr_type type, struct > attr *attr, struct attr_iter *iter); > |^ > /<>/navit/speech/speech_dispatcher/speech_speech_dispatcher.c: > In function ‘speechd_say’: > /<>/navit/speech/speech_dispatcher/speech_speech_dispatcher.c:41:5: > error: format not a string literal and no format arguments > [-Werror=format-security] >41 | err = spd_sayf(this->conn, SPD_MESSAGE, text); > | ^~~ > cc1: some warnings being treated as errors > make[3]: *** > [navit/speech/speech_dispatcher/CMakeFiles/speech_speech_dispatcher.dir/build.make:79: > > navit/speech/speech_dispatcher/CMakeFiles/speech_speech_dispatcher.dir/speech_speech_dispatcher.c.o] > Error 1 The full build log is available from: http://qa-logs.debian.net/2021/12/20/navit_0.5.5+dfsg.1-2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify
Processed: Re. Bug#1002073: src:tryton-modules-country: Tests fail with new iso-codes
Processing commands for cont...@bugs.debian.org: > forwarded 1002073 https://bugs.tryton.org/issue11078 Bug #1002073 [src:tryton-modules-country] src:tryton-modules-country: Tests fail with new iso-codes Set Bug forwarded-to-address to 'https://bugs.tryton.org/issue11078'. > End of message, stopping processing here. Please contact me if you need assistance. -- 1002073: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002073 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: notfound 998565 in 20.7.3+ds1-1
Processing commands for cont...@bugs.debian.org:
> notfound 998565 20.7.3+ds1-1
Bug #998565 {Done: Stuart Prescott } [src:pycountry]
pycountry: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p 3.9
returned exit code 13
No longer marked as found in versions pycountry/20.7.3+ds1-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
998565: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998565
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1002101: marked as done (gjs: FTBFS with Meson 0.60.2: ../meson.build:578:0: ERROR: "install_dir" must be specified when installing a target)
Your message dated Tue, 21 Dec 2021 20:48:43 +
with message-id
and subject line Bug#1002101: fixed in gjs 1.70.0-4
has caused the Debian Bug report #1002101,
regarding gjs: FTBFS with Meson 0.60.2: ../meson.build:578:0: ERROR:
"install_dir" must be specified when installing a target
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.)
--
1002101: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002101
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gjs
Version: 1.70.0-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211220 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> cc: error: unrecognized command-line option '-Wtypedef-redefinition'
>
> Compiler for C supports arguments -Wno-typedef-redefinition: NO
> Running compile:
> Working directory:
> /<>/obj-x86_64-linux-gnu/meson-private/tmpkhsrc8h6
> Command line: c++
> /<>/obj-x86_64-linux-gnu/meson-private/tmpkhsrc8h6/testfile.cpp
> -o /<>/obj-x86_64-linux-gnu/meson-private/tmpkhsrc8h6/output.exe
> -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2
> -D_FILE_OFFSET_BITS=64 -O0 -fpermissive -Wl,--fatal-warnings
> -Bsymbolic-functions -Wl,-z,relro -Wl,-z,now -Wl,-z,defs
>
> Code:
> int main(void) { return 0; }
>
> Compiler stdout:
>
> Compiler stderr:
>
> Compiler for C++ supports link arguments -Bsymbolic-functions: YES
> Running compile:
> Working directory:
> /<>/obj-x86_64-linux-gnu/meson-private/tmprrpmbkqe
> Command line: cc
> /<>/obj-x86_64-linux-gnu/meson-private/tmprrpmbkqe/testfile.c -o
> /<>/obj-x86_64-linux-gnu/meson-private/tmprrpmbkqe/output.obj -c
> -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2
> -D_FILE_OFFSET_BITS=64 -O0 -fno-semantic-interposition
>
> Code:
> extern int i;
> int i;
>
> Compiler stdout:
>
> Compiler stderr:
>
> Compiler for C supports arguments -fno-semantic-interposition: YES
> Running compile:
> Working directory:
> /<>/obj-x86_64-linux-gnu/meson-private/tmp5d7oj47g
> Command line: c++
> /<>/obj-x86_64-linux-gnu/meson-private/tmp5d7oj47g/testfile.cpp
> -o /<>/obj-x86_64-linux-gnu/meson-private/tmp5d7oj47g/output.obj
> -c -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong
> -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2
> -D_FILE_OFFSET_BITS=64 -O0 -fpermissive -fno-semantic-interposition
>
> Code:
> extern int i;
> int i;
>
> Compiler stdout:
>
> Compiler stderr:
>
> Compiler for C++ supports arguments -fno-semantic-interposition: YES
> Pkg-config binary for MachineChoice.HOST is not cached.
> Pkg-config binary missing from cross or native file, or env var undefined.
> Trying a default Pkg-config fallback at pkg-config
> Found pkg-config: /usr/bin/pkg-config (0.29.2)
> Determining dependency 'glib-2.0' with pkg-config executable
> '/usr/bin/pkg-config'
> env[PKG_CONFIG_PATH]:
> Called `/usr/bin/pkg-config --modversion glib-2.0` -> 0
> 2.70.2
> env[PKG_CONFIG_PATH]:
> Called `/usr/bin/pkg-config --cflags glib-2.0` -> 0
> -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include
> env[PKG_CONFIG_ALLOW_SYSTEM_LIBS]: 1
> env[PKG_CONFIG_PATH]:
> Called `/usr/bin/pkg-config --libs glib-2.0` -> 0
> -L/usr/lib/x86_64-linux-gnu -lglib-2.0
> env[PKG_CONFIG_PATH]:
> Called `/usr/bin/pkg-config --libs glib-2.0` -> 0
> -lglib-2.0
> Running compile:
> Working directory:
> /<>/obj-x86_64-linux-gnu/meson-private/tmpzrej3i91
> Command line: c++
> /<>/obj-x86_64-linux-gnu/meson-private/tmpzrej3i91/testfile.cpp
> -o /<>/obj-x86_64-linux-gnu/meson-private/tmpzrej3i91/output.exe
> -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2
> -D_FILE_OFFSET_BITS=64 -O0 -fpermissive -Wl,-z,relro -Wl,-z,now -Wl,-z,defs
>
> Code:
> #include
>
> int main(void) {
> printf("%ld\n", (long)(sizeof(void *)));
> return 0;
> }
> Compiler stdout:
>
> Compiler stderr:
>
> Program stdout:
>
> 8
>
> Program stderr:
>
>
> Running compile:
> Working directory:
> /<>/obj-x86_64-linux-gnu/meson-private/tmppqc33sdx
> Command line: c++
> /<>/obj-x86_64-linux-gnu/meson-private/tmppqc33sdx/testfile.cpp
> -o /<>/obj-x86_64-linux-gnu/meson-private/tmppqc33sdx/output.obj
> -c -g -O2 -ffile-prefix-map=/<>=.
Processed: Help with possibly broken ar archive (Was: Bug#1002253: libatomic-queue: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below)
Processing control commands: > tags -1 pending Bug #1002253 [src:libatomic-queue] libatomic-queue: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below Added tag(s) pending. -- 1002253: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002253 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1002253: Help with possibly broken ar archive (Was: Bug#1002253: libatomic-queue: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below)
Control: tags -1 pending Am Tue, Dec 21, 2021 at 05:33:32PM +0100 schrieb Lucas Nussbaum: > Source: libatomic-queue > Version: 0.0+git20201108.d9d66b6-4 > Severity: serious > Justification: FTBFS This is solved in Git. However, when I try to build the status in Git I get: E: libatomic-queue-dev: unpack-message-for-deb-data ar failed for usr/lib/x86_64-linux-gnu/libatomic_queue.a N: N: Unpacking the contents of the data.tar.gz member of this installable package produced the listed error. N: N: It probably means something is broken or the package was somehow constructed in a strange way. N: N: Visibility: error N: Show-Always: no N: Check: lintian N: and in fact when I install the packages I get: $ ar t /usr/lib/x86_64-linux-gnu/libatomic_queue.a ar: /usr/lib/x86_64-linux-gnu/libatomic_queue.a: malformed archive I've never seen this before and I wonder whether this is something I should be concerned about before uploading. Kind regards Andreas. -- http://fam-tille.de
Bug#965887: Update debhelper compatibility and build rules
Hi Jorge, Niels, all, I prepare patch for Debian packaging files that increases debhelper compatibility and makes clean of build rules. This should completely address this bug. See attachment. Cheers -- Slávek diff -ruN a/debian/changelog b/debian/changelog --- a/debian/changelog 2021-12-21 18:51:32.0 + +++ b/debian/changelog 2021-12-21 18:41:33.935270305 + @@ -1,3 +1,15 @@ +xcalib (0.8.dfsg1-2.2) unstable; urgency=medium + + * Non-maintainer upload. + * debian/control: ++ Update to debhelper 13 compatibility. ++ Bump standards version to 4.6.0. + * debian/rules: Clean the rules - use of debhelper overrides. + * debian/source/format: Declare format 3.0 (quilt). + * debian/copyright: Clarify link to GPL-2. + + -- Slávek Banko Tue, 21 Dec 2021 19:38:58 +0100 + xcalib (0.8.dfsg1-2.1) unstable; urgency=medium * Non-maintainer upload. diff -ruN a/debian/compat b/debian/compat --- a/debian/compat 2021-12-21 18:51:32.0 + +++ b/debian/compat 1970-01-01 00:00:00.0 + @@ -1 +0,0 @@ -5 diff -ruN a/debian/control b/debian/control --- a/debian/control 2021-12-21 18:51:32.0 + +++ b/debian/control 2021-12-21 16:07:56.295333939 + @@ -2,8 +2,8 @@ Section: x11 Priority: optional Maintainer: Jorge Salamero Sanz -Build-Depends: debhelper (>= 5), libxxf86vm-dev, libxext-dev -Standards-Version: 3.8.0 +Build-Depends: debhelper-compat (= 13), libxxf86vm-dev, libxext-dev +Standards-Version: 4.6.0 Homepage: http://xcalib.sourceforge.net/ Package: xcalib diff -ruN a/debian/copyright b/debian/copyright --- a/debian/copyright 2021-12-21 18:51:32.0 + +++ b/debian/copyright 2021-12-21 16:49:13.705050593 + @@ -41,4 +41,4 @@ can be found in the file `/usr/share/common-licenses/GPL-2'. The Debian packaging is (C) 2007, Jorge Salamero Sanz -and is licensed under the GPL, see `/usr/share/common-licenses/GPL'. +and is licensed under the GPL, see `/usr/share/common-licenses/GPL-2'. diff -ruN a/debian/rules b/debian/rules --- a/debian/rules 2021-12-21 18:51:32.0 + +++ b/debian/rules 2021-12-21 16:03:47.383133986 + @@ -1,66 +1,15 @@ #!/usr/bin/make -f -# Uncomment this to turn on verbose mode. -#export DH_VERBOSE=1 - -DPKG_EXPORT_BUILDFLAGS = 1 -include /usr/share/dpkg/default.mk -include /usr/share/dpkg/buildtools.mk - XCALIB_VERSION = 0.8 +%: + dh $@ -configure: configure-stamp - -configure-stamp: - dh_testdir - - touch $@ - -build: build-stamp - -build-stamp: configure-stamp +override_dh_auto_build: dh_testdir - $(CC) $(CFLAGS) -c xcalib.c -DXCALIB_VERSION=\"$(XCALIB_VERSION)\" $(CC) $(CFLAGS) -o xcalib xcalib.o -lm -lX11 -lXxf86vm -lXext - - touch $@ -clean: +override_dh_auto_install: dh_testdir - dh_testroot - rm -f build-stamp configure-stamp - - rm -f xcalib.o xcalib - - dh_clean - -install: build - dh_testdir - dh_testroot - dh_clean -k - dh_installdirs - - install -o 0 -g 0 -m 0755 xcalib $(CURDIR)/debian/xcalib/usr/bin/xcalib - -binary-indep: - -binary-arch: build install - dh_testdir - dh_testroot - dh_installdocs - dh_installchangelogs - dh_installman - dh_link - dh_strip - dh_compress - dh_fixperms - dh_installdeb - dh_shlibdeps - dh_gencontrol - dh_md5sums - dh_builddeb - -binary: binary-indep binary-arch -.PHONY: build clean binary-indep binary-arch binary install + install -o 0 -g 0 -m 0755 xcalib debian/xcalib/usr/bin/xcalib diff -ruN a/debian/source/format b/debian/source/format --- a/debian/source/format 1970-01-01 00:00:00.0 + +++ b/debian/source/format 2016-01-16 15:13:56.0 + @@ -0,0 +1 @@ +3.0 (quilt) signature.asc Description: This is a digitally signed message part.
Processed: Add tag "patch"
Processing commands for cont...@bugs.debian.org: > tag 965887 + patch Bug #965887 [src:xcalib] xcalib: Removal of obsolete debhelper compat 5 and 6 in bookworm Added tag(s) patch. > End of message, stopping processing here. Please contact me if you need assistance. -- 965887: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965887 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1002164: marked as done (rust-alacritty-terminal: FTBFS: build-dependency not installable: librust-signal-hook-registry-1.2+default-dev)
Your message dated Tue, 21 Dec 2021 20:27:51 + with message-id <6dde2ef1-9d7e-81ac-601b-663fabbc2...@p10link.net> and subject line Re: Bug#1002164: rust-alacritty-terminal: FTBFS: build-dependency not installable: librust-signal-hook-registry-1.2+default-dev has caused the Debian Bug report #1002164, regarding rust-alacritty-terminal: FTBFS: build-dependency not installable: librust-signal-hook-registry-1.2+default-dev to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1002164: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002164 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: rust-alacritty-terminal Version: 0.15.0-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211220 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: debhelper (>= 12), dh-cargo (>= 25), cargo, rustc, > libstd-rust-dev, librust-alacritty-config-derive-0.1+default-dev, > librust-base64-0.13+default-dev, librust-bitflags-1+default-dev, > librust-dirs-3+default-dev (>= 3.0.1-~~), librust-libc-0.2+default-dev, > librust-log-0.4+default-dev, librust-mio-0.6+default-dev, > librust-mio-extras-2+default-dev, librust-nix-0.23+default-dev, > librust-parking-lot-0.10+default-dev, librust-regex-automata-0.1+default-dev > (>= 0.1.8-~~), librust-serde-1+default-dev, librust-serde-1+derive-dev, > librust-serde-yaml-0.8+default-dev, librust-signal-hook-0.1+default-dev, > librust-signal-hook-0.1+mio-support-dev, > librust-unicode-width-0.1+default-dev, librust-vte-0.10-dev, build-essential, > fakeroot > Filtered Build-Depends: debhelper (>= 12), dh-cargo (>= 25), cargo, rustc, > libstd-rust-dev, librust-alacritty-config-derive-0.1+default-dev, > librust-base64-0.13+default-dev, librust-bitflags-1+default-dev, > librust-dirs-3+default-dev (>= 3.0.1-~~), librust-libc-0.2+default-dev, > librust-log-0.4+default-dev, librust-mio-0.6+default-dev, > librust-mio-extras-2+default-dev, librust-nix-0.23+default-dev, > librust-parking-lot-0.10+default-dev, librust-regex-automata-0.1+default-dev > (>= 0.1.8-~~), librust-serde-1+default-dev, librust-serde-1+derive-dev, > librust-serde-yaml-0.8+default-dev, librust-signal-hook-0.1+default-dev, > librust-signal-hook-0.1+mio-support-dev, > librust-unicode-width-0.1+default-dev, librust-vte-0.10-dev, build-essential, > fakeroot > dpkg-deb: building package 'sbuild-build-depends-main-dummy' in > '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'. > Ign:1 copy:/<>/apt_archive ./ InRelease > Get:2 copy:/<>/apt_archive ./ Release [963 B] > Ign:3 copy:/<>/apt_archive ./ Release.gpg > Get:4 copy:/<>/apt_archive ./ Sources [594 B] > Get:5 copy:/<>/apt_archive ./ Packages [664 B] > Fetched 2221 B in 0s (0 B/s) > Reading package lists... > Reading package lists... > > Install main build dependencies (apt-based resolver) > > > Installing build dependencies > Reading package lists... > Building dependency tree... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > librust-signal-hook-dev : Depends: > librust-signal-hook-registry-1.2+default-dev but it is not installable > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://qa-logs.debian.net/2021/12/20/rust-alacritty-terminal_0.15.0-2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- This
Bug#1002149: marked as done (rust-signal-hook: FTBFS: build-dependency not installable: librust-signal-hook-registry-1.2+default-dev)
Your message dated Tue, 21 Dec 2021 20:25:03 + with message-id and subject line Bug#1002149: fixed in rust-signal-hook 0.1.13-3 has caused the Debian Bug report #1002149, regarding rust-signal-hook: FTBFS: build-dependency not installable: librust-signal-hook-registry-1.2+default-dev to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1002149: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002149 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: rust-signal-hook Version: 0.1.13-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211220 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: debhelper (>= 12), dh-cargo (>= 25), cargo, rustc, > libstd-rust-dev, librust-libc-0.2+default-dev, > librust-signal-hook-registry-1.2+default-dev, build-essential, fakeroot > Filtered Build-Depends: debhelper (>= 12), dh-cargo (>= 25), cargo, rustc, > libstd-rust-dev, librust-libc-0.2+default-dev, > librust-signal-hook-registry-1.2+default-dev, build-essential, fakeroot > dpkg-deb: building package 'sbuild-build-depends-main-dummy' in > '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'. > Ign:1 copy:/<>/apt_archive ./ InRelease > Get:2 copy:/<>/apt_archive ./ Release [957 B] > Ign:3 copy:/<>/apt_archive ./ Release.gpg > Get:4 copy:/<>/apt_archive ./ Sources [436 B] > Get:5 copy:/<>/apt_archive ./ Packages [511 B] > Fetched 1904 B in 0s (0 B/s) > Reading package lists... > Reading package lists... > > Install main build dependencies (apt-based resolver) > > > Installing build dependencies > Reading package lists... > Building dependency tree... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > sbuild-build-depends-main-dummy : Depends: > librust-signal-hook-registry-1.2+default-dev but it is not installable > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://qa-logs.debian.net/2021/12/20/rust-signal-hook_0.1.13-2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: rust-signal-hook Source-Version: 0.1.13-3 Done: Peter Michael Green We believe that the bug you reported is fixed in the latest version of rust-signal-hook, 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 1002...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Peter Michael Green (supplier of updated rust-signal-hook package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 21 Dec 2021 19:58:06 + Source: rust-signal-hook Architecture: source Version: 0.1.13-3 Distribution: unstable Urgency: medium Maintainer: Debian Rust Maintainers Changed-By: Peter Michael Green Closes: 1002149 Changes: rust-signal-hook (0.1.13-3) unstable; urgency=medium . * Team upload. * Package signal-hook 0.1.13 from crates.io using debcargo 2.5.0 * Use a caret dependency for signal-hook-registry as
Bug#1001764: marked as done (mrgingham: autopkgtest failure with python3.10 as a supported version)
Your message dated Tue, 21 Dec 2021 20:24:14 + with message-id and subject line Bug#1001764: fixed in mrgingham 1.20-4 has caused the Debian Bug report #1001764, regarding mrgingham: autopkgtest failure with python3.10 as a supported version 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.) -- 1001764: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001764 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mrgingham Version: 1.20-3 Severity: serious X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: needs-update User: debian-pyt...@lists.debian.org Usertags: python3.10 python3-all-dev Control: affects -1 src:python3-defaults Hi Maintainer mrgingham's autopkgtests fail with python3.10 as a supported version [1]. This currently prevents the migration of python3-defaults to testing. I've copied what I hope is the relevant part of the log below. I believe the problem is due to the use of 'Testsuite: autopkgtest-pkg-python' and autodep8 always tests for all supported python versions, see #904999. Please either remove 'Testsuite: autopkgtest-pkg-python' from debian/control, or better yet, please adjust mrgingham so that it builds the extension for all supported python versions. Regards Graham [1] https://ci.debian.net/packages/m/mrgingham/testing/amd64/ autopkgtest [06:11:20]: test autodep8-python3: set -e ; for py in $(py3versions -r 2>/dev/null) ; do cd "$AUTOPKGTEST_TMP" ; echo "Testing with $py:" ; $py -c "import mrgingham; print(mrgingham)" ; done autopkgtest [06:11:20]: test autodep8-python3: [--- Testing with python3.10: Traceback (most recent call last): File "", line 1, in ModuleNotFoundError: No module named 'mrgingham' autopkgtest [06:11:20]: test autodep8-python3: ---] autopkgtest [06:11:20]: test autodep8-python3: - - - - - - - - - - results - - - - - - - - - - autodep8-python3 FAIL non-zero exit status 1 --- End Message --- --- Begin Message --- Source: mrgingham Source-Version: 1.20-4 Done: Dima Kogan We believe that the bug you reported is fixed in the latest version of mrgingham, 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 1001...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dima Kogan (supplier of updated mrgingham 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, 21 Dec 2021 11:20:53 -0800 Source: mrgingham Architecture: source Version: 1.20-4 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Dima Kogan Closes: 1001764 Changes: mrgingham (1.20-4) unstable; urgency=medium . * Building for ALL the available Python versions (Closes: #1001764) Checksums-Sha1: 974a7af150948f66cb2ce97457971414e8ce6cc5 2268 mrgingham_1.20-4.dsc f64455fc4fc0aa0a6b4c2ab8e3b8f8ae8da4790c 3596 mrgingham_1.20-4.debian.tar.xz 313f88f8e516828e7b8a990f117b1be7ff78b46e 19848 mrgingham_1.20-4_amd64.buildinfo Checksums-Sha256: 112dfb368f844353b287af9c08b5e2caf9790f49c118a00fdc5e130c9e468678 2268 mrgingham_1.20-4.dsc ef717f7ae5471e2ee1573ab84c93a6029025713c8ce4b68a706ea7a088a3aee9 3596 mrgingham_1.20-4.debian.tar.xz 28787f72c0598e14a5f5edc15f46b20ee25708a9697755a09ee627202e683481 19848 mrgingham_1.20-4_amd64.buildinfo Files: 8ec285acc54d60754ecdcbf8bfdcca56 2268 devel optional mrgingham_1.20-4.dsc f2be3554c352d03a29395a7d8acdb1b5 3596 devel optional mrgingham_1.20-4.debian.tar.xz f0cbbe517b9bfa3af3d43b195d0f4bac 19848 devel optional mrgingham_1.20-4_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEteL6GQ/fmv4hiInPrMfCzzCUEYgFAmHCL6EACgkQrMfCzzCU EYiWew/9H0qTF7xQwfJ9YywLPayAJ9aDRal8tv/tYR21pfxGUJU4xPS2jZEd5PjZ KrewjE4Df29s0OmSmBzRSwyfdb8omsuFNKlcpdpYRrbsl6oseRmobCCPNKGKXTle d2jdBUZFapoybzbFlQ4ZgX/eDoCJWoF38UJfQh4BiJBkYseZ75ce4bI4/jWXr5Xs ETV3CH71UWYRzcJPnfq4/YpQcZe9biWJAae+v0o89vcBNUznojhiBrJsa+K1Fr46 JFgee7W6RPqTEDUwdwC+c0tyJfxghcs2vptpfS0UpuZ6CSOlMloBPjj7wLqH3R2u 5WJ3B/VHrcf2CTxWHvbmCkSlRRCsT0m7ZjNmfdmdsDnI4bbR30hxrS4145+yoYWI sbXa5j+qBJhEjCzCEZNvadsIm7b5Zpple25Q0ykgTcPNc6qgn729TwnbnwcDEFoH
Bug#1002138: marked as done (pyftdi: FTBFS: AttributeError: 'NoneType' object has no attribute 'split')
Your message dated Tue, 21 Dec 2021 20:24:57 + with message-id and subject line Bug#1002138: fixed in pyftdi 0.53.3-1 has caused the Debian Bug report #1002138, regarding pyftdi: FTBFS: AttributeError: 'NoneType' object has no attribute 'split' 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.) -- 1002138: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002138 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pyftdi Version: 0.52.9-4 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211220 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > sphinx-build -W -b html ./pyftdi/doc ./pyftdi/doc/html > Running Sphinx v4.3.2 > making output directory... done > building [mo]: targets for 0 po files that are out of date > building [html]: targets for 23 source files that are out of date > updating environment: [new config] 23 added, 0 changed, 0 removed > reading sources... [ 4%] api/eeprom > reading sources... [ 8%] api/ftdi > reading sources... [ 13%] api/gpio > reading sources... [ 17%] api/i2c > reading sources... [ 21%] api/index > reading sources... [ 26%] api/misc > reading sources... [ 30%] api/spi > reading sources... [ 34%] api/uart > reading sources... [ 39%] api/usbtools > reading sources... [ 43%] authors > reading sources... [ 47%] defs > reading sources... [ 52%] eeprom > reading sources... [ 56%] features > reading sources... [ 60%] gpio > reading sources... [ 65%] index > reading sources... [ 69%] installation > reading sources... [ 73%] license > reading sources... [ 78%] pinout > reading sources... [ 82%] requirements > reading sources... [ 86%] testing > reading sources... [ 91%] tools > reading sources... [ 95%] troubleshooting > reading sources... [100%] urlscheme > > looking for now-outdated files... none found > pickling environment... done > checking consistency... done > preparing documents... done > writing output... [ 4%] api/eeprom > writing output... [ 8%] api/ftdi > writing output... [ 13%] api/gpio > writing output... [ 17%] api/i2c > writing output... [ 21%] api/index > writing output... [ 26%] api/misc > writing output... [ 30%] api/spi > writing output... [ 34%] api/uart > writing output... [ 39%] api/usbtools > writing output... [ 43%] authors > writing output... [ 47%] defs > writing output... [ 52%] eeprom > writing output... [ 56%] features > writing output... [ 60%] gpio > writing output... [ 65%] index > writing output... [ 69%] installation > writing output... [ 73%] license > writing output... [ 78%] pinout > writing output... [ 82%] requirements > writing output... [ 86%] testing > writing output... [ 91%] tools > writing output... [ 95%] troubleshooting > writing output... [100%] urlscheme > > generating indices... genindex py-modindex done > writing additional pages... search done > copying images... [ 50%] images/i2c_wiring.png > copying images... [100%] images/spi_wiring.png > > copying static files... done > copying extra files... done > dumping search index in English (code: en)... done > dumping object inventory... done > build succeeded. > > The HTML pages are in pyftdi/doc/html. > cd /<>/pyftdi/doc/html && find . -type f -print0 | xargs -0 sed > -i 's/https:\/\/fonts.googleapis.com//g' > dh_auto_install -i > I: pybuild base:237: /usr/bin/python3 setup.py install --root > /<>/debian/python3-ftdi > running install > /usr/lib/python3/dist-packages/setuptools/command/install.py:34: > SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and > pip and other standards-based tools. > warnings.warn( > running build > running build_py > running build_scripts > running install_lib > creating /<>/debian/python3-ftdi > creating /<>/debian/python3-ftdi/usr > creating /<>/debian/python3-ftdi/usr/lib > creating /<>/debian/python3-ftdi/usr/lib/python3.9 > creating /<>/debian/python3-ftdi/usr/lib/python3.9/dist-packages > creating > /<>/debian/python3-ftdi/usr/lib/python3.9/dist-packages/pyftdi > copying /<>/.pybuild/cpython3_3.9_ftdi/build/pyftdi/__init__.py > -> /<>/debian/python3-ftdi/usr/lib/python3.9/dist-packages/pyftdi > copying /<>/.pybuild/cpython3_3.9_ftdi/build/pyftdi/eeprom.py -> > /<>/debian/python3-ftdi/usr/lib/python3.9/dist-packages/pyftdi > copying /<>/.pybuild/cpython3_3.9_ftdi/build/pyftdi/spi.py -> > /<>/debian/python3-ftdi/usr/lib/python3.9/dist-packages/pyftdi > creating >
Processed: tagging 1002093, bug 1002093 is forwarded to https://github.com/gooddata/DBD-MariaDB/issues/164
Processing commands for cont...@bugs.debian.org: > tags 1002093 + upstream Bug #1002093 [src:libdbd-mariadb-perl] libdbd-mariadb-perl: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity Added tag(s) upstream. > forwarded 1002093 https://github.com/gooddata/DBD-MariaDB/issues/164 Bug #1002093 [src:libdbd-mariadb-perl] libdbd-mariadb-perl: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity Set Bug forwarded-to-address to 'https://github.com/gooddata/DBD-MariaDB/issues/164'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1002093: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002093 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1002101 marked as pending in gjs
Processing control commands: > tag -1 pending Bug #1002101 [src:gjs] gjs: FTBFS with Meson 0.60.2: ../meson.build:578:0: ERROR: "install_dir" must be specified when installing a target Added tag(s) pending. -- 1002101: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002101 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1002063: libvtk9.1: missing Breaks+Replaces: libvtk9 (<< 9.1.0+really9.1.0)
* Andreas Beckmann [2021-12-21 21:19]: On 21/12/2021 10.07, Jochen Sprickerhof wrote: While I agree that both packages conflict, I'm not sure if proposing a Breaks+Replaces is the proper solution here (and in general). Normally we want to have the library packages to be coinstallable and thus the packages only provide non conflicting files. Could you maybe adopt your template to mention that this hints to a problem in the package and propose to look into resolving the conflict as an alternative solution? What about In case of shared library packages where the conflicting files do not contain the SOVERSION in their name or path, please also consider alternative solutions for solving the conflict and avoiding Breaks+Replaces for easier upgrades in the future. Ideally shared libraries of different SOVERSIONs should only contain non-conflicting files and thus be co-installable for smooth upgrades. Sounds good :). signature.asc Description: PGP signature
Bug#1002101: marked as pending in gjs
Control: tag -1 pending Hello, Bug #1002101 in gjs 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/gnome-team/gjs/-/commit/70f4a8d5f7d325abc8496eb2d288388304203498 Add patch from upstream to fix FTBFS with meson 0.60.2 Closes: #1002101 (this message was generated automatically) -- Greetings https://bugs.debian.org/1002101
Processed: tagging 1002093
Processing commands for cont...@bugs.debian.org: > tags 1002093 + confirmed Bug #1002093 [src:libdbd-mariadb-perl] libdbd-mariadb-perl: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity Added tag(s) confirmed. > thanks Stopping processing here. Please contact me if you need assistance. -- 1002093: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002093 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1002063: libvtk9.1: missing Breaks+Replaces: libvtk9 (<< 9.1.0+really9.1.0)
On 21/12/2021 10.07, Jochen Sprickerhof wrote: While I agree that both packages conflict, I'm not sure if proposing a Breaks+Replaces is the proper solution here (and in general). Normally we want to have the library packages to be coinstallable and thus the packages only provide non conflicting files. Could you maybe adopt your template to mention that this hints to a problem in the package and propose to look into resolving the conflict as an alternative solution? What about In case of shared library packages where the conflicting files do not contain the SOVERSION in their name or path, please also consider alternative solutions for solving the conflict and avoiding Breaks+Replaces for easier upgrades in the future. Ideally shared libraries of different SOVERSIONs should only contain non-conflicting files and thus be co-installable for smooth upgrades. Andreas
Bug#1001122: Processed: Re: Bug#1001122: src:growlight: fails to migrate to testing for too long: autopkgtest regression
Hi Nick, On 21-12-2021 20:52, nick black wrote: well, as i noted above, this use case certainly isn't the standard way growlight will be used (although it's a valid one, and one worth fixing -- this was a valuable exercise, and i appreciate autopkgtests spotting this regression!). so it's not very important to users...but at the same time, it was considered important enough to drop the package from testing =]. so i guess i'm getting a bit of a mixed message here. I understand why you say that. the way i read it, this was critical to fix for the autopkgtests/transition regime, and relatively unimportant for most users. so i agree, we can do without the versioned dep. thanks for walking me through your thinking. But indeed, this. We (the Release Team) have decided that there's two items RC that are relevant for this case: autopkgtest failure and out-of-sync for too long. What's the *reason* for the autopkgtest failure hardly matters as the outcome for nearly everything is black/white due to automation. I mean an autopkgtest that fails because a text changes in output somewhere (yes, I see this a lot), is similarly blocking as segfault during every use. We do accept exceptions once in a while, but the baseline is, it should work. We try to have a balance here; there's a carrot (reduced migration and less rules during the freeze) and a stick (it has to work, otherwise). Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#1002292: node-babel7: ships /usr/share/nodejs/babel-plugin-add-module-exports/*, already in node-babel-plugin-add-module-exports
Package: node-babel7 Version: 7.16.6+~cs215.259.185-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install because it tries to overwrite other packages filea. If node-babel-plugin-add-module-exports is to be merged into node-babel7, please RM it and add corresponding Breaks+Replaces, otherwise use the already packaged copy. >From the attached log (scroll to the bottom...): Preparing to unpack .../node-babel7_7.16.6+~cs215.259.185-2_all.deb ... Unpacking node-babel7 (7.16.6+~cs215.259.185-2) ... dpkg: error processing archive /var/cache/apt/archives/node-babel7_7.16.6+~cs215.259.185-2_all.deb (--unpack): trying to overwrite '/usr/share/nodejs/babel-plugin-add-module-exports/lib/index.js', which is also in package node-babel-plugin-add-module-exports 1.0.4+dfsg1~cs5.8.0-2 Errors were encountered while processing: /var/cache/apt/archives/node-babel7_7.16.6+~cs215.259.185-2_all.deb cheers, Andreas node-babel-plugin-add-module-exports=1.0.4+dfsg1~cs5.8.0-2_node-babel7=7.16.6+~cs215.259.185-2.log.gz Description: application/gzip
Bug#1002060: liblunar-date-doc: missing Breaks+Replaces: liblunar-date-dev (<< 3)
Hi, another issue I noticed in liblunar-date-3.0-1: It is missing a corresponding Breaks to the existing Replaces. Without it the following sequence install liblunar-date-2.0-0 install liblunar-date-3.0-1 remove liblunar-date-3.0-1 will result in liblunar-date-2.0-0 having lost all its lunar-date.mo files, while dpkg considers it correctly installed. I would also recommend to use Breaks+Replaces: liblunar-date-2.0-0 (<< 3) in case lunar-date needs to be updated in stable at some point, because the (<= 2.4.0-8) will no longer be sufficient in this case. Andreas
Bug#1001122: Processed: Re: Bug#1001122: src:growlight: fails to migrate to testing for too long: autopkgtest regression
well, as i noted above, this use case certainly isn't the standard way growlight will be used (although it's a valid one, and one worth fixing -- this was a valuable exercise, and i appreciate autopkgtests spotting this regression!). so it's not very important to users...but at the same time, it was considered important enough to drop the package from testing =]. so i guess i'm getting a bit of a mixed message here. the way i read it, this was critical to fix for the autopkgtests/transition regime, and relatively unimportant for most users. so i agree, we can do without the versioned dep. thanks for walking me through your thinking. signature.asc Description: PGP signature
Bug#1002182: qutebrowser: FTBFS: AttributeError: 'NoneType' object has no attribute 'split'
Hi, On Tue, Dec 21, 2021 at 07:12:26PM +0100, Axel Beckert wrote: > > That seems like a false-positive: The dataclasses backport is only > > required for Python 3.6, but Debian sets "Depends: python3 (>= 3.7)" > > already. > […] > > That smells like a bug in dh-python. > > I tried downgrading dh-python until it no more FTBFS. It doesn't FTBFS > with dh-python 5.2024 and the first version it FTBFS is 5.20211213. > > The changelog entry of 5.20211213 contains these potential causes, at > least from my point of view: > >* Handle dist-info extra sections the same way we do for requirements.txt. > (closes: 998374) That seems to be related to the "flit" integration, a build system which qutebrowser does not use: https://flit.readthedocs.io/ >* Add new pep517 plugin that uses python3-build + python3-installer to > build > Python modules as wheels and then unpack the wheel. This is the new > interface used by modern Python packaging tools. (Closes: #984824) Could be, but it't not :) > Full entry (in cases something didn't look suspicious to me) at > https://packages.qa.debian.org/d/dh-python/news/20211214T010008Z.html > > Florian: Any idea which of these might have broken this? It's "Add support for environment markers.". Environment markers are basically conditional dependencies, e.g. for a given Python version or OS only. The crash happens here: https://salsa.debian.org/python-team/tools/dh-python/-/blob/5.20211217/dhpython/pydist.py#L522 because "dependency" is None. That's coming from here: https://salsa.debian.org/python-team/tools/dh-python/-/blob/5.20211217/dhpython/pydist.py#L516 i.e. is the return value of "guess_deps". Looking at that, we spot our error message about dataclasses: https://salsa.debian.org/python-team/tools/dh-python/-/blob/5.20211217/dhpython/pydist.py#L313-317 ...but also a strange commented out "return pname" which has been around for 7 years: https://salsa.debian.org/python-team/tools/dh-python/-/commit/de7db9bd0021cee65e477f11cd69cfd93350bd2e Due to the commented out return, the function ends and implicitly returns None. The code which crashes due to that None value is very recent: https://salsa.debian.org/python-team/tools/dh-python/-/commit/832f01c9c7da22a1d00887d8ce0e6be9893bdf3e So I suppose it would be good if someone could forward this do dh-python, I use the Debian bugtracker too seldom to know what the best way to do this would be (but if preferable, I can open a new bug). > And is the suggestion to add "dataclasses python3-dataclasses" line to > debian/py3dist-overrides something we should simply do or is this an > issue which we should make the dh-python maintainers aware of? I must > admit, I still don't understand what this is dh-python argues about. > Maybe someone has some more Python insight for a non-pythonista? Perhaps both. So what dh-python seems to be doing here is to look at the dependencies declared in a "requirements.txt" (a somewhat common way to specify dependencies for Python projects) and check whether the Debian packaging mirrors those requirements as well. Here is the line in question: https://github.com/qutebrowser/qutebrowser/blob/v2.4.0/requirements.txt#L5 So this declares that qutebrowser needs the "dataclasses" backport for Python versions older than 3.7 (it still supports Python 3.6, though that will change as soon as 3.0.0 is finished: https://github.com/qutebrowser/qutebrowser/issues/6905). However, the Debian package for qutebrowser declares "Depends: python3 (>= 3.7)", so that dependency actually is irrelevant for Debian. Should dh-python handle that case? Well, maybe, but it sure shouldn't crash. Florian -- m...@the-compiler.org | https://www.qutebrowser.org https://bruhin.software/ | https://github.com/sponsors/The-Compiler/ GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc I love long mails! | https://email.is-not-s.ms/ signature.asc Description: PGP signature
Processed: Fw: Bug#1002062: Acknowledgement (RFS: mlucas/20.1.1-1 [RC] -- program to perform Lucas-Lehmer test on a Mersenne number)
Processing commands for cont...@bugs.debian.org: > package src:mlucas Limiting to bugs with field 'package' containing at least one of 'src:mlucas' Limit currently set to 'package':'src:mlucas' > block 957547 by 1002062 Bug #957547 [src:mlucas] mlucas: ftbfs with GCC-10 957547 was not blocked by any bugs. 957547 was not blocking any bugs. Added blocking bug(s) of 957547: 1002062 > block 945666 by 1002062 Bug #945666 [src:mlucas] mlucas: Python2 removal in sid/bullseye Bug #966758 [src:mlucas] mlucas: Unversioned Python removal in sid/bullseye 945666 was not blocked by any bugs. 945666 was blocking: 937695 Added blocking bug(s) of 945666: 1002062 966758 was not blocked by any bugs. 966758 was blocking: 937695 Added blocking bug(s) of 966758: 1002062 > thanks Stopping processing here. Please contact me if you need assistance. -- 945666: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945666 957547: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957547 966758: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966758 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1001122: Processed: Re: Bug#1001122: src:growlight: fails to migrate to testing for too long: autopkgtest regression
Hi Nick, On 21-12-2021 19:52, nick black wrote: well, if you have an older version of notcurses, you're going to run into this growlight problem, so "solving" this problem for Debian would seem to me to require the versioned dep? The problem exist only in unstable, and to have the problem, you'd need to not upgrade notcurses although it has a newer version. So, it's technically correct to need the newer version. But then the question is, how big is the issue? Do we need to tell users of growlight to update notcurses by having the tighter relation? Remember, because of the transition, growlight already has the versioned dependency on the newer SONAME version. So, it's more a matter of, does it really help and is the current issue worth it. So technically you may be right, my argument is more, is it worth it (because how much is really improved)? Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#1002101: gjs: FTBFS: collect2: error: ld returned 1 exit status
Control: retitle -1 gjs: FTBFS with Meson 0.60.2: ../meson.build:578:0: ERROR: "install_dir" must be specified when installing a target On Tue, 21 Dec 2021 at 16:53:41 +0100, Lucas Nussbaum wrote: > Relevant part (hopefully): [meson-logs/meson-log.txt follows] This doesn't look like the reason for FTBFS. The reason for FTBFS seems to be this: > ../meson.build:578:0: ERROR: "install_dir" must be specified when installing > a target > dh_auto_configure: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. > --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc > --localstatedir=/var --libdir=lib/x86_64-linux-gnu -Dauto_features=enabled > -Dprofiler=disabled returned exit code 1 smcv
Processed: Re: Bug#1002101: gjs: FTBFS: collect2: error: ld returned 1 exit status
Processing control commands: > retitle -1 gjs: FTBFS with Meson 0.60.2: ../meson.build:578:0: ERROR: > "install_dir" must be specified when installing a target Bug #1002101 [src:gjs] gjs: FTBFS: collect2: error: ld returned 1 exit status Changed Bug title to 'gjs: FTBFS with Meson 0.60.2: ../meson.build:578:0: ERROR: "install_dir" must be specified when installing a target' from 'gjs: FTBFS: collect2: error: ld returned 1 exit status'. -- 1002101: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002101 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1002290: dh_python3 needing contextvars -- not a problem with my package, then?
Package: dh-python
Version: 5.20211217
Severity: grave
python-anyio package is supposedly broken (bug #1002179), but the build
log makes me think it's a problem with dh-python:
>dh_python3 -O--buildsystem=pybuild
> I: dh_python3 pydist:313: Cannot find package that provides
contextvars. Please add package that provides it to Build-Depends or
add "contextvars python3-contextvars" line to debian/py3dist-overrides
or add proper dependency to Depends by hand and ignore this info.
> Traceback (most recent call last):
> File "/usr/bin/dh_python3", line 280, in
> main()
> File "/usr/bin/dh_python3", line 201, in main
> dependencies.parse(stats, options)
> File "/usr/share/dh-python/dhpython/depends.py", line 242, in parse
> deps = parse_pydep(self.impl, fn, bdep=self.bdep,
**section_options)
> File "/usr/share/dh-python/dhpython/pydist.py", line 522, in
parse_pydep
> for part in dependency.split(','))
> AttributeError: 'NoneType' object has no attribute 'split'
> make: *** [debian/rules:8: binary] Error 1
Cheers,
J.Puydt
Bug#1002197: marked as done (entrypoints: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p 3.9 returned exit code 13)
Your message dated Tue, 21 Dec 2021 19:03:34 +
with message-id
and subject line Bug#1002197: fixed in entrypoints 0.3-10
has caused the Debian Bug report #1002197,
regarding entrypoints: FTBFS: dh_auto_test: error: pybuild --test -i
python{version} -p 3.9 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.)
--
1002197: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002197
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: entrypoints
Version: 0.3-9
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211220 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules binary
> dh binary --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild plugin_flit:70: Installing file /<>/entrypoints.py ->
> /<>/.pybuild/cpython3_3.9_entrypoints/build/entrypoints.py
> I: pybuild plugin_flit:79: Writing dist-info
> /<>/.pybuild/cpython3_3.9_entrypoints/build/
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:237: cd
> /<>/.pybuild/cpython3_3.9_entrypoints/build; python3.9 -m
> unittest discover -v
> tests.test_entrypoints (unittest.loader._FailedTest) ... ERROR
>
> ==
> ERROR: tests.test_entrypoints (unittest.loader._FailedTest)
> --
> ImportError: Failed to import test module: tests.test_entrypoints
> Traceback (most recent call last):
> File "/usr/lib/python3.9/unittest/loader.py", line 436, in _find_test_path
> module = self._get_module_from_name(name)
> File "/usr/lib/python3.9/unittest/loader.py", line 377, in
> _get_module_from_name
> __import__(name)
> File
> "/<>/.pybuild/cpython3_3.9_entrypoints/build/tests/test_entrypoints.py",
> line 5, in
> import pytest
> ModuleNotFoundError: No module named 'pytest'
>
>
> --
> Ran 1 test in 0.000s
>
> FAILED (errors=1)
> E: pybuild pybuild:355: test: plugin flit failed with: exit code=1: cd
> /<>/.pybuild/cpython3_3.9_entrypoints/build; python3.9 -m
> unittest discover -v
> dh_auto_test: error: pybuild --test -i python{version} -p 3.9 returned exit
> code 13
The full build log is available from:
http://qa-logs.debian.net/2021/12/20/entrypoints_0.3-9_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: entrypoints
Source-Version: 0.3-10
Done: Julien Puydt
We believe that the bug you reported is fixed in the latest version of
entrypoints, 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 1002...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Julien Puydt (supplier of updated entrypoints 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, 21 Dec 2021 19:45:05 +0100
Source: entrypoints
Architecture: source
Version: 0.3-10
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team
Changed-By: Julien Puydt
Closes: 1002197
Changes:
entrypoints (0.3-10) unstable; urgency=medium
.
* Add b-depends on python3-pytest. (Closes: #1002197)
Checksums-Sha1:
a1caad292931f3ffadaf00e9c054dab7c02d4ee5 2112 entrypoints_0.3-10.dsc
937dea8d10b5d797ddeafcc06c42857c02341885 3424 entrypoints_0.3-10.debian.tar.xz
92d96200b6aae04b0bafe01cc481afd23dbd6a0e 7758
entrypoints_0.3-10_source.buildinfo
Checksums-Sha256:
Processed: reassign 1001841 to src:liblouisutdml, forcibly merging 1001841 1002097
Processing commands for cont...@bugs.debian.org: > reassign 1001841 src:liblouisutdml Bug #1001841 [liblouisutdml] liblouisutdml autopkgtest failing with the new liblouis Bug reassigned from package 'liblouisutdml' to 'src:liblouisutdml'. Ignoring request to alter found versions of bug #1001841 to the same values previously set Ignoring request to alter fixed versions of bug #1001841 to the same values previously set > forcemerge 1001841 1002097 Bug #1001841 [src:liblouisutdml] liblouisutdml autopkgtest failing with the new liblouis Bug #1001841 [src:liblouisutdml] liblouisutdml autopkgtest failing with the new liblouis Marked as found in versions liblouisutdml/2.10.0-3. Added tag(s) ftbfs, bookworm, and sid. Bug #1002097 [src:liblouisutdml] liblouisutdml: FTBFS: tests fail Set Bug forwarded-to-address to 'https://github.com/liblouis/liblouisutdml/issues/75'. Merged 1001841 1002097 > thanks Stopping processing here. Please contact me if you need assistance. -- 1001841: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001841 1002097: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002097 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed (with 1 error): reassign 1001841 to liblouisutdml, severity of 1001841 is serious, forcibly merging 1001841 1002097
Processing commands for cont...@bugs.debian.org: > reassign 1001841 liblouisutdml Bug #1001841 [liblouis] liblouisutdml autopkgtest failing with the new liblouis Bug reassigned from package 'liblouis' to 'liblouisutdml'. No longer marked as found in versions 3.20.0-1. Ignoring request to alter fixed versions of bug #1001841 to the same values previously set > severity 1001841 serious Bug #1001841 [liblouisutdml] liblouisutdml autopkgtest failing with the new liblouis Severity set to 'serious' from 'normal' > forcemerge 1001841 1002097 Bug #1001841 [liblouisutdml] liblouisutdml autopkgtest failing with the new liblouis Unable to merge bugs because: package of #1002097 is 'src:liblouisutdml' not 'liblouisutdml' Failed to forcibly merge 1001841: Did not alter merged bugs. > thanks Stopping processing here. Please contact me if you need assistance. -- 1001841: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001841 1002097: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002097 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1001122: Processed: Re: Bug#1001122: src:growlight: fails to migrate to testing for too long: autopkgtest regression
if i don't need the versioned dep, there is -- so far as i can tell -- no reason to upload a new growlight at all, unless i need do so to retrigger the autopkgtests and allow a transition to testing. (sorry for my ignorance--i'm still applying for DD) signature.asc Description: PGP signature
Bug#1001122: Processed: Re: Bug#1001122: src:growlight: fails to migrate to testing for too long: autopkgtest regression
> I don't think you need the versioned depends really. Or did I miss > something? well, if you have an older version of notcurses, you're going to run into this growlight problem, so "solving" this problem for Debian would seem to me to require the versioned dep? i'm sure you're much more knowledgeable though, so please do explain. signature.asc Description: PGP signature
Bug#1002197: marked as pending in entrypoints
Control: tag -1 pending Hello, Bug #1002197 in entrypoints reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/entrypoints/-/commit/1282bdaf0febd9d4fa9a2b00a6c7e224af6054ee Add b-depends on python3-pytest (Closes: #1002197) (this message was generated automatically) -- Greetings https://bugs.debian.org/1002197
Processed: Bug#1002197 marked as pending in entrypoints
Processing control commands:
> tag -1 pending
Bug #1002197 [src:entrypoints] entrypoints: FTBFS: dh_auto_test: error: pybuild
--test -i python{version} -p 3.9 returned exit code 13
Added tag(s) pending.
--
1002197: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002197
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1002141: marked as done (osmid: FTBFS: libfmt-dev : Breaks: libspdlog-dev (< 1:1.9.2+ds-0.1) but 1:1.8.5+ds-3 is to be installed)
Your message dated Tue, 21 Dec 2021 19:41:15 +0100 with message-id and subject line Re: Bug#1002141: osmid: FTBFS: libfmt-dev : Breaks: libspdlog-dev (< 1:1.9.2+ds-0.1) but 1:1.8.5+ds-3 is to be installed has caused the Debian Bug report #1002141, regarding osmid: FTBFS: libfmt-dev : Breaks: libspdlog-dev (< 1:1.9.2+ds-0.1) but 1:1.8.5+ds-3 is to be installed 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.) -- 1002141: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002141 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: osmid Version: 0.8.0~repack-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211220 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: cmake, debhelper-compat (= 13), libasound2-dev, > liboscpack-dev, libspdlog-dev (>= 1:1.5.0+ds), build-essential, fakeroot > Filtered Build-Depends: cmake, debhelper-compat (= 13), libasound2-dev, > liboscpack-dev, libspdlog-dev (>= 1:1.5.0+ds), build-essential, fakeroot > dpkg-deb: building package 'sbuild-build-depends-main-dummy' in > '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'. > Ign:1 copy:/<>/apt_archive ./ InRelease > Get:2 copy:/<>/apt_archive ./ Release [957 B] > Ign:3 copy:/<>/apt_archive ./ Release.gpg > Get:4 copy:/<>/apt_archive ./ Sources [409 B] > Get:5 copy:/<>/apt_archive ./ Packages [493 B] > Fetched 1859 B in 0s (0 B/s) > Reading package lists... > Reading package lists... > > Install main build dependencies (apt-based resolver) > > > Installing build dependencies > Reading package lists... > Building dependency tree... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > libfmt-dev : Breaks: libspdlog-dev (< 1:1.9.2+ds-0.1) but 1:1.8.5+ds-3 is to > be installed > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://qa-logs.debian.net/2021/12/20/osmid_0.8.0~repack-2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- On 2021-12-21 17:08:43, Lucas Nussbaum wrote: > Source: osmid > Version: 0.8.0~repack-2 > Severity: serious > Justification: FTBFS > Tags: bookworm sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-20211220 ftbfs-bookworm > > Hi, > > During a rebuild of all packages in sid, your package failed to build > on amd64. Fixed in spdlog Cheers > > > Relevant part (hopefully): > > +--+ > > | Install package build dependencies > >| > > +--+ > > > > > > Setup apt archive > > - > > > > Merged Build-Depends: cmake, debhelper-compat (= 13), libasound2-dev, > > liboscpack-dev, libspdlog-dev (>= 1:1.5.0+ds), build-essential, fakeroot > > Filtered Build-Depends: cmake, debhelper-compat (= 13), libasound2-dev, > > liboscpack-dev, libspdlog-dev (>= 1:1.5.0+ds), build-essential, fakeroot > > dpkg-deb: building package 'sbuild-build-depends-main-dummy' in > > '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'. > > Ign:1 copy:/<>/apt_archive ./ InRelease > > Get:2 copy:/<>/apt_archive ./ Release [957 B] > > Ign:3 copy:/<>/apt_archive ./ Release.gpg > > Get:4 copy:/<>/apt_archive ./ Sources [409 B] > > Get:5 copy:/<>/apt_archive ./ Packages [493 B] > >
Bug#1002169: marked as done (intel-gmmlib: FTBFS: libfmt-dev : Breaks: libspdlog-dev (< 1:1.9.2+ds-0.1) but 1:1.8.5+ds-3 is to be installed)
Your message dated Tue, 21 Dec 2021 19:41:03 +0100 with message-id and subject line Re: Bug#1002169: intel-gmmlib: FTBFS: libfmt-dev : Breaks: libspdlog-dev (< 1:1.9.2+ds-0.1) but 1:1.8.5+ds-3 is to be installed has caused the Debian Bug report #1002169, regarding intel-gmmlib: FTBFS: libfmt-dev : Breaks: libspdlog-dev (< 1:1.9.2+ds-0.1) but 1:1.8.5+ds-3 is to be installed 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.) -- 1002169: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002169 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: intel-gmmlib Version: 21.3.3+ds1-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211220 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: debhelper-compat (= 13), cmake, libspdlog-dev, > build-essential, fakeroot > Filtered Build-Depends: debhelper-compat (= 13), cmake, libspdlog-dev, > build-essential, fakeroot > dpkg-deb: building package 'sbuild-build-depends-main-dummy' in > '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'. > Ign:1 copy:/<>/apt_archive ./ InRelease > Get:2 copy:/<>/apt_archive ./ Release [957 B] > Ign:3 copy:/<>/apt_archive ./ Release.gpg > Get:4 copy:/<>/apt_archive ./ Sources [385 B] > Get:5 copy:/<>/apt_archive ./ Packages [464 B] > Fetched 1806 B in 0s (0 B/s) > Reading package lists... > Reading package lists... > > Install main build dependencies (apt-based resolver) > > > Installing build dependencies > Reading package lists... > Building dependency tree... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > libfmt-dev : Breaks: libspdlog-dev (< 1:1.9.2+ds-0.1) but 1:1.8.5+ds-3 is to > be installed > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://qa-logs.debian.net/2021/12/20/intel-gmmlib_21.3.3+ds1-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- On 2021-12-21 17:08:13, Lucas Nussbaum wrote: > Source: intel-gmmlib > Version: 21.3.3+ds1-1 > Severity: serious > Justification: FTBFS > Tags: bookworm sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-20211220 ftbfs-bookworm > > Hi, > > During a rebuild of all packages in sid, your package failed to build > on amd64. Fixed in spdlog Cheers > > > Relevant part (hopefully): > > +--+ > > | Install package build dependencies > >| > > +--+ > > > > > > Setup apt archive > > - > > > > Merged Build-Depends: debhelper-compat (= 13), cmake, libspdlog-dev, > > build-essential, fakeroot > > Filtered Build-Depends: debhelper-compat (= 13), cmake, libspdlog-dev, > > build-essential, fakeroot > > dpkg-deb: building package 'sbuild-build-depends-main-dummy' in > > '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'. > > Ign:1 copy:/<>/apt_archive ./ InRelease > > Get:2 copy:/<>/apt_archive ./ Release [957 B] > > Ign:3 copy:/<>/apt_archive ./ Release.gpg > > Get:4 copy:/<>/apt_archive ./ Sources [385 B] > > Get:5 copy:/<>/apt_archive ./ Packages [464 B] > > Fetched 1806 B in 0s (0 B/s) > > Reading package lists... > > Reading package lists... > > > > Install main build dependencies (apt-based resolver) > >
Bug#1001122: Processed: Re: Bug#1001122: src:growlight: fails to migrate to testing for too long: autopkgtest regression
Hi Nick, On 21-12-2021 14:53, nick black wrote: the growlight bug: https://github.com/dankamongmen/growlight/issues/153 it was determined that this was a flaw in Notcurses when > input was redirected from a file. it has been resolved, So, I would reassign the bug to notcurses, mark it as affects growlight and be done with it. and the fix will be present in Notcurses 3.0.2. i'll then add a versioned dep on libnotcurses3 3.0.2+ to growlight, and reupload 1.2.38-n with that version requirement (and marking this bug as closed). I don't think you need the versioned depends really. Or did I miss something? Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#1002129: marked as done (flameshot: FTBFS: libfmt-dev : Breaks: libspdlog-dev (< 1:1.9.2+ds-0.1) but 1:1.8.5+ds-3 is to be installed)
Your message dated Tue, 21 Dec 2021 18:34:57 + with message-id and subject line Bug#1002129: fixed in flameshot 0.10.2+ds1-4 has caused the Debian Bug report #1002129, regarding flameshot: FTBFS: libfmt-dev : Breaks: libspdlog-dev (< 1:1.9.2+ds-0.1) but 1:1.8.5+ds-3 is to be installed 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.) -- 1002129: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002129 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: flameshot Version: 0.10.2+ds1-3 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211220 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: cmake (>= 3.13~), debhelper-compat (= 13), > libqt5svg5-dev, libspdlog-dev (>= 1:1.8.5~), qtbase5-dev, qttools5-dev, > qttools5-dev-tools, build-essential, fakeroot > Filtered Build-Depends: cmake (>= 3.13~), debhelper-compat (= 13), > libqt5svg5-dev, libspdlog-dev (>= 1:1.8.5~), qtbase5-dev, qttools5-dev, > qttools5-dev-tools, build-essential, fakeroot > dpkg-deb: building package 'sbuild-build-depends-main-dummy' in > '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'. > Ign:1 copy:/<>/apt_archive ./ InRelease > Get:2 copy:/<>/apt_archive ./ Release [957 B] > Ign:3 copy:/<>/apt_archive ./ Release.gpg > Get:4 copy:/<>/apt_archive ./ Sources [427 B] > Get:5 copy:/<>/apt_archive ./ Packages [511 B] > Fetched 1895 B in 0s (0 B/s) > Reading package lists... > Reading package lists... > > Install main build dependencies (apt-based resolver) > > > Installing build dependencies > Reading package lists... > Building dependency tree... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > libfmt-dev : Breaks: libspdlog-dev (< 1:1.9.2+ds-0.1) but 1:1.8.5+ds-3 is to > be installed > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://qa-logs.debian.net/2021/12/20/flameshot_0.10.2+ds1-3_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: flameshot Source-Version: 0.10.2+ds1-4 Done: Boyuan Yang We believe that the bug you reported is fixed in the latest version of flameshot, 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 1002...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Boyuan Yang (supplier of updated flameshot 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, 21 Dec 2021 13:19:19 -0500 Source: flameshot Architecture: source Version: 0.10.2+ds1-4 Distribution: unstable Urgency: medium Maintainer: Boyuan Yang Changed-By: Boyuan Yang Closes: 1002129 Changes: flameshot (0.10.2+ds1-4) unstable; urgency=medium . * Rebuild the package. * debian/control: Tighten build dependency to libspdlog-dev (>= 1:1.9~) to assist libfmt8 transition. (Closes: #1002129) Checksums-Sha1: 945b8ec6c7b8f185d534c652581fb19f18e8c3cf 1969 flameshot_0.10.2+ds1-4.dsc
Bug#1002266: marked as done (node-y18n: FTBFS: TypeError: Cannot read property 'text' of undefined)
Your message dated Tue, 21 Dec 2021 18:35:08 + with message-id and subject line Bug#1002266: fixed in node-y18n 5.0.8+~5.0.0-1 has caused the Debian Bug report #1002266, regarding node-y18n: FTBFS: TypeError: Cannot read property 'text' of undefined 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.) -- 1002266: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002266 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-y18n Version: 5.0.8-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211220 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > tsc > rollup -c > [36m > [1m./lib/cjs.ts[22m → [1m./build/index.cjs[22m...[39m > [1m[33m(!) Unresolved dependencies[39m[22m > [90mhttps://rollupjs.org/guide/en/#warning-treating-module-as-external-dependency[39m > [1mfs[22m (imported by lib/platform-shims/node.ts) > [1mutil[22m (imported by lib/platform-shims/node.ts) > [1mpath[22m (imported by lib/platform-shims/node.ts) > [1m[31m[!] [1m(plugin Typescript) TypeError: Cannot read property 'text' > of undefined[22m[1m[39m[22m > [2mTypeError: Cannot read property 'text' of undefined > at getExportedSymbolFromExportSpecifier > (/<>/debian/build_modules/@wessberg/rollup-plugin-ts/dist/cjs/index.js:2155:41) > at createExportSpecifierFromNameAndModifiers > (/<>/debian/build_modules/@wessberg/rollup-plugin-ts/dist/cjs/index.js:2176:29) > at visitInterfaceDeclaration$5 > (/<>/debian/build_modules/@wessberg/rollup-plugin-ts/dist/cjs/index.js:2518:32) > at visitNode$c > (/<>/debian/build_modules/@wessberg/rollup-plugin-ts/dist/cjs/index.js:2601:16) > at > /<>/debian/build_modules/@wessberg/rollup-plugin-ts/dist/cjs/index.js:2627:13 > at visitNodes (/usr/share/nodejs/typescript/lib/typescript.js:29880:30) > at Object.forEachChild > (/usr/share/nodejs/typescript/lib/typescript.js:30122:24) > at Object.childContinuation > (/<>/debian/build_modules/@wessberg/rollup-plugin-ts/dist/cjs/index.js:2626:52) > at visitModuleDeclaration$7 > (/<>/debian/build_modules/@wessberg/rollup-plugin-ts/dist/cjs/index.js:2528:28) > at visitNode$c > (/<>/debian/build_modules/@wessberg/rollup-plugin-ts/dist/cjs/index.js:2607:16)[22m > > make[1]: *** [debian/rules:12: override_dh_auto_build] Error 1 The full build log is available from: http://qa-logs.debian.net/2021/12/20/node-y18n_5.0.8-2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: node-y18n Source-Version: 5.0.8+~5.0.0-1 Done: Yadd We believe that the bug you reported is fixed in the latest version of node-y18n, 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 1002...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yadd (supplier of updated node-y18n 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, 21 Dec 2021 19:10:11 +0100 Source: node-y18n Architecture: source Version: 5.0.8+~5.0.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Yadd Closes: 1002266 Changes: node-y18n (5.0.8+~5.0.0-1) unstable; urgency=medium . * Team upload * Embed typescript declarations and repack * Fix build dependencies for rollup ≥ 2.61 (Closes: #1002266) Checksums-Sha1: fb1f4959defbef229a0266684608665562b70b16 2453 node-y18n_5.0.8+~5.0.0-1.dsc 1af95e72038d7780c88d5150905d10b153993cd5 1071 node-y18n_5.0.8+~5.0.0.orig-types-y18n.tar.gz 99f974c2f806a8988d48fae519620e20cc16556d 10524 node-y18n_5.0.8+~5.0.0.orig.tar.gz
Bug#1002060: [Debian-zh-dev] Bug#1002060: liblunar-date-doc: missing Breaks+Replaces: liblunar-date-dev (<< 3)
Hi, 在 2021-12-21星期二的 22:17 +0800，xiao sheng wen写道： > Control: tags -1 pending > > > Hi Andreas, > > Thanks for your bugreport. > > I do rename upstream NEWS to changelog-upstream to fix this bug.(In > 3.0.1-1, it rename to changelog :-( ) > > In old upstream version 2.4.0, there is a ChangeLog file under the top > level directory, > > this ChangeLog file is automatic installed by dh_installchangelogs: > > dh_installchangelogs > [...] > install -p -m0644 debian/changelog > debian/liblunar-date-dev/usr/share/doc/liblunar-date-dev/changelog.Debian > install -p -m0644 ./ChangeLog > debian/liblunar-date-dev/usr/share/doc/liblunar-date-dev/changelog > > > In new upstream verison 3.0.1, there is not this ChangeLog file. > > I'd uploaded the version 3.0.1-2 to mentors.d.n: > > https://mentors.debian.net/package/lunar-date/ Using the filename "changelog-upstream" is not a standard practice. Why not just keep using the old filename /usr/share/doc/liblunar-date-dev/changelog? As email title said, using Breaks+Replaces: liblunar-date-dev (<< 3) would be enough. Thanks, Boyuan signature.asc Description: This is a digitally signed message part
Bug#1002160: ignition-transport: FTBFS: build-dependency not installable: libignition-msgs5-5 (= 5.1.0+dfsg-7+b1)
The problems should be fixed by resolving the transition from experimental to unstable of the whole Ignition family: See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002286 On Tue, Dec 21, 2021 at 5:34 PM Lucas Nussbaum wrote: > Source: ignition-transport > Version: 8.0.0+dfsg-3 > Severity: serious > Justification: FTBFS > Tags: bookworm sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-20211220 ftbfs-bookworm > > Hi, > > During a rebuild of all packages in sid, your package failed to build > on amd64. > > > Relevant part (hopefully): > > > +--+ > > | Install package build dependencies >| > > > +--+ > > > > > > Setup apt archive > > - > > > > Merged Build-Depends: cmake, pkg-config, debhelper-compat (= 12), > libgtest-dev, libprotoc-dev, libprotobuf-dev, protobuf-compiler, uuid-dev, > libzmq3-dev (>= 3.0.0), libignition-msgs-dev (>= 5), libignition-cmake-dev > (>= 2), libsqlite3-dev, build-essential, fakeroot > > Filtered Build-Depends: cmake, pkg-config, debhelper-compat (= 12), > libgtest-dev, libprotoc-dev, libprotobuf-dev, protobuf-compiler, uuid-dev, > libzmq3-dev (>= 3.0.0), libignition-msgs-dev (>= 5), libignition-cmake-dev > (>= 2), libsqlite3-dev, build-essential, fakeroot > > dpkg-deb: building package 'sbuild-build-depends-main-dummy' in > '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'. > > Ign:1 copy:/<>/apt_archive ./ InRelease > > Get:2 copy:/<>/apt_archive ./ Release [957 B] > > Ign:3 copy:/<>/apt_archive ./ Release.gpg > > Get:4 copy:/<>/apt_archive ./ Sources [459 B] > > Get:5 copy:/<>/apt_archive ./ Packages [540 B] > > Fetched 1956 B in 0s (0 B/s) > > Reading package lists... > > Reading package lists... > > > > Install main build dependencies (apt-based resolver) > > > > > > Installing build dependencies > > Reading package lists... > > Building dependency tree... > > Some packages could not be installed. This may mean that you have > > requested an impossible situation or if you are using the unstable > > distribution that some required packages have not yet been created > > or been moved out of Incoming. > > The following information may help to resolve the situation: > > > > The following packages have unmet dependencies: > > libignition-msgs-dev : Depends: libignition-msgs5-5 (= 5.1.0+dfsg-7+b1) > but it is not going to be installed > > E: Unable to correct problems, you have held broken packages. > > apt-get failed. > > > The full build log is available from: > > http://qa-logs.debian.net/2021/12/20/ignition-transport_8.0.0+dfsg-3_unstable.log > > A list of current common problems and possible solutions is available at > http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! > > If you reassign this bug to another package, please marking it as > 'affects'-ing > this package. See https://www.debian.org/Bugs/server-control#affects > > If you fail to reproduce this, please provide a build log and diff it with > mine > so that we can identify if something relevant changed in the meantime. > > -- > debian-science-maintainers mailing list > debian-science-maintain...@alioth-lists.debian.net > > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers >
Processed: add found version
Processing commands for cont...@bugs.debian.org: > found 1002153 1.0.0-3 Bug #1002153 [src:rust-zbus] rust-zbus: FTBFS: build-dependency not installable: librust-zbus-macros-1.0.0+default-dev Marked as found in versions rust-zbus/1.0.0-3. > thanks Stopping processing here. Please contact me if you need assistance. -- 1002153: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002153 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1001764: More info
Hi. Graham Inggs writes: > numpy 1:1.21.4-2 in testing is already built for python3.9 and 3.10 > [1]. Search for 'cpython-3' and you should find files like: > > /usr/lib/python3/dist-packages/numpy/core/_multiarray_tests.cpython-310-x86_64-linux-gnu.so > /usr/lib/python3/dist-packages/numpy/core/_multiarray_tests.cpython-39-x86_64-linux-gnu.so Strange. I had a new version installed (1:1.21.4-3), and it only had python 3.9 files in there. An even newer python3-numpy ws just uploaded, and it has both 3.9 and 3.10. So I'm good there. >> What do I need to install to reproduce this bug? > > You should be able to reproduce this with all packages from unstable, > or all packages from testing and only packages built from > src:python3-defaults from unstable, e.g. python3, python3-all ,etc. > Follow the links in the unstable and testing columns [2], and note the > 'Trigger/Pinned packages' column on the testing page. OK. mrgingham currently will build for only ONE python version: the one that runs when you invoke "python3". You're saying that I should build for ALL the versions that "py3versions" reports, yes? And all the resulting binaries should go into the python3-mrgingham package, yes? Thanks.
Bug#1002276: schroot: FTBFS: The following tests FAILED: 3 - sbuild-chroot-config (Failed)
Hi Lucas, This isn't a schroot bug. It's actually down to a behaviour change in "fakeroot". If you run "dpkg-buildpackage" by hand, then "cd debian/build" and then run "fakeroot ctest -V", you'll see this: 3: 1) test: test_config::test_construction_file (E) 3: setUp() failed 3: - uncaught exception of type std::exception (or derived). 3: - /home/rleigh/schroot-1.6.10/debian/build/test/testdata/config.ex1: File is not owned by user root This is a behaviour change or breakage in fakeroot in unstable, from what I can tell. The same package built on bullseye runs the tests as expected. If you look at tests/setup-test-data[.cmake] you'll see that we do an explicit chown of the test datafiles to root:root specifically so that the unit tests will check the ownership correctly. I would suggest reassigning this bug to fakeroot. As an aside, I did suggest several years back that schroot should be retired from Debian given its obsolescence. Since docker and other alternative virtualisation technologies can do a better job of creating and tearing down temporary but well-defined build environments, I think it would be worth spending a day adding that support to sbuild , and then dropping the schroot support. While I'm happy to answer the occasional question, I am no longer in a position to properly support schroot, and I myself haven't used it in years--it's past time to move on from using it IMHO, and so I'd just like to reiterate my suggestion that its removal be investigated. In sbuild, lib/Sbuild/ChrootSchroot.pm could be replaced with an alternative ChrootDocker.pm which sets up and provisions a docker container, then runs commands and tears it down. Kind regards, Roger > -Original Message- > From: Lucas Nussbaum > Sent: 21 December 2021 16:51 > To: sub...@bugs.debian.org > Subject: Bug#1002276: schroot: FTBFS: The following tests FAILED: 3 - sbuild- > chroot-config (Failed) > > Source: schroot > Version: 1.6.10-12 > Severity: serious > Justification: FTBFS > Tags: bookworm sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-20211220 ftbfs-bookworm > > Hi, > > During a rebuild of all packages in sid, your package failed to build on > amd64. > > > Relevant part (hopefully): > > make[2]: Entering directory '/<>/debian/build' > > Running tests... > > /usr/bin/ctest --force-new-ctest-process -V UpdateCTestConfiguration > > from :/<>/debian/build/DartConfiguration.tcl > > UpdateCTestConfiguration from > > :/<>/debian/build/DartConfiguration.tcl > > Test project /<>/debian/build Constructing a list of > > tests Done constructing a list of tests Updating test list for > > fixtures Added 0 tests to meet fixture requirements Checking test > > dependency graph... > > Checking test dependency graph end > > test 1 > > Start 1: setup-test-data > > > > 1: Test command: /<>/debian/build/test/setup-test-data > > 1: Test timeout computed to be: 1000 > > 1/8 Test #1: setup-test-data .. Passed0.01 sec > > test 2 > > Start 2: sbuild-chroot-chroot > > > > 2: Test command: > > /<>/debian/build/test/sbuild-chroot-chroot > > 2: Test timeout computed to be: 1000 > > 2: > . > ... > > 2: > > 2: > > 2: OK (148 tests) > > 2: > > 2: > > 2/8 Test #2: sbuild-chroot-chroot . Passed0.03 sec > > test 3 > > Start 3: sbuild-chroot-config > > > > 3: Test command: > > /<>/debian/build/test/sbuild-chroot-config > > 3: Test timeout computed to be: 1000 > > 3: .E.E.E.E.E.E.E.E.E.E.E.E.E.E.E.E > > 3: > > 3: > > 3: !!!FAILURES!!! > > 3: Test Results: > > 3: Run: 16 Failures: 0 Errors: 16 > > 3: > > 3: > > 3: 1) test: test_config::test_construction_file (E) > > 3: setUp() failed > > 3: - uncaught exception of type std::exception (or derived). > > 3: - /<>/debian/build/test/testdata/config.ex1: File is > > not owned by user root > > 3: > > 3: > > 3: 2) test: test_config::test_construction_dir (E) > > 3: setUp() failed > > 3: - uncaught exception of type std::exception (or derived). > > 3: - /<>/debian/build/test/testdata/config.ex1: File is > > not owned by user root > > 3: > > 3: > > 3: 3) test: test_config::test_construction_fail (E) > > 3: setUp() failed > > 3: - uncaught exception of type std::exception (or derived). > > 3: - /<>/debian/build/test/testdata/config.ex1: File is > > not owned by user root > > 3: > > 3: > > 3: 4) test: test_config::test_add_file (E) > > 3: setUp() failed > > 3: - uncaught exception of type std::exception (or derived). > > 3: - /<>/debian/build/test/testdata/config.ex1: File is > > not owned by user root > > 3: > > 3: > > 3: 5) test: test_config::test_add_dir (E) > > 3: setUp() failed > > 3: - uncaught exception of type std::exception (or derived). > > 3: - /<>/debian/build/test/testdata/config.ex1: File is > > not owned by user root > > 3: > > 3: > > 3: 6) test:
Bug#1002266: marked as pending in node-y18n
Control: tag -1 pending Hello, Bug #1002266 in node-y18n reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-y18n/-/commit/2068f8a4eedf1cb531cf7ee0c0e80cfaf4da29c2 Fix build dependencies for rollup ≥ 2.61 Closes: #1002266 (this message was generated automatically) -- Greetings https://bugs.debian.org/1002266
Bug#1002182: qutebrowser: FTBFS: AttributeError: 'NoneType' object has no attribute 'split'
Hi, Florian Bruhin wrote: > On Tue, Dec 21, 2021 at 05:15:47PM +0100, Lucas Nussbaum wrote: > > > I: dh_python3 pydist:313: Cannot find package that provides > > > dataclasses. Please add package that provides it to > > > Build-Depends or add "dataclasses python3-dataclasses" line to > > > debian/py3dist-overrides or add proper dependency to Depends by > > > hand and ignore this info. Can reproduce this issue. > That seems like a false-positive: The dataclasses backport is only > required for Python 3.6, but Debian sets "Depends: python3 (>= 3.7)" > already. […] > That smells like a bug in dh-python. I tried downgrading dh-python until it no more FTBFS. It doesn't FTBFS with dh-python 5.2024 and the first version it FTBFS is 5.20211213. The changelog entry of 5.20211213 contains these potential causes, at least from my point of view: * Handle dist-info extra sections the same way we do for requirements.txt. (closes: 998374) * Add new pep517 plugin that uses python3-build + python3-installer to build Python modules as wheels and then unpack the wheel. This is the new interface used by modern Python packaging tools. (Closes: #984824) Full entry (in cases something didn't look suspicious to me) at https://packages.qa.debian.org/d/dh-python/news/20211214T010008Z.html Florian: Any idea which of these might have broken this? And is the suggestion to add "dataclasses python3-dataclasses" line to debian/py3dist-overrides something we should simply do or is this an issue which we should make the dh-python maintainers aware of? I must admit, I still don't understand what this is dh-python argues about. Maybe someone has some more Python insight for a non-pythonista? Regards, Axel -- ,''`. | Axel Beckert , https://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
Processed: Bug#1002266 marked as pending in node-y18n
Processing control commands: > tag -1 pending Bug #1002266 [src:node-y18n] node-y18n: FTBFS: TypeError: Cannot read property 'text' of undefined Added tag(s) pending. -- 1002266: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002266 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1002228: marked as done (node-rollup-plugin-buble: FTBFS: dh_auto_test: error: cd ./legacy && sh -ex ../debian/nodejs/legacy/test returned exit code 1)
Your message dated Tue, 21 Dec 2021 18:05:41 +
with message-id
and subject line Bug#1002228: fixed in node-rollup-plugin-buble
0.21.3+repack+~0.19.8-2
has caused the Debian Bug report #1002228,
regarding node-rollup-plugin-buble: FTBFS: dh_auto_test: error: cd ./legacy &&
sh -ex ../debian/nodejs/legacy/test returned exit code 1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1002228: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002228
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-rollup-plugin-buble
Version: 0.21.3+repack+~0.19.8-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211220 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_build --buildsystem=nodejs
> Found debian/nodejs/legacy/build
> cd ./legacy && sh -ex ../debian/nodejs/legacy/build
> + rollup -c
> [36m
> [1msrc/index.js[22m → [1mdist/rollup-plugin-buble.es.js,
> dist/rollup-plugin-buble.cjs.js[22m...[39m
> [1m[33m(!) Entry module "src/index.js" is implicitly using "default" export
> mode, which means for CommonJS output that its default export is assigned to
> "module.exports". For many tools, such CommonJS output will not be
> interchangeable with the original ES module. If this is intended, explicitly
> set "output.exports" to either "auto" or "default", otherwise you might want
> to consider changing the signature of "src/index.js" to use named exports
> only.[39m[22m
> [90mhttps://rollupjs.org/guide/en/#outputexports[39m
> [1msrc/index.js[22m
> [32mcreated [1mdist/rollup-plugin-buble.es.js,
> dist/rollup-plugin-buble.cjs.js[22m in [1m16ms[22m[39m
> cd packages/buble && rollup -c
> [36m
> [1msrc/index.ts[22m → [1mdist/rollup-plugin-buble.es.js,
> dist/rollup-plugin-buble.cjs.js[22m...[39m
> [1m[33m(!) Entry module "src/index.ts" is implicitly using "default" export
> mode, which means for CommonJS output that its default export is assigned to
> "module.exports". For many tools, such CommonJS output will not be
> interchangeable with the original ES module. If this is intended, explicitly
> set "output.exports" to either "auto" or "default", otherwise you might want
> to consider changing the signature of "src/index.ts" to use named exports
> only.[39m[22m
> [90mhttps://rollupjs.org/guide/en/#outputexports[39m
> [1msrc/index.ts[22m
> [1m[33m(!) Plugin typescript: @rollup/plugin-typescript TS2307: Cannot find
> module 'buble' or its corresponding type declarations.[39m[22m
> [1msrc/index.ts: (1:27)[22m
> [90m
> [7m1[0m import { transform } from 'buble';
> [7m [0m [91m ~~~[0m
> [39m
> [1m[33m(!) Plugin typescript: @rollup/plugin-typescript TS2307: Cannot find
> module 'rollup' or its corresponding type declarations.[39m[22m
> [1msrc/index.ts: (2:24)[22m
> [90m
> [7m2[0m import { Plugin } from 'rollup';
> [7m [0m [91m [0m
> [39m
> [1m[33m(!) Plugin typescript: @rollup/plugin-typescript TS2307: Cannot find
> module '@rollup/pluginutils' or its corresponding type declarations.[39m[22m
> [1msrc/index.ts: (3:30)[22m
> [90m
> [7m3[0m import { createFilter } from '@rollup/pluginutils';
> [7m [0m [91m ~[0m
> [39m
> [1m[33m(!) Plugin typescript: @rollup/plugin-typescript TS2339: Property
> 'transforms' does not exist on type 'RollupBubleOptions'.[39m[22m
> [1msrc/index.ts: (9:67)[22m
> [90m
> [7m9[0m const transformOptions = { ...options, transforms: {
> ...options.transforms, modules: false } };
> [7m [0m [91m
>~~[0m
> [39m
> [1m[33m(!) Plugin typescript: @rollup/plugin-typescript TS7006: Parameter
> 'code' implicitly has an 'any' type.[39m[22m
> [1msrc/index.ts: (14:15)[22m
> [90m
> [7m14[0m transform(code, id) {
> [7m [0m [91m [0m
> [39m
> [1m[33m(!) Plugin typescript: @rollup/plugin-typescript TS7006: Parameter
> 'id' implicitly has an 'any' type.[39m[22m
> [1msrc/index.ts: (14:21)[22m
> [90m
> [7m14[0m transform(code, id) {
> [7m [0m [91m~~[0m
> [39m
> [1m[33m(!) Plugin typescript: @rollup/plugin-typescript TS2571: Object is
> of type 'unknown'.[39m[22m
> [1msrc/index.ts: (20:9)[22m
> [90m
> [7m20[0m e.plugin = 'buble';
> [7m
Bug#1002246: marked as done (containerd: FTBFS: src/github.com/containerd/containerd/vendor/k8s.io/client-go/util/workqueue/default_rate_limiters.go:24:2: cannot find package "golang.org/x/time/rate")
Your message dated Tue, 21 Dec 2021 18:03:39 + with message-id and subject line Bug#1002246: fixed in containerd 1.5.8~ds1-3 has caused the Debian Bug report #1002246, regarding containerd: FTBFS: src/github.com/containerd/containerd/vendor/k8s.io/client-go/util/workqueue/default_rate_limiters.go:24:2: cannot find package "golang.org/x/time/rate" 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.) -- 1002246: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002246 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: containerd Version: 1.5.8~ds1-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211220 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules binary > dh binary --buildsystem=golang --with=golang --builddirectory=_build >dh_update_autotools_config -O--buildsystem=golang -O--builddirectory=_build >dh_autoreconf -O--buildsystem=golang -O--builddirectory=_build >dh_auto_configure -O--buildsystem=golang -O--builddirectory=_build >debian/rules override_dh_auto_build > make[1]: Entering directory '/<>' > dh_auto_build -- -ldflags '-X > github.com/containerd/containerd/version.Version=1.5.8~ds1 -X > github.com/containerd/containerd/version.Revision=1.5.8~ds1-2' > cd _build && go install -trimpath -v -p 4 -ldflags "-X > github.com/containerd/containerd/version.Version=1.5.8~ds1 -X > github.com/containerd/containerd/version.Revision=1.5.8~ds1-2" > github.com/containerd/containerd github.com/containerd/containerd/api/events > github.com/containerd/containerd/api/services/containers/v1 > github.com/containerd/containerd/api/services/content/v1 > github.com/containerd/containerd/api/services/diff/v1 > github.com/containerd/containerd/api/services/events/v1 > github.com/containerd/containerd/api/services/images/v1 > github.com/containerd/containerd/api/services/introspection/v1 > github.com/containerd/containerd/api/services/leases/v1 > github.com/containerd/containerd/api/services/namespaces/v1 > github.com/containerd/containerd/api/services/snapshots/v1 > github.com/containerd/containerd/api/services/tasks/v1 > github.com/containerd/containerd/api/services/ttrpc/events/v1 > github.com/containerd/containerd/api/services/version/v1 > github.com/containerd/containerd/api/types > github.com/containerd/containerd/api/types/task > github.com/containerd/containerd/archive > github.com/containerd/containerd/archive/compression > github.com/containerd/containerd/archive/tartest > github.com/containerd/containerd/cio > github.com/containerd/containerd/cmd/containerd > github.com/containerd/containerd/cmd/containerd/command > github.com/containerd/containerd/cmd/containerd-shim > github.com/containerd/containerd/cmd/containerd-shim-runc-v1 > github.com/containerd/containerd/cmd/containerd-shim-runc-v2 > github.com/containerd/containerd/cmd/ctr > github.com/containerd/containerd/cmd/ctr/app > github.com/containerd/containerd/cmd/ctr/commands > github.com/containerd/containerd/cmd/ctr/commands/containers > github.com/containerd/containerd/cmd/ctr/commands/content > github.com/containerd/containerd/cmd/ctr/commands/events > github.com/containerd/containerd/cmd/ctr/commands/images > github.com/containerd/containerd/cmd/ctr/commands/install > github.com/containerd/containerd/cmd/ctr/commands/leases > github.com/containerd/containerd/cmd/ctr/commands/namespaces > github.com/containerd/containerd/cmd/ctr/commands/oci > github.com/containerd/containerd/cmd/ctr/commands/plugins > github.com/containerd/containerd/cmd/ctr/commands/pprof > github.com/containerd/containerd/cmd/ctr/commands/run > github.com/containerd/containerd/cmd/ctr/commands/shim > github.com/containerd/containerd/cmd/ctr/commands/snapshots > github.com/containerd/containerd/cmd/ctr/commands/tasks > github.com/containerd/containerd/cmd/ctr/commands/version > github.com/containerd/containerd/cmd/gen-manpages > github.com/containerd/containerd/containers > github.com/containerd/containerd/content > github.com/containerd/containerd/content/local > github.com/containerd/containerd/content/proxy > github.com/containerd/containerd/content/testsuite > github.com/containerd/containerd/contrib/apparmor > github.com/containerd/containerd/contrib/nvidia > github.com/containerd/containerd/contrib/seccomp > github.com/containerd/containerd/contrib/snapshotservice > github.com/containerd/containerd/defaults >
Bug#965586: marked as done (hugs98: Removal of obsolete debhelper compat 5 and 6 in bookworm)
Your message dated Tue, 21 Dec 2021 17:50:30 + with message-id and subject line (No Subject) has caused the Debian Bug report #965586, regarding hugs98: Removal of obsolete debhelper compat 5 and 6 in bookworm 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.) -- 965586: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965586 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: hugs98 Version: 98.200609.21-5.4 Severity: normal Usertags: compat-5-6-removal Hi, The package hugs98 uses debhelper with a compat level of 5 or 6, which is deprecated and scheduled for removal[1]. Please bump the debhelper compat at your earliest convenience /outside the freeze/! * Compat 13 is recommended (supported in stable-backports) * Compat 7 is the bare minimum PLEASE KEEP IN MIND THAT the release team *DOES NOT* accept uploads with compat bumps during the freeze. If there is any risk that the fix for this bug might not migrate to testing before 2021-01-01[3] then please postpone the fix until after the freeze. At the time of filing this bug, compat 5 and 6 are expected to be removed "some time during the development cycle of bookworm". Thanks, ~Niels [1] https://lists.debian.org/debian-devel/2020/07/msg00065.html [2] https://release.debian.org/bullseye/FAQ.html [3] The choice of 2021-01-01 as a "deadline" is set before the actual freeze deadline to provide a safe cut off point for most people. Mind you, it is still your responsibility to ensure that the upload makes it into testing even if you upload before that date. --- End Message --- --- Begin Message --- Hi! This bug was fixed in upload 98.200609.21-6. For that reason I am closing the bug. -- Hugo Torres de Lima 0x365C8CEF4233E3D8 Sent with ProtonMail Secure Email. signature.asc Description: OpenPGP digital signature --- End Message ---
Processed: fixed 1002156 in 1:1.9.2+ds-0.1
Processing commands for cont...@bugs.debian.org:
> fixed 1002156 1:1.9.2+ds-0.1
Bug #1002156 {Done: Shengjing Zhu } [src:spdlog] purify:
FTBFS: libfmt-dev : Breaks: libspdlog-dev (< 1:1.9.2+ds-0.1) but 1:1.8.5+ds-3
is to be installed
Bug #1002124 {Done: Shengjing Zhu } [src:spdlog] sopt: FTBFS:
libfmt-dev : Breaks: libspdlog-dev (< 1:1.9.2+ds-0.1) but 1:1.8.5+ds-3 is to be
installed
Marked as fixed in versions spdlog/1:1.9.2+ds-0.1.
Marked as fixed in versions spdlog/1:1.9.2+ds-0.1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1002124: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002124
1002156: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002156
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1002228: marked as pending in node-rollup-plugin-buble
Control: tag -1 pending Hello, Bug #1002228 in node-rollup-plugin-buble reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-rollup-plugin-buble/-/commit/6c188da82c6d63f6b998014785522ba6ac1f1bb9 Workaround tsc paths bug Closes: #1002228 (this message was generated automatically) -- Greetings https://bugs.debian.org/1002228
Processed: Bug#1002228 marked as pending in node-rollup-plugin-buble
Processing control commands: > tag -1 pending Bug #1002228 [src:node-rollup-plugin-buble] node-rollup-plugin-buble: FTBFS: dh_auto_test: error: cd ./legacy && sh -ex ../debian/nodejs/legacy/test returned exit code 1 Ignoring request to alter tags of bug #1002228 to the same tags previously set -- 1002228: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002228 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1002228: marked as pending in node-rollup-plugin-buble
Control: tag -1 pending Hello, Bug #1002228 in node-rollup-plugin-buble reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-rollup-plugin-buble/-/commit/d5dc0116f362cbd696ad201c9b85a4b9fe8d42f1 Fix test for rollup ≥ 2.61 Closes: #1002228 (this message was generated automatically) -- Greetings https://bugs.debian.org/1002228
Processed: Bug#1002228 marked as pending in node-rollup-plugin-buble
Processing control commands: > tag -1 pending Bug #1002228 [src:node-rollup-plugin-buble] node-rollup-plugin-buble: FTBFS: dh_auto_test: error: cd ./legacy && sh -ex ../debian/nodejs/legacy/test returned exit code 1 Added tag(s) pending. -- 1002228: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002228 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1002170: closing 1002170
close 1002170 1:1.9.2+ds-0.1 thanks
Bug#998917: marked as done (swish++: missing required debian/rules targets build-arch and/or build-indep)
Your message dated Tue, 21 Dec 2021 17:49:38 +
with message-id
and subject line Bug#998917: fixed in swish++ 6.1.5-6
has caused the Debian Bug report #998917,
regarding swish++: missing required debian/rules targets build-arch and/or
build-indep
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.)
--
998917: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998917
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: swish++
Version: 6.1.5-5
Severity: important
Justification: Debian Policy section 4.9
Tags: bookworm sid
User: debian...@lists.debian.org
Usertags: missing-build-arch-indep
Dear maintainer,
Your package does not include build-arch and/or build-indep targets in
debian/rules. This is required by Debian Policy section 4.9, since 2012.
https://www.debian.org/doc/debian-policy/ch-source.html#main-building-script-debian-rules
Please note that this is also a sign that the packaging of this software
could benefit from a refresh. For example, packages using 'dh' cannot be
affected by this issue.
This mass bug filing was discussed on debian-devel@ in
https://lists.debian.org/debian-devel/2021/11/msg00052.html .
The severity of this bug will be changed to 'serious' after a month.
Best,
Lucas
--- End Message ---
--- Begin Message ---
Source: swish++
Source-Version: 6.1.5-6
Done: Håvard Flaget Aasen
We believe that the bug you reported is fixed in the latest version of
swish++, 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 998...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Håvard Flaget Aasen (supplier of updated swish++
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, 20 Dec 2021 18:22:13 +0100
Source: swish++
Architecture: source
Version: 6.1.5-6
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group
Changed-By: Håvard Flaget Aasen
Closes: 838727 908047 998917
Changes:
swish++ (6.1.5-6) unstable; urgency=medium
.
[ Tobias Frost ]
* QA upload.
* Moved repository to salsa.debian.org.
.
[ Ondřej Nový ]
* d/changelog: Remove trailing whitespaces
* d/rules: Remove trailing whitespaces
* d/watch: Use https protocol
.
[ Debian Janitor ]
* Trim trailing whitespace.
* Add missing ${misc:Depends} to Depends for swish++.
* debian/rules: Use dh_prep rather than "dh_clean -k".
* Set debhelper-compat version in Build-Depends.
* Remove patches fix_splitmail_manpage that are missing from
debian/patches/series.
.
[ Håvard Flaget Aasen ]
* Refresh all patches using quilt.
* Change to dh sequencer. Closes: #838727
- This includes target build-arch and build-indep. Closes: #998917
- Build also respects DEB_BUILD_OPTIONS nostrip and noopt. Closes: #908047
* d/watch: Bump to version 4.
* Change capitalization on Vcs* fields.
* Bump debhelper to 13.
* Drop quilt as build dependency.
* Convert d/email_indexing/nnir.el to utf-8
* Document Root-Requires-Root.
* Update Standards-Version to 4.6.0.
Checksums-Sha1:
f3a033e8aef73f60e663ae36b2c5efa325682b27 1846 swish++_6.1.5-6.dsc
8c37774c219b2b581bbbfbd73d55ca0665e14730 41860 swish++_6.1.5-6.debian.tar.xz
27041676138a2a19d9a1f1fd24b70f537e946807 5467 swish++_6.1.5-6_source.buildinfo
Checksums-Sha256:
7dd720c939c1647f04a51e52c25587e4eacecccd07d74b711fc64113510b3f8b 1846
swish++_6.1.5-6.dsc
4bfeed911d8a432f97849ea170d3106fabcb8503cbddb60d2ea13611e7b6a211 41860
swish++_6.1.5-6.debian.tar.xz
f56433d0a0858ff2c4c480a1b70888c97cc8c9c83fc990f29fb6f83c04a9d937 5467
swish++_6.1.5-6_source.buildinfo
Files:
3e52191b707ae8928adb8f4566ca1e99 1846 web optional swish++_6.1.5-6.dsc
ec7e4881ab4549d0681f259d43452d28 41860 web optional
swish++_6.1.5-6.debian.tar.xz
5ade86c14a12abd0743bba097ddc90d7 5467 web optional
swish++_6.1.5-6_source.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEkjZVexcMh/iCHArDweDZLphvfH4FAmHCEHkACgkQweDZLphv
fH7RdRAAwiw4NigrsjZLpYtVcQcG5cVGETl2JvC6D1VdqmH4duqAlxeYdMa49K2z
AfcHEx2tnaYmeQTzcahxdfErTQx3K/0sH2AGjcFd6mF/ULVjrjOpVmLA276b3gvn
T1tic8AGWL8jESw5y6dFO6q6HC7mfclfp562zbPkxD+i5I7IlpLk57KsXLjmXMyd
Bug#1002220: marked as done (node-rollup-plugin-alias: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1)
Your message dated Tue, 21 Dec 2021 17:49:15 +
with message-id
and subject line Bug#1002220: fixed in node-rollup-plugin-alias 3.1.8~ds-2
has caused the Debian Bug report #1002220,
regarding node-rollup-plugin-alias: FTBFS: dh_auto_test: error: /bin/sh -ex
debian/tests/pkg-js/test returned exit code 1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1002220: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002220
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-rollup-plugin-alias
Version: 3.1.8~ds-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211220 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> # Build @rollup/plugin-alias
> cd packages/alias && rollup -c
> [36m
> [1msrc/index.ts[22m → [1mdist/index.js, dist/index.es.js[22m...[39m
> [1m[33m(!) Plugin typescript: @rollup/plugin-typescript TS2307: Cannot find
> module 'rollup' or its corresponding type declarations.[39m[22m
> [1msrc/index.ts: (1:43)[22m
> [90m
> [7m1[0m import { PartialResolvedId, Plugin } from 'rollup';
> [7m [0m [91m [0m
> [39m
> [1m[33m(!) Plugin typescript: @rollup/plugin-typescript TS2550: Property
> 'entries' does not exist on type 'ObjectConstructor'. Do you need to change
> your target library? Try changing the 'lib' compiler option to 'es2017' or
> later.[39m[22m
> [1msrc/index.ts: (37:17)[22m
> [90m
> [7m37[0m return Object.entries(entries).map(([key, value]) => {
> [7m [0m [91m~~~[0m
> [39m
> [1m[33m(!) Plugin typescript: @rollup/plugin-typescript TS7031: Binding
> element 'key' implicitly has an 'any' type.[39m[22m
> [1msrc/index.ts: (37:40)[22m
> [90m
> [7m37[0m return Object.entries(entries).map(([key, value]) => {
> [7m [0m [91m ~~~[0m
> [39m
> [1m[33m(!) Plugin typescript: @rollup/plugin-typescript TS7031: Binding
> element 'value' implicitly has an 'any' type.[39m[22m
> [1msrc/index.ts: (37:45)[22m
> [90m
> [7m37[0m return Object.entries(entries).map(([key, value]) => {
> [7m [0m [91m~[0m
> [39m
> [1m[33m(!) Plugin typescript: @rollup/plugin-typescript TS7006: Parameter
> 'inputOptions' implicitly has an 'any' type.[39m[22m
> [1msrc/index.ts: (73:16)[22m
> [90m
> [7m73[0m buildStart(inputOptions) {
> [7m [0m [91m [0m
> [39m
> [1m[33m(!) Plugin typescript: @rollup/plugin-typescript TS7006: Parameter
> 'importee' implicitly has an 'any' type.[39m[22m
> [1msrc/index.ts: (86:15)[22m
> [90m
> [7m86[0m resolveId(importee, importer, resolveOptions) {
> [7m [0m [91m [0m
> [39m
> [1m[33m(!) Plugin typescript: @rollup/plugin-typescript TS7006: Parameter
> 'importer' implicitly has an 'any' type.[39m[22m
> [1msrc/index.ts: (86:25)[22m
> [90m
> [7m86[0m resolveId(importee, importer, resolveOptions) {
> [7m [0m [91m[0m
> [39m
> [1m[33m(!) Plugin typescript: @rollup/plugin-typescript TS7006: Parameter
> 'resolveOptions' implicitly has an 'any' type.[39m[22m
> [1msrc/index.ts: (86:35)[22m
> [90m
> [7m86[0m resolveId(importee, importer, resolveOptions) {
> [7m [0m [91m ~~[0m
> [39m
> [1m[33m(!) Plugin typescript: @rollup/plugin-typescript TS7006: Parameter
> 'resolved' implicitly has an 'any' type.[39m[22m
> [1msrc/index.ts: (109:15)[22m
> [90m
> [7m109[0m ).then((resolved) => {
> [7m [0m [91m [0m
> [39m
> [32mcreated [1mdist/index.js, dist/index.es.js[22m in [1m420ms[22m[39m
> make[1]: Leaving directory '/<>'
>dh_auto_test --buildsystem=nodejs
> mkdir -p node_modules/\@rollup
> ln -s ../../packages/alias node_modules/\@rollup/plugin-alias
> /bin/sh -ex debian/tests/pkg-js/test
> + cd packages/alias
> + mkdir -p node_modules/@rollup
> + ln -s ../.. node_modules/@rollup/plugin-alias
> + tape test/test.js
> TAP version 13
> # type
> ok 1 should be strictly equal
> # instance
> ok 2 should be strictly equal
> ok 3 should be strictly equal
> # defaults
> ok 4 should be strictly equal
> ok 5 should be strictly equal
> # Simple aliasing (array)
> ok 6 should be deeply equivalent
> # Simple aliasing (object)
> ok 7 should be
Processed: tagging 1002182
Processing commands for cont...@bugs.debian.org: > # Can reproduce the FTBFS but see Florian's mail > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002182#10 > tags 1002182 + moreinfo confirmed Bug #1002182 [src:qutebrowser] qutebrowser: FTBFS: AttributeError: 'NoneType' object has no attribute 'split' Added tag(s) confirmed and moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 1002182: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002182 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: closing 1002170
Processing commands for cont...@bugs.debian.org: > close 1002170 1:1.9.2+ds-0.1 Bug #1002170 [src:spdlog] spdlog: fails to install due to Breaks in fmtlib Marked as fixed in versions spdlog/1:1.9.2+ds-0.1. Bug #1002170 [src:spdlog] spdlog: fails to install due to Breaks in fmtlib Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1002170: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002170 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1002220 marked as pending in node-rollup-plugin-alias
Processing control commands: > tag -1 pending Bug #1002220 [src:node-rollup-plugin-alias] node-rollup-plugin-alias: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1 Added tag(s) pending. -- 1002220: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002220 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1002220: marked as pending in node-rollup-plugin-alias
Control: tag -1 pending Hello, Bug #1002220 in node-rollup-plugin-alias reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-rollup-plugin-alias/-/commit/470aa6d7f0cdc5ba5e67f89d085af076cc9cb762 Workaround typescript paths bug Closes: #1002220 (this message was generated automatically) -- Greetings https://bugs.debian.org/1002220
Processed: Bug#1002220 marked as pending in node-rollup-plugin-alias
Processing control commands: > tag -1 pending Bug #1002220 [src:node-rollup-plugin-alias] node-rollup-plugin-alias: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1 Ignoring request to alter tags of bug #1002220 to the same tags previously set -- 1002220: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002220 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1002220: marked as pending in node-rollup-plugin-alias
Control: tag -1 pending Hello, Bug #1002220 in node-rollup-plugin-alias reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-rollup-plugin-alias/-/commit/8c8145b9887163bcd6d9b587f50d4ae7cdd1ca41 Fix test Closes: #1002220 (this message was generated automatically) -- Greetings https://bugs.debian.org/1002220
Bug#1002256: marked as done (node-gulp-sourcemaps: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1)
Your message dated Tue, 21 Dec 2021 17:34:12 + with message-id and subject line Bug#1002256: fixed in node-gulp-sourcemaps 3.0.0+~cs4.0.1-2 has caused the Debian Bug report #1002256, regarding node-gulp-sourcemaps: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1002256: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002256 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-gulp-sourcemaps Version: 3.0.0+~cs4.0.1-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211220 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules binary > dh binary >dh_update_autotools_config >dh_autoreconf >dh_auto_configure --buildsystem=nodejs > Link node_modules/@gulp-sourcemaps/identity-map -> > ../../gulp-sourcemapsidentity-map > Link node_modules/@gulp-sourcemaps/map-sources -> > ../../gulp-sourcemapsmap-sources > Link node_modules/strip-bom-string -> ../strip-bom-string >dh_auto_build --buildsystem=nodejs > No build command found, searching known files > No build command found, searching known files > No build command found, searching known files > No build command found, searching known files >dh_auto_test --buildsystem=nodejs > ln -s ../debian/tests/test_modules/expect node_modules/expect > ln -s ../debian/tests/test_modules/function.prototype.name > node_modules/function.prototype.name > ln -s ../debian/tests/test_modules/functions-have-names > node_modules/functions-have-names > ln -s ../debian/tests/test_modules/is-arrow-function > node_modules/is-arrow-function > ln -s ../debian/tests/test_modules/is-async-fn node_modules/is-async-fn > ln -s ../debian/tests/test_modules/is-equal node_modules/is-equal > ln -s ../debian/tests/test_modules/is-finalizationregistry > node_modules/is-finalizationregistry > ln -s ../debian/tests/test_modules/is-weakref node_modules/is-weakref > ln -s ../debian/tests/test_modules/object.getprototypeof > node_modules/object.getprototypeof > ln -s ../debian/tests/test_modules/reflect.getprototypeof > node_modules/reflect.getprototypeof > ln -s ../debian/tests/test_modules/which-builtin-type > node_modules/which-builtin-type > ln -s ../. node_modules/gulp-sourcemaps > /bin/sh -ex debian/tests/pkg-js/test > + ls test/init.test.js test/integration.test.js test/publish.test.js > test/test-helpers.js test/utils.test.js test/write.test.js > + grep -v+ test/integration.test.js > grep -v test/publish.test.js > + mocha --async-only test/init.test.js test/test-helpers.js > test/utils.test.js test/write.test.js > > Error: Cannot find module 'object-inspect' > Require stack: > - /<>/debian/tests/test_modules/expect/lib/assert.js > - /<>/debian/tests/test_modules/expect/lib/Expectation.js > - /<>/debian/tests/test_modules/expect/lib/index.js > - /<>/test/init.test.js > at Function.Module._resolveFilename > (internal/modules/cjs/loader.js:815:15) > at Function.Module._load (internal/modules/cjs/loader.js:667:27) > at Module.require (internal/modules/cjs/loader.js:887:19) > at require (internal/modules/cjs/helpers.js:74:18) > at Object. > (/<>/debian/tests/test_modules/expect/lib/assert.js:7:22) > at Module._compile (internal/modules/cjs/loader.js:999:30) > at Object.Module._extensions..js (internal/modules/cjs/loader.js:1027:10) > at Module.load (internal/modules/cjs/loader.js:863:32) > at Function.Module._load (internal/modules/cjs/loader.js:708:14) > at Module.require (internal/modules/cjs/loader.js:887:19) > at require (internal/modules/cjs/helpers.js:74:18) > at Object. > (/<>/debian/tests/test_modules/expect/lib/Expectation.js:19:15) > at Module._compile (internal/modules/cjs/loader.js:999:30) > at Object.Module._extensions..js (internal/modules/cjs/loader.js:1027:10) > at Module.load (internal/modules/cjs/loader.js:863:32) > at Function.Module._load (internal/modules/cjs/loader.js:708:14) > at Module.require (internal/modules/cjs/loader.js:887:19) > at require (internal/modules/cjs/helpers.js:74:18) > at Object. > (/<>/debian/tests/test_modules/expect/lib/index.js:3:20) > at Module._compile (internal/modules/cjs/loader.js:999:30) > at Object.Module._extensions..js (internal/modules/cjs/loader.js:1027:10) > at Module.load
Bug#1002280: marked as done (node-neo-async: FTBFS: Error: Cannot find module 'minimist')
Your message dated Tue, 21 Dec 2021 17:34:04 +
with message-id
and subject line Bug#1002280: fixed in node-gulp 4.0.2+~cs54.26.36-3
has caused the Debian Bug report #1002280,
regarding node-neo-async: FTBFS: Error: Cannot find module 'minimist'
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.)
--
1002280: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002280
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-neo-async
Version: 2.6.2+~cs3.0.0-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211220 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules binary
> dh binary
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure --buildsystem=nodejs
> Link node_modules/asyncro -> ../asyncro
>dh_auto_build --buildsystem=nodejs
> Found debian/nodejs/asyncro/build
> cd ./asyncro && sh -ex ../debian/nodejs/asyncro/build
> + rollup -i ./src/index.js -f cjs -o ./dist/asyncro.js
> [36m
> [1m./src/index.js[22m → [1m./dist/asyncro.js[22m...[39m
> [32mcreated [1m./dist/asyncro.js[22m in [1m42ms[22m[39m
> Found debian/nodejs/./build
> cd ./. && sh -ex debian/nodejs/./build
> + gulp --gulpfile gulp/tasks/npm.js npm:publish
> [19:05:21] Local gulp not found in /<>/gulp/tasks
> [19:05:21] Try running: npm install gulp
> [19:05:21] Using globally installed gulp
> [19:05:21] Working directory changed to /<>/gulp/tasks
> Error: Cannot find module 'minimist'
> Require stack:
> - /<>/gulp/tasks/npm.js
> - /usr/share/nodejs/gulp-cli/lib/shared/require-or-import.js
> - /usr/share/nodejs/gulp-cli/lib/versioned/^4.0.0/index.js
> - /usr/share/nodejs/gulp-cli/index.js
> - /usr/share/nodejs/gulp/bin/gulp.js
> at Function.Module._resolveFilename
> (internal/modules/cjs/loader.js:815:15)
> at Function.Module._load (internal/modules/cjs/loader.js:667:27)
> at Module.require (internal/modules/cjs/loader.js:887:19)
> at require (internal/modules/cjs/helpers.js:74:18)
> at Object. (/<>/gulp/tasks/npm.js:8:14)
> at Module._compile (internal/modules/cjs/loader.js:999:30)
> at Object.Module._extensions..js (internal/modules/cjs/loader.js:1027:10)
> at Module.load (internal/modules/cjs/loader.js:863:32)
> at Function.Module._load (internal/modules/cjs/loader.js:708:14)
> at Module.require (internal/modules/cjs/loader.js:887:19) {
> code: 'MODULE_NOT_FOUND',
> requireStack: [
> '/<>/gulp/tasks/npm.js',
> '/usr/share/nodejs/gulp-cli/lib/shared/require-or-import.js',
> '/usr/share/nodejs/gulp-cli/lib/versioned/^4.0.0/index.js',
> '/usr/share/nodejs/gulp-cli/index.js',
> '/usr/share/nodejs/gulp/bin/gulp.js'
> ]
> }
> dh_auto_build: error: cd ./. && sh -ex debian/nodejs/./build returned exit
> code 1
> make: *** [debian/rules:8: binary] Error 25
The full build log is available from:
http://qa-logs.debian.net/2021/12/20/node-neo-async_2.6.2+~cs3.0.0-2_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: node-gulp
Source-Version: 4.0.2+~cs54.26.36-3
Done: Yadd
We believe that the bug you reported is fixed in the latest version of
node-gulp, 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 1002...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Yadd (supplier of updated node-gulp 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, 21 Dec 2021 18:12:09 +0100
Source: node-gulp
Architecture: source
Version: 4.0.2+~cs54.26.36-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers
Bug#999311: marked as done (convlit: missing required debian/rules targets build-arch and/or build-indep)
Your message dated Tue, 21 Dec 2021 17:33:36 + with message-id and subject line Bug#999311: fixed in convlit 1.8-3 has caused the Debian Bug report #999311, regarding convlit: missing required debian/rules targets build-arch and/or build-indep 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.) -- 999311: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999311 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: convlit Version: 1.8-2 Severity: important Justification: Debian Policy section 4.9 Tags: bookworm sid User: debian...@lists.debian.org Usertags: missing-build-arch-indep Dear maintainer, Your package does not include build-arch and/or build-indep targets in debian/rules. This is required by Debian Policy section 4.9, since 2012. https://www.debian.org/doc/debian-policy/ch-source.html#main-building-script-debian-rules Please note that this is also a sign that the packaging of this software could benefit from a refresh. For example, packages using 'dh' cannot be affected by this issue. This mass bug filing was discussed on debian-devel@ in https://lists.debian.org/debian-devel/2021/11/msg00052.html . The severity of this bug will be changed to 'serious' after a month. Best, Lucas --- End Message --- --- Begin Message --- Source: convlit Source-Version: 1.8-3 Done: Hugo Torres de Lima We believe that the bug you reported is fixed in the latest version of convlit, 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 999...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Hugo Torres de Lima (supplier of updated convlit 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, 20 Dec 2021 00:25:29 -0300 Source: convlit Architecture: source Version: 1.8-3 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Hugo Torres de Lima Closes: 999311 Changes: convlit (1.8-3) unstable; urgency=medium . * QA upload. * debian/control: - Added 'Rules-Requires-Root: no' to source stanza. - Bumped Standards-Version to 4.6.0. - Debhelper-compat bumped to 13. - Organized Depends. * debian/copyright: - Added Upstream-Contact. - Added public-domain license text. * debian/patches/01_old_changes.patch: Added "Forwarded: Not-needed" in header. * debian/patches/02_hardening.patch: Created. * debian/rules: - Added "dh sequencer" (Closes: #999311). - Removed some comments. * debian/upstream/metadata: Created. * debian/watch: - Bumped to version 4. - Removed comments. Checksums-Sha1: 261b114620b08b88c1ee28bf57021cafc819fc8a 1717 convlit_1.8-3.dsc 4bc1f032fccbcebc4c01d4bc9a99835f4569bc38 6008 convlit_1.8-3.debian.tar.xz eb2ad369a4e23e3de76aad76c06760cb84f29861 5479 convlit_1.8-3_source.buildinfo Checksums-Sha256: 96ccb703bd988fdbf9d1a16d3041f97a4641bdc48a3f59e0286a335ee39d8ccd 1717 convlit_1.8-3.dsc f027b9d1b605b144aa40afb74a202f1dec9fc90123cdf57019c6e7f7bfb30173 6008 convlit_1.8-3.debian.tar.xz 75abdf27fe6beba480c8c9bad491350c91caa3b83f191c9ec8ab81c3540b8b8f 5479 convlit_1.8-3_source.buildinfo Files: 5d449a9bd34985f533d74cb3d57959eb 1717 utils optional convlit_1.8-3.dsc 68830af8ce4fa4c3d42ee0086ea71fa7 6008 utils optional convlit_1.8-3.debian.tar.xz 003e980aba12d487f5ad48739ab7747d 5479 utils optional convlit_1.8-3_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEkjZVexcMh/iCHArDweDZLphvfH4FAmHCDLgACgkQweDZLphv fH7fPRAA16jNiX+nUq8n/RNYPuvpEWNxYA3dRwzJbs0KNavvvew5d4ENb7ef/Vss SYInfLWDv9Xd9Z1cxmRW/OaQDrOzJynaRJ2DLFnQSbpW3HEyoZq1OOjrJIPrjG3w RC1fTMsMwSG43n8suG932J3jmslmJm7aEg9T/lvs6cJOdS5UXYsvqHqJq+79YrjC dkpjTcDf5yBPfck9x+SpToT5K/H/aa0snsVz3b2cWYD/5bu7ThR22gpjHy22uDuq j8ScG/LjYlwA3glhIuktu5XAo9YS7VQn7n7c2CXqC1kXO88ekbH439ZfoFJ6BYy+ FygHGh37FP3vXdSv6hW6Tve5/YoJUMXOfmXZP1ug0FrIgpVHyJix08jH4eEmIXZw PS/l3Une/2jRxHPyUqcgK+1cQGECNhC0Lkmqlq/CnH4j7eiT1ZYV8m5bfsecy2EF 6DhsE3mRCamPLSlaSY1qL2Eg4/smdg8vij9lsKegMm45FetodPQIRv3zrW2nmE/1 edAZzXdBfMh2UV6bwmBKl6Dis/ilv1ebL+sZUY6VutUWcm8jZrL7aPGOX0Tz5ELn
Processed: Bug#1002246 marked as pending in containerd
Processing control commands: > tag -1 pending Bug #1002246 [src:containerd] containerd: FTBFS: src/github.com/containerd/containerd/vendor/k8s.io/client-go/util/workqueue/default_rate_limiters.go:24:2: cannot find package "golang.org/x/time/rate" Added tag(s) pending. -- 1002246: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002246 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1002246: marked as pending in containerd
Control: tag -1 pending Hello, Bug #1002246 in containerd 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/containerd/-/commit/786dc3a664988b3fad4fef8dbc6eaf63e330bbff Add golang-golang-x-time-dev to Build-Depends Closes: #1002246 (this message was generated automatically) -- Greetings https://bugs.debian.org/1002246
Bug#1002182: qutebrowser: FTBFS: AttributeError: 'NoneType' object has no attribute 'split'
Hi,
On Tue, Dec 21, 2021 at 05:15:47PM +0100, Lucas Nussbaum wrote:
> > I: dh_python3 pydist:313: Cannot find package that provides dataclasses.
> > Please add package that provides it to Build-Depends or add "dataclasses
> > python3-dataclasses" line to debian/py3dist-overrides or add proper
> > dependency to Depends by hand and ignore this info.
That seems like a false-positive: The dataclasses backport is only
required for Python 3.6, but Debian sets "Depends: python3 (>= 3.7)"
already.
> > Traceback (most recent call last):
> > File "/usr/bin/dh_python3", line 280, in
> > main()
> > File "/usr/bin/dh_python3", line 201, in main
> > dependencies.parse(stats, options)
> > File "/usr/share/dh-python/dhpython/depends.py", line 242, in parse
> > deps = parse_pydep(self.impl, fn, bdep=self.bdep, **section_options)
> > File "/usr/share/dh-python/dhpython/pydist.py", line 522, in parse_pydep
> > for part in dependency.split(','))
> > AttributeError: 'NoneType' object has no attribute 'split'
That smells like a bug in dh-python.
Florian (upstream maintainer)
--
m...@the-compiler.org | https://www.qutebrowser.org
https://bruhin.software/ | https://github.com/sponsors/The-Compiler/
GPG: 916E B0C8 FD55 A072 | https://the-compiler.org/pubkey.asc
I love long mails! | https://email.is-not-s.ms/
signature.asc
Description: PGP signature
Bug#1002280: marked as pending in node-gulp
Control: tag -1 pending Hello, Bug #1002280 in node-gulp reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-gulp/-/commit/cf431faf30436194e9d0abf2f2c3d0da127e083c Add dependency to node-minimist Closes: #1002280 (this message was generated automatically) -- Greetings https://bugs.debian.org/1002280
Processed: Bug#1002256 marked as pending in node-gulp-sourcemaps
Processing control commands: > tag -1 pending Bug #1002256 [src:node-gulp-sourcemaps] node-gulp-sourcemaps: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1 Added tag(s) pending. -- 1002256: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002256 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1002280 marked as pending in node-gulp
Processing control commands: > tag -1 pending Bug #1002280 [gulp] node-neo-async: FTBFS: Error: Cannot find module 'minimist' Added tag(s) pending. -- 1002280: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002280 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
