Bug#1006818: marked as done (intermediary files embed arch-specific path)
Your message dated Fri, 30 Sep 2022 06:35:00 + with message-id and subject line Bug#1006818: fixed in eye 22.0203.1955~ds-2 has caused the Debian Bug report #1006818, regarding intermediary files embed arch-specific path 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.) -- 1006818: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006818 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: eye Version: 19.0221.2026~ds-1 Severity: serious User: debian...@lists.debian.org Usertags: fails-always Dear maintainer(s), You package has an autopkgtest, great. However, it fails on all architectures but amd64. Can you please investigate the situation and fix it? I copied some of the output at the bottom of this report. It seems that eye is expecting the run on amd64 exclusively. If that can't be reasonably be fixed, then please mark your test for amd64 exclusively (with the relatively new "Architecture" field in d/t/control). More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://ci.debian.net/packages/e/eye/ https://ci.debian.net/data/autopkgtest/testing/arm64/e/eye/19245228/log.gz autopkgtest [11:10:11]: test command1: prove debian/tests/*.t autopkgtest [11:10:11]: test command1: [--- # Failed test 'Check return from 'eye.pvm' is 0' # at debian/tests/eye.pvm.t line 9. # got: '127' # expected: '0' # Failed test 'bare command, stderr' # at debian/tests/eye.pvm.t line 11. # '/usr/bin/eye.pvm: 3: exec: /usr/lib/swi-prolog/bin/x86_64-linux/swipl: not found # ' # doesn't match '(?^:Usage: eye.pvm)' # Failed test 'Check return from 'eye.pvm --help' is 0' # at debian/tests/eye.pvm.t line 13. # got: '127' # expected: '0' # Failed test 'help, stderr' # at debian/tests/eye.pvm.t line 15. # '/usr/bin/eye.pvm: 3: exec: /usr/lib/swi-prolog/bin/x86_64-linux/swipl: not found # ' # doesn't match '(?^:Usage: eye.pvm)' # Failed test 'Check return from 'eye.pvm --n3 reasoning/socrates/socrates.n3 --query reasoning/socrates/socrates-query.n3' is 0' # at debian/tests/eye.pvm.t line 17. # got: '127' # expected: '0' # Failed test 'help, stderr' # at debian/tests/eye.pvm.t line 18. # '' # doesn't match '(?^:r:because)' # Failed test 'help, stderr' # at debian/tests/eye.pvm.t line 19. # '/usr/bin/eye.pvm: 3: exec: /usr/lib/swi-prolog/bin/x86_64-linux/swipl: not found # ' # doesn't match '(?^s:starting .*\nGET .*\nnetworking .*\nreasoning)' # Looks like you failed 7 tests of 15. debian/tests/eye.pvm.t .. Dubious, test returned 7 (wstat 1792, 0x700) Failed 7/15 subtests Test Summary Report --- debian/tests/eye.pvm.t (Wstat: 1792 Tests: 15 Failed: 7) Failed tests: 3, 5, 8, 10, 13-15 Non-zero exit status: 7 Files=1, Tests=15, 0 wallclock secs ( 0.02 usr 0.00 sys + 0.06 cusr 0.02 csys = 0.10 CPU) Result: FAIL autopkgtest [11:10:11]: test command1: ---] OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: eye Source-Version: 22.0203.1955~ds-2 Done: Jonas Smedegaard We believe that the bug you reported is fixed in the latest version of eye, 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 1006...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jonas Smedegaard (supplier of updated eye package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 30 Sep 2022 08:20:17 +0200 Source: eye Architecture: source Version: 22.0203.1955~ds-2 Distribution: unstable Urgency: medium Maintainer: Jonas Smedegaard Changed-By: Jonas Smedegaard Closes: 1006818 Changes: eye (22.0203.1955~ds-2) unstable; urgency=medium . * fix use swipl executable in PATH; tighten build-dependency on swi-prolog-nox; closes: bug#1006818, thanks to Paul Gevers, Adrian Bunk, and Lev Lamberov Checksums-Sha1: cadee877443651c106e064e3940e504d
Bug#1006818: eye: (autopkgtest) failure on non-amd64
Quoting Lev Lamberov (2022-09-29 18:10:06) > Ср 28 сен 2022 @ 18:59 Jonas Smedegaard : > > > Quoting Lev Lamberov (2022-09-28 09:35:00) > >> Since now SWI-Prolog in Debian supports setting an arch-independent path > >> to the interpreter (8.4.3+dfsg-1, uploaded on 2022-09-18, in testing > >> since 2022-09-21), I'm reassigning this bug report to eye. The eye > >> package needs rebuild against the mentioned new swi-prolog version using > >> something like this command: > >> > >> swipl -o myexe --emulator=/usr/bin/swipl -c mycode.pl > > > > Hmm - seems I will need some additional guidance - the above does not > > work for me. > > > > This is the command that was used previously: > > > > swipl -q -f eye.pl -g main -- --image eye.pvm > > > > I tried replacing with the following command: > > > > swipl -q -c eye.pl -g main --emulator=/usr/bin/swipl -o eye.pvm > > > > ...but that did *not* generate file "eye.pvm" but instead "a.out" which > > did not behave as expected (running `./a.out --help` ended in some > > prompt - I guess a SWI-Prolog prompt). > > > > I then tried this command: > > > > swipl -o myexe --emulator=/usr/bin/swipl -c eye.pl > > > > ...which generated expected file, but again it offered some prompt not > > expected eye interface. > > > > Can you help suggest a command? > > Probably the command you need is > > /usr/bin/swipl -o eye.pvm --emulator=/usr/bin/swipl -g main -c eye.pl -- > --image eye.pvm Indeed that works - Thanks! (seems my problem was that order of options matter!) - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#1012893: [Help] anfo: ftbfs with GCC-12
On 30 September 2022 10:57:16 am IST, Andreas Tille wrote: >Am Thu, Sep 29, 2022 at 05:41:52PM -0400 schrieb Aaron M. Ucko: >> Étienne Mollier writes: >> >> > I believe in the case of anfo, that warnings about auto_ptr / >> > unique_ptr are red herrings. If I search for "error:"s, then I >> > get some errors about no match for operator<: >> >> Oops, good catch. As for unique_ptr, this is evidently one of those >> situtations where whoever makes the substitution (possibly upstream >> after all at some point) will need to make additional changes to make it >> clear that their usage is safe. In particular, the ...Reader >> constructors will probably want to accept auto_ptr<> by rvalue reference >> rather than by value: >> >> std::unique_ptr&& is > >Just a note: This package was created at 11 Aug 2011 and since then >there was no new upstream release. So we can not trust that upstream >will do anything here. The popcon installations have some number >but the actual vote is 1 (which is more than zero and we never know >who is submitting popcon data or not). > >Removal of the package would be a valid option in case fixing it will >consume to much person-power from our side. I had spent a bit of time on this bug report few weeks back (IIRC it was just reported at that time). After spending sometime it was clear to me that it needs more code changes and isn't a ~trivial bug to fix. If no one gets to it, asking for removal is a sensible option. It otherwise imho becomes another time sapping package that no one cares about much. -- Best, Nilesh
Bug#1012893: [Help] anfo: ftbfs with GCC-12
Am Thu, Sep 29, 2022 at 05:41:52PM -0400 schrieb Aaron M. Ucko: > Étienne Mollier writes: > > > I believe in the case of anfo, that warnings about auto_ptr / > > unique_ptr are red herrings. If I search for "error:"s, then I > > get some errors about no match for operator<: > > Oops, good catch. As for unique_ptr, this is evidently one of those > situtations where whoever makes the substitution (possibly upstream > after all at some point) will need to make additional changes to make it > clear that their usage is safe. In particular, the ...Reader > constructors will probably want to accept auto_ptr<> by rvalue reference > rather than by value: > > std::unique_ptr&& is Just a note: This package was created at 11 Aug 2011 and since then there was no new upstream release. So we can not trust that upstream will do anything here. The popcon installations have some number but the actual vote is 1 (which is more than zero and we never know who is submitting popcon data or not). Removal of the package would be a valid option in case fixing it will consume to much person-power from our side. Kind regards Andreas. -- http://fam-tille.de
Bug#1014797: FTBFS: test failures with new libgd3
Am Fri, Sep 30, 2022 at 02:20:26AM +0200 schrieb olivier sallou: > Will try to have a look, but i have no perl knowledge and software is quite > old now... Alternatively we might consider removal. Kind regards Andreas. -- http://fam-tille.de
Processed: Re: Bug#1020986: postgis: create extension postgis fails with postgresql 13 Debian stable
Processing commands for cont...@bugs.debian.org: > tags 1020986 - a11y ftbfs Bug #1020986 [postgis] postgis: create extension postgis fails with postgresql 13 Debian stable Removed tag(s) a11y and ftbfs. > tags 1020986 + unreproducible Bug #1020986 [postgis] postgis: create extension postgis fails with postgresql 13 Debian stable Added tag(s) unreproducible. > severity 1020986 normal Bug #1020986 [postgis] postgis: create extension postgis fails with postgresql 13 Debian stable Severity set to 'normal' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 1020986: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020986 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1020987: barrier FTBFS with nocheck: missing gtest
Source: barrier Version: 2.4.0+dfsg-2 Tags: ftbfs Severity: serious Justification: last RT meeting, elbrus and ginggs said nocheck FTBFS should be serious X-Debbugs-Cc: elb...@debian.org Hi, barrier fails to build from source when enabling the nocheck build profile. The cmake stuff fails hard when it misses gtest, which happens to be annotated . There probably is some flag involved for actually removing this requirement. Failing that, the annotation on gtest should be reverted. Helmut
Bug#1020986: postgis: create extension postgis fails with postgresql 13 Debian stable
Package: postgis Version: 3.1.1+dfsg-1 Severity: serious Tags: a11y ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: matt_gibb...@fastmail.com.au Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Created a new database in Postgresql 13. Attempted to add postgis extension. Failed with ERROR: could not find function "gserialized_gist_sortsupport_2d" in file "/usr/lib/postgresql/13/lib/postgis-3.so" * What exactly did you do (or not do) that was effective (or ineffective)? Reinstalled package. Executed select postgis_extensions_upgrade(); Attempted to compile from source. Configuration unable to proceed from checking for gdal-config... no checking GDAL version... not found configure: error: gdal-config not found. Use --without-raster or try --with-gdalconfig= Installation of libgdal-dev failed. The following packages have unmet dependencies: libaom-dev : Depends: libaom0 (= 1.0.0.errata1-3) but 1:1.0.0.1-dmo1+deb10u3 is to be installed E: Unable to correct problems, you have held broken packages. Checking of libaom0 version by reinstallation failed. Reading package lists... Done Building dependency tree... Done Reading state information... Done Reinstallation of libaom0 is not possible, it cannot be downloaded. * What was the outcome of this action? Issue not resolved * What outcome did you expect instead? To enable postgis on Postgresql 13. -- System Information: Debian Release: 11.5 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-11-amd64 (SMP w/2 CPU threads) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages postgis depends on: ii libc6 2.31-13+deb11u4 ii libgdal28 3.2.2+dfsg-2+deb11u2 ii libgeos-c1v5 3.9.0-1 ii libpq514.1-1.pgdg110+1 ii libproj19 7.2.1-1 Versions of packages postgis recommends: ii postgis-doc 3.2.0+dfsg-1.pgdg110+1 ii postgresql-13-postgis-3 [postgresql-postgis] 3.1.1+dfsg-1 postgis suggests no packages. -- no debconf information
Bug#1014797: FTBFS: test failures with new libgd3
Will try to have a look, but i have no perl knowledge and software is quite old now... Le jeu. 29 sept. 2022, 19:44, Andreas Tille a écrit : > Control: tags -1 help > > Hi Aaron and Olivier, > > do you have some idea how to fix this bug? > > Kind regards > > Andreas. > > -- > http://fam-tille.de >
Bug#1020980: marked as done (nodejs: "Cannot load externalized builtin" error)
Your message dated Thu, 29 Sep 2022 22:37:18 + with message-id and subject line Bug#1020980: fixed in nodejs 18.10.0+dfsg-2 has caused the Debian Bug report #1020980, regarding nodejs: "Cannot load externalized builtin" error to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1020980: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020980 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: nodejs Version: 18.10.0+dfsg-1 Severity: grave Control: block 1020230 by -1 Dear Maintainer, Trying to run "nodejs --version" in a fresh sid chroot results in this error: Cannot load externalized builtin: "internal/deps/cjs-module-lexer/lexer:/usr/share/nodejs/cjs-module-lexer/lexer.js". 1: 0x7f88e7f6ae58 node::Abort() [/lib/x86_64-linux-gnu/libnode.so.108] 2: 0x7f88e7f4bbfb [/lib/x86_64-linux-gnu/libnode.so.108] 3: 0x7f88e7f4bd36 node::builtins::BuiltinLoader::BuiltinLoader() [/lib/x86_64-linux-gnu/libnode.so.108] 4: 0x7f88e7e881df [/lib/x86_64-linux-gnu/libnode.so.108] 5: 0x7f88ea120cee [/lib64/ld-linux-x86-64.so.2] 6: 0x7f88ea120dd4 [/lib64/ld-linux-x86-64.so.2] 7: 0x7f88ea13797a [/lib64/ld-linux-x86-64.so.2] Aborted (core dumped) A stack trace obtained with gdb is attached. -- Dmitry Shachnev (gdb) r --version Starting program: /usr/lib/nodejs/bin/node --version [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Cannot load externalized builtin: "internal/deps/cjs-module-lexer/lexer:/usr/share/nodejs/cjs-module-lexer/lexer.js". 1: 0x75e13e58 node::Abort() [/lib/x86_64-linux-gnu/libnode.so.108] 2: 0x75df4bfb [/lib/x86_64-linux-gnu/libnode.so.108] 3: 0x75df4d36 node::builtins::BuiltinLoader::BuiltinLoader() [/lib/x86_64-linux-gnu/libnode.so.108] 4: 0x75d311df [/lib/x86_64-linux-gnu/libnode.so.108] 5: 0x77fcdcee [/lib64/ld-linux-x86-64.so.2] 6: 0x77fcddd4 [/lib64/ld-linux-x86-64.so.2] 7: 0x77fe497a [/lib64/ld-linux-x86-64.so.2] Program received signal SIGABRT, Aborted. __pthread_kill_implementation (threadid=, signo=signo@entry=6, no_tid=no_tid@entry=0) at ./nptl/pthread_kill.c:44 44 ./nptl/pthread_kill.c: No such file or directory. (gdb) bt #0 __pthread_kill_implementation (threadid=, signo=signo@entry=6, no_tid=no_tid@entry=0) at ./nptl/pthread_kill.c:44 #1 0x752a55df in __pthread_kill_internal (signo=6, threadid=) at ./nptl/pthread_kill.c:78 #2 0x75259a02 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #3 0x75244469 in __GI_abort () at ./stdlib/abort.c:79 #4 0x75e13e65 in node::Abort () at ../src/node_errors.cc:299 #5 0x75df4bfb in node::builtins::BuiltinLoader::AddExternalizedBuiltin (id=id@entry=0x777eacb0 "internal/deps/cjs-module-lexer/lexer", filename=filename@entry=0x777eac80 "/usr/share/nodejs/cjs-module-lexer/lexer.js") at ../src/node_builtins.cc:261 #6 0x75df4d36 in node::builtins::BuiltinLoader::BuiltinLoader (this=0x77fa44a0 ) at ../src/node_builtins.cc:37 #7 0x75d311df in __static_initialization_and_destruction_0 (__initialize_p=1, __priority=65535) at ../src/node_builtins.cc:31 #8 _GLOBAL__sub_I_node_builtins.cc(void) () at ../src/node_builtins.cc:700 #9 0x77fcdcee in call_init (env=0x7fffe3c0, argv=0x7fffe3a8, argc=2, l=) at ./elf/dl-init.c:70 #10 call_init (l=, argc=2, argv=0x7fffe3a8, env=0x7fffe3c0) at ./elf/dl-init.c:26 #11 0x77fcddd4 in _dl_init (main_map=0x77ffe2c0, argc=2, argv=0x7fffe3a8, env=0x7fffe3c0) at ./elf/dl-init.c:117 #12 0x77fe497a in _dl_start_user () from /lib64/ld-linux-x86-64.so.2 #13 0x0002 in ?? () #14 0x7fffe621 in ?? () #15 0x7fffe63a in ?? () #16 0x in ?? () signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: nodejs Source-Version: 18.10.0+dfsg-2 Done: Jérémy Lal We believe that the bug you reported is fixed in the latest version of nodejs, 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 1020...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jérémy Lal (supplier of updated nodejs package) (This message was generated automatically at their request; if you believe that there is a problem with i
Bug#1014797: FTBFS: test failures with new libgd3
Andreas Tille writes: > do you have some idea how to fix this bug? Not offhand, sorry. In general, I'm not closely familiar with either this package or the underlying GD library (though I do know Perl); I just added myself to Uploaders a decade ago so I could most cleanly upload a packaging fix (for #624130) and stayed there by inertia. -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
Bug#1017170: marked as done (clasp: FTBFS: catch.hpp:6415:41: error: array bound is not an integer constant before ‘]’ token)
Your message dated Thu, 29 Sep 2022 22:05:14 + with message-id and subject line Bug#1004022: fixed in clasp 3.3.5-4.1 has caused the Debian Bug report #1004022, regarding clasp: FTBFS: catch.hpp:6415:41: error: array bound is not an integer constant before ‘]’ token 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.) -- 1004022: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004022 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: clasp Version: 3.3.5-4 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220813 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[4]: Entering directory '/<>/build.dir/hardening_mt' > [ 20%] Building CXX object > libpotassco/tests/CMakeFiles/test_potassco_opts.dir/test_options.cpp.o > [ 20%] Building CXX object > libpotassco/tests/CMakeFiles/test_potassco_opts.dir/test_application.cpp.o > [ 20%] Building CXX object > libpotassco/tests/CMakeFiles/test_potassco_lp.dir/test_text.cpp.o > [ 20%] Building CXX object > libpotassco/tests/CMakeFiles/test_potassco_lp.dir/test_aspif.cpp.o > [ 21%] Building CXX object > libpotassco/tests/CMakeFiles/test_potassco_lp.dir/test_smodels.cpp.o > [ 23%] Building CXX object > libpotassco/tests/CMakeFiles/test_potassco_lp.dir/test_string_convert.cpp.o > [ 25%] Building CXX object src/CMakeFiles/libclasp.dir/asp_preprocessor.cpp.o > [ 25%] Building CXX object > libpotassco/tests/CMakeFiles/test_potassco_opts.dir/test_value.cpp.o > cd /<>/build.dir/hardening_mt/libpotassco/tests && > /usr/bin/g++-10 -I/<>/libpotassco/tests > -I/<>/libpotassco -g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -O3 -Wall > -Wdate-time -D_FORTIFY_SOURCE=2 -DNDEBUG -Wdate-time -D_FORTIFY_SOURCE=2 > -DNDEBUG -std=gnu++11 -MD -MT > libpotassco/tests/CMakeFiles/test_potassco_opts.dir/test_application.cpp.o > -MF CMakeFiles/test_potassco_opts.dir/test_application.cpp.o.d -o > CMakeFiles/test_potassco_opts.dir/test_application.cpp.o -c > /<>/libpotassco/tests/test_application.cpp > cd /<>/build.dir/hardening_mt/libpotassco/tests && > /usr/bin/g++-10 -I/<>/libpotassco/tests > -I/<>/libpotassco -g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -O3 -Wall > -Wdate-time -D_FORTIFY_SOURCE=2 -DNDEBUG -Wdate-time -D_FORTIFY_SOURCE=2 > -DNDEBUG -std=c++11 -MD -MT > libpotassco/tests/CMakeFiles/test_potassco_lp.dir/test_text.cpp.o -MF > CMakeFiles/test_potassco_lp.dir/test_text.cpp.o.d -o > CMakeFiles/test_potassco_lp.dir/test_text.cpp.o -c > /<>/libpotassco/tests/test_text.cpp > cd /<>/build.dir/hardening_mt/libpotassco/tests && > /usr/bin/g++-10 -I/<>/libpotassco/tests > -I/<>/libpotassco -g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -O3 -Wall > -Wdate-time -D_FORTIFY_SOURCE=2 -DNDEBUG -Wdate-time -D_FORTIFY_SOURCE=2 > -DNDEBUG -std=c++11 -MD -MT > libpotassco/tests/CMakeFiles/test_potassco_lp.dir/test_aspif.cpp.o -MF > CMakeFiles/test_potassco_lp.dir/test_aspif.cpp.o.d -o > CMakeFiles/test_potassco_lp.dir/test_aspif.cpp.o -c > /<>/libpotassco/tests/test_aspif.cpp > cd /<>/build.dir/hardening_mt/libpotassco/tests && > /usr/bin/g++-10 -I/<>/libpotassco/tests > -I/<>/libpotassco -g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -O3 -Wall > -Wdate-time -D_FORTIFY_SOURCE=2 -DNDEBUG -Wdate-time -D_FORTIFY_SOURCE=2 > -DNDEBUG -std=gnu++11 -MD -MT > libpotassco/tests/CMakeFiles/test_potassco_opts.dir/test_options.cpp.o -MF > CMakeFiles/test_potassco_opts.dir/test_options.cpp.o.d -o > CMakeFiles/test_potassco_opts.dir/test_options.cpp.o -c > /<>/libpotassco/tests/test_options.cpp > cd /<>/build.dir/hardening_mt/libpotassco/tests && > /usr/bin/g++-10 -I/<>/libpotassco/tests > -I/<>/libpotassco -g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -O3 -Wall > -Wdate-time -D_FORTIFY_SOURCE=2 -DNDEBUG -Wdate-time -D_FORTIFY_SOURCE=2 > -DNDEBUG -std=c++11 -MD -MT > libpotassco/tests/CMakeFiles/test_potassco_lp.dir/test_smodels.cpp.o -MF > CMakeFiles/test_potassco_lp.dir/test_smodels.cpp.o.d -o > CMakeFiles/test_potassco_lp.dir/test_smodels.cpp.o -c > /<>/libpotassco/tests/test_smodels.cpp > cd /<>/build.dir/hardening_mt/libpotassco/tests && > /usr/bin/g++-10 -I/<>/libpotassco/tests > -I/<>/libpotassco -g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -Wformat -W
Bug#1020952: marked as done (gradle fails to start - org/fusesource/jansi/AnsiOutputStream error)
Your message dated Thu, 29 Sep 2022 22:07:26 + with message-id and subject line Bug#1020952: fixed in gradle 4.4.1-16 has caused the Debian Bug report #1020952, regarding gradle fails to start - org/fusesource/jansi/AnsiOutputStream error to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1020952: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020952 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gradle Version: 4.4.1-15 Severity: grave Justification: renders package unusable Dear Maintainer, running on testing a simple "gradle -version" leads to this failure. FAILURE: Build failed with an exception. * What went wrong: org/fusesource/jansi/AnsiOutputStream * Try: Run with --stacktrace option to get the stack trace. Run with --info or -- debug option to get more log output. Run with --scan to get full insights. * Get more help at https://help.gradle.org The only way I could make it work is to manually downgrade libjansi-java to version from bullseye. Although you changed the dependency to libjansi1-java, libjansi-java is still installed because it is a dependency of groovy. Rgds Fab -- System Information: Debian Release: 11.5 APT prefers stable-updates APT policy: (991, 'stable-updates'), (991, 'stable'), (95, 'testing'), (90, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-18-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr:en_US Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gradle depends on: ii default-jre-headless [java8-runtime-headless] 2:1.11-72 ii libgradle-core-java 4.4.1-13 ii libgradle-plugins-java4.4.1-13 ii openjdk-11-jre-headless [java8-runtime-headless] 11.0.16+8-1~deb11u1 gradle recommends no packages. Versions of packages gradle suggests: pn gradle-doc --- End Message --- --- Begin Message --- Source: gradle Source-Version: 4.4.1-16 Done: Markus Koschany We believe that the bug you reported is fixed in the latest version of gradle, 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 1020...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Markus Koschany (supplier of updated gradle package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 29 Sep 2022 23:26:57 +0200 Source: gradle Architecture: source Version: 4.4.1-16 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers Changed-By: Markus Koschany Closes: 1020952 Changes: gradle (4.4.1-16) unstable; urgency=medium . * Team upload. * Update normalize-classpath.patch and add jansi1.jar to the CLASSPATH. Thanks to Fab Stz for the report. (Closes: #1020952) Checksums-Sha1: 41eea8769b9c01c532841b0d5fce3e2ea68619fc 3419 gradle_4.4.1-16.dsc ad67c133138b6914ad819cc2dd38dbbdf4d5d13d 59416 gradle_4.4.1-16.debian.tar.xz 772689ade6e6852869c1d1046d515c027ae27198 16014 gradle_4.4.1-16_amd64.buildinfo Checksums-Sha256: 7829464d89baf87825e4bdfe5f342ee0937f52b467105b73ea1eaa437060b6fe 3419 gradle_4.4.1-16.dsc 2f3e6a5070b3b362eb9af7043d8463827d6df902d3ec66587c91721c18858342 59416 gradle_4.4.1-16.debian.tar.xz 8d6e8b3133392946cf6e2d8ebce63ffeb5923db8e30ce98a88e354e1fb6239af 16014 gradle_4.4.1-16_amd64.buildinfo Files: 189a4af4f03b107802cba9758ca65301 3419 java optional gradle_4.4.1-16.dsc c835ad351cd221cc381029be64e44765 59416 java optional gradle_4.4.1-16.debian.tar.xz 6ad4888ae49f93e9c9eb89e79b8d0af7 16014 java optional gradle_4.4.1-16_amd64.buildinfo -BEGIN PGP SIGNATURE- iQKjBAEBCgCNFiEErPPQiO8y7e9qGoNf2a0UuVE7UeQFAmM2EVRfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEFD RjNEMDg4RUYzMkVERUY2QTFBODM1RkQ5QUQxNEI5NTEzQjUxRTQPHGFwb0BkZWJp YW4ub3JnAAoJENmtFLlRO1HkueMQAJFLs3SYb6mdYK7PavB2UQ1ZQdWm8wXYP6er gyTsuveBIXeh3v+GLVO0hdyEHTdRLoWgPk+9+LbllJbRw5J/eI3vLkQWWr1crwAQ YsLs/ShG/w/wp/KF+EnKfhTpeVL/i8Iyf2nOSriV
Bug#1017262: marked as done (golang-github-anacrolix-dms: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 8 github.com/anacrolix/dms github.com/anacrolix/dms/dlna github.
Your message dated Thu, 29 Sep 2022 22:05:22 + with message-id and subject line Bug#1017262: fixed in golang-github-anacrolix-dms 1.1.0-3 has caused the Debian Bug report #1017262, regarding golang-github-anacrolix-dms: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 8 github.com/anacrolix/dms github.com/anacrolix/dms/dlna github.com/anacrolix/dms/dlna/dms github.com/anacrolix/dms/misc github.com/anacrolix/dms/play/termsig github.com/anacrolix/dms/rrcache github.com/anacrolix/dms/soap github.com/anacrolix/dms/ssdp github.com/anacrolix/dms/transcode github.com/anacrolix/dms/upnp github.com/anacrolix/dms/upnpav 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.) -- 1017262: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017262 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: golang-github-anacrolix-dms Version: 1.1.0-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220813 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules build > dh build --buildsystem=golang --with=golang >dh_update_autotools_config -O--buildsystem=golang >dh_autoreconf -O--buildsystem=golang >dh_auto_configure -O--buildsystem=golang >dh_auto_build -O--buildsystem=golang > cd obj-x86_64-linux-gnu && go install -trimpath -v -p 8 > github.com/anacrolix/dms github.com/anacrolix/dms/dlna > github.com/anacrolix/dms/dlna/dms github.com/anacrolix/dms/misc > github.com/anacrolix/dms/play/termsig github.com/anacrolix/dms/rrcache > github.com/anacrolix/dms/soap github.com/anacrolix/dms/ssdp > github.com/anacrolix/dms/transcode github.com/anacrolix/dms/upnp > github.com/anacrolix/dms/upnpav > internal/unsafeheader > internal/goarch > internal/goexperiment > internal/goos > internal/race > internal/cpu > runtime/internal/syscall > sync/atomic > internal/abi > runtime/internal/math > runtime/internal/sys > runtime/internal/atomic > unicode > unicode/utf8 > internal/itoa > math/bits > encoding > internal/bytealg > unicode/utf16 > golang.org/x/net/internal/iana > golang.org/x/sys/internal/unsafeheader > internal/nettrace > container/list > crypto/internal/subtle > crypto/subtle > vendor/golang.org/x/crypto/cryptobyte/asn1 > crypto/internal/boring/sig > math > vendor/golang.org/x/crypto/internal/subtle > image/color > runtime > internal/reflectlite > sync > internal/testlog > internal/singleflight > math/rand > runtime/cgo > errors > sort > github.com/anacrolix/dms/rrcache > io > internal/oserror > path > vendor/golang.org/x/net/dns/dnsmessage > strconv > crypto/internal/nistec/fiat > syscall > bytes > strings > hash > hash/crc32 > crypto/internal/randutil > reflect > crypto > crypto/rc4 > bufio > vendor/golang.org/x/text/transform > net/http/internal/ascii > regexp/syntax > html > text/tabwriter > image > hash/adler32 > time > internal/syscall/execenv > internal/syscall/unix > regexp > github.com/nfnt/resize > io/fs > context > internal/poll > embed > encoding/binary > internal/fmtsort > os > crypto/md5 > crypto/cipher > encoding/base64 > crypto/internal/edwards25519/field > vendor/golang.org/x/crypto/internal/poly1305 > crypto/internal/nistec > golang.org/x/sys/unix > encoding/pem > crypto/internal/edwards25519 > vendor/golang.org/x/crypto/curve25519/internal/field > crypto/des > crypto/internal/boring > vendor/golang.org/x/crypto/chacha20 > crypto/aes > crypto/sha512 > crypto/hmac > fmt > internal/godebug > crypto/sha1 > internal/intern > crypto/sha256 > net/netip > path/filepath > io/ioutil > vendor/golang.org/x/crypto/hkdf > vendor/golang.org/x/sys/cpu > os/signal > os/exec > vendor/golang.org/x/crypto/chacha20poly1305 > net > encoding/json > flag > encoding/xml > compress/flate > github.com/anacrolix/dms/dlna > github.com/anacrolix/dms/misc > golang.org/x/net/bpf > log > math/big > encoding/hex > compress/gzip > net/url > vendor/golang.org/x/crypto/curve25519 > vendor/golang.org/x/text/unicode/bidi > vendor/golang.org/x/text/unicode/norm > vendor/golang.org/x/net/http2/hpack > github.com/anacrolix/dms/soap > mime > mime/quotedprintable > net/http/internal > github.com/anacrolix/ffprobe > github.com/anacrolix/dms/upnpav > vendor/golang.org/x/text/secure/bidirule > text/template/parse > internal/profile > github.com/anacrolix/dms/transcode > runtime/pprof > runtime/trace > os/user > compress/zlib > image/png > crypto/rand > crypto/elliptic > crypto/internal/boring/bbig > encoding/asn1 > c
Bug#1004022: marked as done (clasp: Clasp FTBFS with glibc 2.34)
Your message dated Thu, 29 Sep 2022 22:05:14 +
with message-id
and subject line Bug#1004022: fixed in clasp 3.3.5-4.1
has caused the Debian Bug report #1004022,
regarding clasp: Clasp FTBFS with glibc 2.34
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.)
--
1004022: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004022
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: clasp
Version: 3.3.5-4
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu jammy ubuntu-patch
X-Debbugs-Cc: sl...@ubuntu.com
Dear Maintainer,
Once glibc will be upgraded to 2.34+ clasp will FTBFS.
In Ubuntu, the attached patch was applied to fix this issue:
* d/p/use-system-catch-for-glibc-2.34-compat.patch: Fix FTBFS with glibc-2.34
- Add catch v1 build-dependency
- Make use of system provided catch v1 (CTest) library
Thanks for considering the patch.
Cheers,
Lukas
-- System Information:
Debian Release: 11.0
APT prefers impish-updates
APT policy: (500, 'impish-updates'), (500, 'impish-security'), (500,
'impish'), (100, 'impish-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.13.0-23-generic (SMP w/4 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8),
LANGUAGE=de_DE:en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru clasp-3.3.5/debian/control clasp-3.3.5/debian/control
--- clasp-3.3.5/debian/control 2020-12-26 22:25:24.0 +0100
+++ clasp-3.3.5/debian/control 2022-01-19 14:36:04.0 +0100
@@ -6,6 +6,7 @@
Build-Depends: debhelper-compat (= 13),
dpkg-dev (>= 1.16.1~),
g++-10 (>= 10.2.1),
+ catch,
cmake (>= 3.1.0)
Rules-Requires-Root: no
Standards-Version: 4.5.1
diff -Nru clasp-3.3.5/debian/patches/series clasp-3.3.5/debian/patches/series
--- clasp-3.3.5/debian/patches/series 2020-12-26 21:49:38.0 +0100
+++ clasp-3.3.5/debian/patches/series 2022-01-19 14:24:03.0 +0100
@@ -1,2 +1,3 @@
clasp-manpage.patch
link-libatomic-check-gcc.patch
+use-system-catch-for-glibc-2.34-compat.patch
diff -Nru
clasp-3.3.5/debian/patches/use-system-catch-for-glibc-2.34-compat.patch
clasp-3.3.5/debian/patches/use-system-catch-for-glibc-2.34-compat.patch
--- clasp-3.3.5/debian/patches/use-system-catch-for-glibc-2.34-compat.patch
1970-01-01 01:00:00.0 +0100
+++ clasp-3.3.5/debian/patches/use-system-catch-for-glibc-2.34-compat.patch
2022-01-19 14:35:31.0 +0100
@@ -0,0 +1,296 @@
+Description: Fix 'catch' (CTest) compatibility with glibc-2.34
+ The clasp package contains an embedded copy of the 'catch' v1 (CTest)
+ library. That copy is outdated and incompatible with glibc-2.34.
+ This patch updates the test sources to use the system provided versions of
+ 'catch' instead, to fix this issue.
+ C.f.: https://github.com/catchorg/Catch2/issues/2178
+Author: Lukas Märdian
+Origin: vendor, Ubuntu
+Forwarded: no
+Bug: https://github.com/potassco/clasp/issues/73
+Last-Update: 2022-01-18
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- clasp-3.3.5.orig/libpotassco/tests/main.cpp
clasp-3.3.5/libpotassco/tests/main.cpp
+@@ -16,4 +16,4 @@ int enableDebugHeap() {
+ static int eh = enableDebugHeap();
+ #endif
+ #define CATCH_CONFIG_MAIN // This tells Catch to provide a main() - only do
this in one cpp file
+-#include "catch.hpp"
++#include
+--- clasp-3.3.5.orig/libpotassco/tests/test_application.cpp
clasp-3.3.5/libpotassco/tests/test_application.cpp
+@@ -18,7 +18,7 @@
+ // LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
+ // FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
DEALINGS
+ // IN THE SOFTWARE.
+-#include "catch.hpp"
++#include
+ #include
+ #include
+ #include
+--- clasp-3.3.5.orig/libpotassco/tests/test_aspif.cpp
clasp-3.3.5/libpotassco/tests/test_aspif.cpp
+@@ -24,7 +24,7 @@
+ #ifdef _MSC_VER
+ #pragma warning (disable : 4996)
+ #endif
+-#include "catch.hpp"
++#include
+ #include "test_common.h"
+ #include
+ #include
+--- clasp-3.3.5.orig/libpotassco/tests/test_options.cpp
clasp-3.3.5/libpotassco/tests/test_options.cpp
+@@ -18,7 +18,7 @@
+ // LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
+ // FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
DEALINGS
+ // IN THE SOFTWARE.
+-#include "catch.hpp"
++#include
+ #include
+ #include
+ #include
+--- clasp-3.3.5.or
Processed: Bug#1020980 marked as pending in nodejs
Processing control commands: > tag -1 pending Bug #1020980 [nodejs] nodejs: "Cannot load externalized builtin" error Added tag(s) pending. -- 1020980: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020980 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1020980: marked as pending in nodejs
Control: tag -1 pending Hello, Bug #1020980 in nodejs 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/nodejs/-/commit/7a949cab6d89a3ffb019f3dfe17c1e68e64bb0d3 Depends on externalized builtins (Closes: #1020980) (this message was generated automatically) -- Greetings https://bugs.debian.org/1020980
Processed: Bug#1020952 marked as pending in gradle
Processing control commands: > tag -1 pending Bug #1020952 [gradle] gradle fails to start - org/fusesource/jansi/AnsiOutputStream error Added tag(s) pending. -- 1020952: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020952 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1020952: marked as pending in gradle
Control: tag -1 pending Hello, Bug #1020952 in gradle reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/java-team/gradle/-/commit/e0ae4bd7ac5a65535db5e67823c045cea328f587 Update normalize-classpath.patch and add jansi1.jar to the CLASSPATH. Closes: #1020952 Thanks: Fab Stz for the report. (this message was generated automatically) -- Greetings https://bugs.debian.org/1020952
Bug#1012893: [Help] anfo: ftbfs with GCC-12
Étienne Mollier writes: > I believe in the case of anfo, that warnings about auto_ptr / > unique_ptr are red herrings. If I search for "error:"s, then I > get some errors about no match for operator<: Oops, good catch. As for unique_ptr, this is evidently one of those situtations where whoever makes the substitution (possibly upstream after all at some point) will need to make additional changes to make it clear that their usage is safe. In particular, the ...Reader constructors will probably want to accept auto_ptr<> by rvalue reference rather than by value: std::unique_ptr&& is -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
Bug#1020980: nodejs: "Cannot load externalized builtin" error
Package: nodejs Version: 18.10.0+dfsg-1 Severity: grave Control: block 1020230 by -1 Dear Maintainer, Trying to run "nodejs --version" in a fresh sid chroot results in this error: Cannot load externalized builtin: "internal/deps/cjs-module-lexer/lexer:/usr/share/nodejs/cjs-module-lexer/lexer.js". 1: 0x7f88e7f6ae58 node::Abort() [/lib/x86_64-linux-gnu/libnode.so.108] 2: 0x7f88e7f4bbfb [/lib/x86_64-linux-gnu/libnode.so.108] 3: 0x7f88e7f4bd36 node::builtins::BuiltinLoader::BuiltinLoader() [/lib/x86_64-linux-gnu/libnode.so.108] 4: 0x7f88e7e881df [/lib/x86_64-linux-gnu/libnode.so.108] 5: 0x7f88ea120cee [/lib64/ld-linux-x86-64.so.2] 6: 0x7f88ea120dd4 [/lib64/ld-linux-x86-64.so.2] 7: 0x7f88ea13797a [/lib64/ld-linux-x86-64.so.2] Aborted (core dumped) A stack trace obtained with gdb is attached. -- Dmitry Shachnev (gdb) r --version Starting program: /usr/lib/nodejs/bin/node --version [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Cannot load externalized builtin: "internal/deps/cjs-module-lexer/lexer:/usr/share/nodejs/cjs-module-lexer/lexer.js". 1: 0x75e13e58 node::Abort() [/lib/x86_64-linux-gnu/libnode.so.108] 2: 0x75df4bfb [/lib/x86_64-linux-gnu/libnode.so.108] 3: 0x75df4d36 node::builtins::BuiltinLoader::BuiltinLoader() [/lib/x86_64-linux-gnu/libnode.so.108] 4: 0x75d311df [/lib/x86_64-linux-gnu/libnode.so.108] 5: 0x77fcdcee [/lib64/ld-linux-x86-64.so.2] 6: 0x77fcddd4 [/lib64/ld-linux-x86-64.so.2] 7: 0x77fe497a [/lib64/ld-linux-x86-64.so.2] Program received signal SIGABRT, Aborted. __pthread_kill_implementation (threadid=, signo=signo@entry=6, no_tid=no_tid@entry=0) at ./nptl/pthread_kill.c:44 44 ./nptl/pthread_kill.c: No such file or directory. (gdb) bt #0 __pthread_kill_implementation (threadid=, signo=signo@entry=6, no_tid=no_tid@entry=0) at ./nptl/pthread_kill.c:44 #1 0x752a55df in __pthread_kill_internal (signo=6, threadid=) at ./nptl/pthread_kill.c:78 #2 0x75259a02 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #3 0x75244469 in __GI_abort () at ./stdlib/abort.c:79 #4 0x75e13e65 in node::Abort () at ../src/node_errors.cc:299 #5 0x75df4bfb in node::builtins::BuiltinLoader::AddExternalizedBuiltin (id=id@entry=0x777eacb0 "internal/deps/cjs-module-lexer/lexer", filename=filename@entry=0x777eac80 "/usr/share/nodejs/cjs-module-lexer/lexer.js") at ../src/node_builtins.cc:261 #6 0x75df4d36 in node::builtins::BuiltinLoader::BuiltinLoader (this=0x77fa44a0 ) at ../src/node_builtins.cc:37 #7 0x75d311df in __static_initialization_and_destruction_0 (__initialize_p=1, __priority=65535) at ../src/node_builtins.cc:31 #8 _GLOBAL__sub_I_node_builtins.cc(void) () at ../src/node_builtins.cc:700 #9 0x77fcdcee in call_init (env=0x7fffe3c0, argv=0x7fffe3a8, argc=2, l=) at ./elf/dl-init.c:70 #10 call_init (l=, argc=2, argv=0x7fffe3a8, env=0x7fffe3c0) at ./elf/dl-init.c:26 #11 0x77fcddd4 in _dl_init (main_map=0x77ffe2c0, argc=2, argv=0x7fffe3a8, env=0x7fffe3c0) at ./elf/dl-init.c:117 #12 0x77fe497a in _dl_start_user () from /lib64/ld-linux-x86-64.so.2 #13 0x0002 in ?? () #14 0x7fffe621 in ?? () #15 0x7fffe63a in ?? () #16 0x in ?? () signature.asc Description: PGP signature
Processed: nodejs: "Cannot load externalized builtin" error
Processing control commands: > block 1020230 by -1 Bug #1020230 [release.debian.org] transition: qtbase-opensource-src 1020230 was blocked by: 1019974 1020230 was not blocking any bugs. Added blocking bug(s) of 1020230: 1020980 -- 1020230: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020230 1020980: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020980 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1016238: marked as done (autofdo FTBFS with LLVM 14)
Your message dated Thu, 29 Sep 2022 21:35:23 +
with message-id
and subject line Bug#1016238: fixed in autofdo 0.19-2.2
has caused the Debian Bug report #1016238,
regarding autofdo FTBFS with LLVM 14
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.)
--
1016238: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016238
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: autofdo
Version: 0.19-2.1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220728 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> g++ -DHAVE_CONFIG_H -I. -I. -I./third_party/perf_data_converter/src/quipper
> -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/lib/llvm-14/include -D_GNU_SOURCE
> -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS
> -DCREATE_LLVM_PROF -g -O2 -ffile-prefix-map=/<>=.
> -fstack-protector-strong -Wformat -Werror=format-security -c -o
> create_llvm_prof-llvm_profile_writer.o `test -f 'llvm_profile_writer.cc' ||
> echo './'`llvm_profile_writer.cc
> llvm_profile_writer.cc: In static member function ‘static bool
> autofdo::LLVMProfileBuilder::Write(const std::string&,
> llvm::sampleprof::SampleProfileFormat, const autofdo::SymbolMap&, const
> autofdo::StringIndexMap&)’:
> llvm_profile_writer.cc:54:42: error: cannot convert ‘const
> llvm::StringMap’ to ‘const
> llvm::sampleprof::SampleProfileMap&’ {aka ‘const
> std::unordered_map llvm::sampleprof::FunctionSamples, llvm::sampleprof::SampleContext::Hash>&’}
>54 | if (std::error_code EC = Writer->write(profiles)) {
> | ^~~~
> | |
> | const
> llvm::StringMap
> In file included from llvm_profile_writer.h:9,
> from llvm_profile_writer.cc:30:
> /usr/lib/llvm-14/include/llvm/ProfileData/SampleProfWriter.h:55:57: note:
> initializing argument 1 of ‘virtual std::error_code
> llvm::sampleprof::SampleProfileWriter::write(const
> llvm::sampleprof::SampleProfileMap&)’
>55 | virtual std::error_code write(const SampleProfileMap &ProfileMap);
> | ^~
> make[2]: *** [Makefile:1040: create_llvm_prof-llvm_profile_writer.o] Error 1
The full build log is available from:
http://qa-logs.debian.net/2022/07/28/autofdo_0.19-2.1_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220728;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20220728&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please 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: autofdo
Source-Version: 0.19-2.2
Done: Adrian Bunk
We believe that the bug you reported is fixed in the latest version of
autofdo, 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 1016...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Adrian Bunk (supplier of updated autofdo 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, 13 Sep 2022 23:41:57 +0300
Source: autofdo
Architecture: source
Version: 0.19-2.2
Distribution: unstable
Urgency: medium
Maintainer: Debian GCC Maintainers
Changed-By: Adrian Bunk
Closes: 1016238
Changes:
autofdo (0.19-2.2) unstable; urgency=medium
.
* Non-maintainer upload.
* Build with LLVM 13. (Closes: #1016238)
Checksums-Sha1:
6e298ab28ca22aab80a699856d4b6b710591f635
Bug#1020978: FTBFS: *** DH_PHP_VERSIONS cannot be empty. Stop.
Source: tideways Version: 5.0.4-2 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Hi! I'm afraid your package fails to build: Command: dpkg-buildpackage --sanitize-env -us -uc -b -rfakeroot dpkg-buildpackage: info: source package tideways dpkg-buildpackage: info: source version 5.0.4-2 dpkg-buildpackage: info: source distribution unstable dpkg-buildpackage: info: source changed by Ondřej Surý dpkg-source --before-build . dpkg-buildpackage: info: host architecture amd64 fakeroot debian/rules clean sed: can't read debian/control.in: No such file or directory DH_PHP_VERSIONS_DEFAULT := "" DH_PHP_VERSIONS_OVERRIDE := "" AVAILABLE_PHP_VERSIONS := "8.1" /usr/share/dh-php/pkg-pecl.mk:50: *** DH_PHP_VERSIONS cannot be empty. Stop. dpkg-buildpackage: error: fakeroot debian/rules clean subprocess returned exit status 2 Meow! -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (120, 'experimental'), (1, 'experimental-debug') merged-usr: no Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.0.0-rc7-00050-g3dbd74b86e01 (SMP w/64 CPU threads) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init)
Bug#1020977: FTBFS: *** DH_PHP_VERSIONS cannot be empty. Stop.
Source: php-facedetect Version: 1.1.0-19-g135c72a-2 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Hi! I'm afraid your package fails to build: Command: dpkg-buildpackage --sanitize-env -us -uc -b -rfakeroot dpkg-buildpackage: info: source package php-facedetect dpkg-buildpackage: info: source version 1.1.0-19-g135c72a-2 dpkg-buildpackage: info: source distribution unstable dpkg-buildpackage: info: source changed by Ondřej Surý dpkg-source --before-build . dpkg-buildpackage: info: host architecture amd64 fakeroot debian/rules clean sed: can't read debian/control.in: No such file or directory DH_PHP_VERSIONS_DEFAULT := "" DH_PHP_VERSIONS_OVERRIDE := "" AVAILABLE_PHP_VERSIONS := "8.1" /usr/share/dh-php/pkg-pecl.mk:50: *** DH_PHP_VERSIONS cannot be empty. Stop. dpkg-buildpackage: error: fakeroot debian/rules clean subprocess returned exit status 2 Meow! -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (120, 'experimental'), (1, 'experimental-debug') merged-usr: no Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.0.0-rc7-00050-g3dbd74b86e01 (SMP w/64 CPU threads) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init)
Bug#1020973: FTBFS: distutils.errors.DistutilsClassError: command class [...] must subclass Command
Source: devscripts
Version: 2.22.2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Hi!
I'm afraid your package fails to build:
python3 setup.py clean -a
/<>/scripts/setup.py:5: DeprecationWarning: The distutils package
is deprecated and slated
for removal in Python 3.12. Use setuptools or check PEP 632 for potential
alternatives
from distutils.command.clean import clean as BaseCleanCommand
/usr/lib/python3/dist-packages/_distutils_hack/__init__.py:18: UserWarning:
Distutils was imported befo
re Setuptools, but importing Setuptools also replaces the `distutils` module in
`sys.modules`. This may
lead to undesirable behaviors or errors. To avoid these issues, avoid using
distutils directly, ensure
that setuptools is installed in the traditional way (e.g. not an editable
install), and/or make sure t
hat setuptools is always imported before distutils.
warnings.warn(
/usr/lib/python3/dist-packages/_distutils_hack/__init__.py:33: UserWarning:
Setuptools is replacing dis
tutils.
warnings.warn("Setuptools is replacing distutils.")
Traceback (most recent call last):
File "/<>/scripts/setup.py", line 37, in
setup(
File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 87, in
setup
return distutils.core.setup(**attrs)
File "/usr/lib/python3/dist-packages/setuptools/_distutils/core.py", line
172, in setup
ok = dist.parse_command_line()
File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line
479, in parse_command_line
args = self._parse_command_opts(parser, args)
File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 1107, in
_parse_command_opts
nargs = _Distribution._parse_command_opts(self, parser, args)
File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line
545, in _parse_command_opts
raise DistutilsClassError(
distutils.errors.DistutilsClassError: command class must subclass Com
mand
make[2]: *** [Makefile:143: clean] Error 1
Meow!
-- Package-specific info:
--- /etc/devscripts.conf ---
Empty.
--- ~/.devscripts ---
DEBCHANGE_RELEASE_HEURISTIC=log
DEBSIGN_KEYID=FD9CE2D8D7754B78AB279BBD2C3B436FEAC68101
DSCVERIFY_KEYRINGS="~/.gnupg/pubring.gpg"
-- System Information:
Debian Release: bookworm/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'),
(120, 'experimental'), (1, 'experimental-debug')
merged-usr: no
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.0.0-rc7-00050-g3dbd74b86e01 (SMP w/64 CPU threads)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
Processed: found 926699 in glibc/2.3.5-7
Processing commands for cont...@bugs.debian.org:
> found 926699 glibc/2.3.5-7
Bug #926699 {Done: Aurelien Jarno } [src:glibc] libc6
foreign/biarch: installing, removing, reinstalling in a --merged-usr system
results in unmerged /lib{32,x32}
Marked as found in versions glibc/2.3.5-7.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
926699: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926699
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1020970: elpa-evil: fails to install: wrong-number-of-arguments
Package: elpa-evil Version: 1.14.0-1 Severity: grave Justification: non-installable Hi! I'm afraid your package fails to install: Setting up elpa-evil (1.14.0-1) ... tsort: -: input contains a loop: tsort: emacsen-common tsort: elpa-goto-chg tsort: -: input contains a loop: tsort: elpa-undo-tree tsort: emacsen-common Install elpa-queue for emacs install/queue-0.2: Handling install of emacsen flavor emacs install/queue-0.2: byte-compiling for emacs Install elpa-undo-tree for emacs install/undo-tree-0.8.1: Handling install of emacsen flavor emacs install/undo-tree-0.8.1: byte-compiling for emacs Install emacsen-common for emacs emacsen-common: Handling install of emacsen flavor emacs Install elpa-goto-chg for emacs install/goto-chg-1.7.3: Handling install of emacsen flavor emacs install/goto-chg-1.7.3: byte-compiling for emacs Install elpa-evil for emacs install/evil-1.14.0: Handling install of emacsen flavor emacs install/evil-1.14.0: byte-compiling for emacs Eager macro-expansion failure: (wrong-number-of-arguments (3 . 4) 2) Eager macro-expansion failure: (wrong-number-of-arguments (3 . 4) 2) In toplevel form: evil-command-window.el:36:1: Error: Wrong number of arguments: (3 . 4), 2 Eager macro-expansion failure: (wrong-number-of-arguments (3 . 4) 2) Eager macro-expansion failure: (wrong-number-of-arguments (3 . 4) 2) In toplevel form: evil-commands.el:29:1: Error: Wrong number of arguments: (3 . 4), 2 In evil-add-to-alist: evil-common.el:128:18: Warning: ‘evil-add-to-alist’ is an obsolete function (as of 1.13.1); use ‘evil--add-to-alist’ instead. You may need to recompile code with evil macros. In evil-with-view-list: evil-common.el:3922:11: Warning: docstring wider than 80 characters In toplevel form: evil-core.el:181:31: Warning: defcustom for ‘evil-mode’ fails to specify containing group evil-core.el:181:31: Warning: defcustom for ‘evil-mode’ fails to specify containing group In toplevel form: evil-ex.el:596:1: Error: Wrong number of arguments: (3 . 4), 2 Eager macro-expansion failure: (wrong-number-of-arguments (3 . 4) 2) Eager macro-expansion failure: (wrong-number-of-arguments (3 . 4) 2) In toplevel form: evil-integration.el:35:1: Error: Wrong number of arguments: (3 . 4), 2 In toplevel form: evil-jumps.el:38:1: Warning: custom-declare-variable `evil-jumps-cross-buffers' docstring wider than 80 characters evil-jumps.el:58:1: Warning: custom-declare-variable `evil-jumps-ignored-file-patterns' docstring wider than 80 characters evil-jumps.el:71:1: Warning: defvar `evil--jumps-buffer-targets' docstring wider than 80 characters Eager macro-expansion failure: (wrong-number-of-arguments (3 . 4) 2) Eager macro-expansion failure: (wrong-number-of-arguments (3 . 4) 2) In toplevel form: evil-keybindings.el:35:1: Error: Wrong number of arguments: (3 . 4), 2 Eager macro-expansion failure: (wrong-number-of-arguments (3 . 4) 2) Eager macro-expansion failure: (wrong-number-of-arguments (3 . 4) 2) In toplevel form: evil-maps.el:29:1: Error: Wrong number of arguments: (3 . 4), 2 In evil-repeat-force-abort-p: evil-repeat.el:242:8: Warning: docstring wider than 80 characters In evil-repeat-motion: evil-repeat.el:349:8: Warning: docstring wider than 80 characters Eager macro-expansion failure: (wrong-number-of-arguments (3 . 4) 2) Eager macro-expansion failure: (wrong-number-of-arguments (3 . 4) 2) In toplevel form: evil-search.el:30:1: Error: Wrong number of arguments: (3 . 4), 2 Eager macro-expansion failure: (wrong-number-of-arguments (3 . 4) 2) Eager macro-expansion failure: (wrong-number-of-arguments (3 . 4) 2) In toplevel form: evil.el:133:1: Error: Wrong number of arguments: (3 . 4), 2 ERROR: install script from elpa-evil package failed dpkg: error processing package elpa-evil (--configure): installed elpa-evil package post-installation script subprocess returned error exit status 1 Meow! -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (120, 'experimental'), (1, 'experimental-debug') merged-usr: no Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.0.0-rc7-00050-g3dbd74b86e01 (SMP w/64 CPU threads) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages elpa-evil depends on: ii dh-elpa-helper 2.0.12 ii elpa-goto-chg 1.7.3-1 ii elpa-undo-tree 0.8.1-1 ii emacs 1:28.1+1-4 ii emacs-gtk [emacs] 1:28.1+1-4 ii emacsen-common 3.0.4 Versions of packages elpa-evil recommends: ii emacs 1:28.1+1-4 ii emacs-gtk [emacs] 1:28.1+1-4 elpa-evil suggests no packages. -- no debconf information
Processed: somehow missed raising
Processing commands for cont...@bugs.debian.org: > # I tried to raise it in message #10 > severity 1016711 serious Bug #1016711 [src:libthrust] libthrust: flaky autopkgtest Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 1016711: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016711 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bullseye freeze is coming soon
Processing control commands: > severity -1 serious Bug #956423 [node-request] node-request: deprecated upstream: should not be part of next stable Debian release Severity set to 'serious' from 'important' -- 956423: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956423 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1015102: heudiconv: FTBFS: FAILED heudiconv/tests/test_heuristics.py::test_reproin_largely_smoke[--files /<>/.pybuild/cpython3_3.10_heudiconv/build/heudiconv/tests/data-reproin]
oh, sorry about that and thanks for the ping!
I fixed it upstream already (the bug is really in datalad), and will
look to release it asap (i.e. now) and then see if we can update package
(might need to also upload new version of dcmstack first)
On Thu, 29 Sep 2022, Nilesh Patra wrote:
> Hi Yaroslav,
> Since you are the upstream for heudiconv, could you please help fix this?
> On Sat, 16 Jul 2022 15:49:48 +0200 Lucas Nussbaum wrote:
> > Source: heudiconv
> > Version: 0.11.3-1
> > Severity: serious
> > Justification: FTBFS
> > Tags: bookworm sid ftbfs
> > User: lu...@debian.org
> > Usertags: ftbfs-20220716 ftbfs-bookworm
> > Hi,
> > During a rebuild of all packages in sid, your package failed to build
> > on amd64.
> > Relevant part (hopefully):
> >dh_auto_test -O--buildsystem=pybuild
> > pybuild --test --test-pytest -i python{version} -p "3.9 3.10"
> > I: pybuild pybuild:300: cp -a heudiconv/tests
> > /<>/.pybuild/cpython3_3.9_heudiconv/build/heudiconv/
> > I: pybuild base:239: cd
> > /<>/.pybuild/cpython3_3.9_heudiconv/build; python3.9 -m pytest
> > = test session starts
> > ==
> > platform linux -- Python 3.9.13, pytest-7.1.2, pluggy-1.0.0
> > rootdir: /<>
> > collected 99 items / 1 skipped
> > heudiconv/external/tests/test_dlad.py . [
> > 1%]
> > heudiconv/heuristics/test_reproin.py [
> > 9%]
> > heudiconv/tests/test_bids.py ..s [
> > 44%]
> > heudiconv/tests/test_convert.py .. [
> > 54%]
> > heudiconv/tests/test_dicoms.py ... [
> > 57%]
> > heudiconv/tests/test_heuristics.py .F. [
> > 68%]
> > heudiconv/tests/test_main.py .. [
> > 82%]
> > heudiconv/tests/test_queue.py ...[
> > 85%]
> > heudiconv/tests/test_regression.py sss. [
> > 89%]
> > heudiconv/tests/test_tarballs.py . [
> > 90%]
> > heudiconv/tests/test_utils.py .
> > [100%]
> > === FAILURES
> > ===
> > _ test_reproin_largely_smoke[--files
> > /<>/.pybuild/cpython3_3.9_heudiconv/build/heudiconv/tests/data-reproin]
> > _
> > tmpdir =
> > local('/tmp/pytest-of-user42/pytest-9/test_reproin_largely_smoke___f0')
> > heuristic = 'reproin'
> > invocation = '--files
> > /<>/.pybuild/cpython3_3.9_heudiconv/build/heudiconv/tests/data'
> > @pytest.mark.parametrize('heuristic', ['reproin', 'convertall'])
> > @pytest.mark.parametrize(
> > 'invocation', [
> > "--files %s" % TESTS_DATA_PATH,# our new way with automated
> > groupping
> > "-d %s/{subject}/* -s 01-fmap_acq-3mm" % TESTS_DATA_PATH #
> > "old" way specifying subject
> > # should produce the same results
> > ])
> > @pytest.mark.skipif(Dataset is None, reason="no datalad")
> > def test_reproin_largely_smoke(tmpdir, heuristic, invocation):
> > is_bids = True if heuristic == 'reproin' else False
> > arg = "--random-seed 1 -f %s -c dcm2niix -o %s" \
> > % (heuristic, tmpdir)
> > if is_bids:
> > arg += " -b"
> > arg += " --datalad "
> > args = (
> > arg + invocation
> > ).split(' ')
> > # Test some safeguards
> > if invocation == "--files %s" % TESTS_DATA_PATH:
> > # Multiple subjects must not be specified -- only a single one
> > could
> > # be overridden from the command line
> > with pytest.raises(ValueError):
> > runner(args + ['--subjects', 'sub1', 'sub2'])
> > if heuristic != 'reproin':
> > # if subject is not overridden, raise error
> > with pytest.raises(NotImplementedError):
> > runner(args)
> > return
> > runner(args)
> > ds = Dataset(str(tmpdir))
> > assert ds.is_installed()
> > assert not ds.repo.dirty
> > head = ds.repo.get_hexsha()
> > # and if we rerun -- should fail
> > lgr.info(
> > "RERUNNING, expecting to FAIL since the same everything "
> > "and -c specified so we did conversion already"
> > )
> > with pytest.raises(RuntimeError):
> > runner(args)
> > # but there should be nothing new
> > assert not ds.repo.dirty
> > > assert head == ds.repo.get_hexsha()
> > E AssertionError: assert '2c32d90c7252...452338c3a611a' ==
> > '52121805b02b...b36be77769e34'
> > E - 52121805b02b454149686a4ae12b36be77769e34
> > E + 2c32d90c7252c966ebdba876f6f452338c3a611a
> > /<>/.pybui
Processed: bug 1012704 is forwarded to https://github.com/pjacklam/p5-Math-BigInt/issues/7
Processing commands for cont...@bugs.debian.org: > forwarded 1012704 https://github.com/pjacklam/p5-Math-BigInt/issues/7 Bug #1012704 [libmath-bigint-perl] libmath-bigint-perl: busy loop with bignum bitwise operations Bug #1017042 [libmath-bigint-perl] libmath-bigint-perl: busy loop with bignum bitwise operations Set Bug forwarded-to-address to 'https://github.com/pjacklam/p5-Math-BigInt/issues/7'. Set Bug forwarded-to-address to 'https://github.com/pjacklam/p5-Math-BigInt/issues/7'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1012704: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012704 1017042: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017042 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: unconfuse the bts
Processing commands for cont...@bugs.debian.org:
> reassign 926699 src:glibc
Bug #926699 {Done: Aurelien Jarno } [debootstrap,usrmerge]
libc6 foreign/biarch: installing, removing, reinstalling in a --merged-usr
system results in unmerged /lib{32,x32}
Bug reassigned from package 'debootstrap,usrmerge' to 'src:glibc'.
No longer marked as found in versions 1.
No longer marked as fixed in versions glibc/2.35-1.
> fixed 926699 2.35-1
Bug #926699 {Done: Aurelien Jarno } [src:glibc] libc6
foreign/biarch: installing, removing, reinstalling in a --merged-usr system
results in unmerged /lib{32,x32}
Marked as fixed in versions glibc/2.35-1.
> affects 926699 usrmerge debootstrap
Bug #926699 {Done: Aurelien Jarno } [src:glibc] libc6
foreign/biarch: installing, removing, reinstalling in a --merged-usr system
results in unmerged /lib{32,x32}
Added indication that 926699 affects usrmerge and debootstrap
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
926699: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926699
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: found in bookworm
Processing commands for cont...@bugs.debian.org: > found 1015188 8.1.5-1 Bug #1015188 [src:php8.1] php8.1: records wrong path to sed when built on a system with /usr/bin/sed Marked as found in versions php8.1/8.1.5-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1015188: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015188 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1018936: marked as done (busco: unsatisfiable dependency on arm64)
Your message dated Thu, 29 Sep 2022 18:04:44 + with message-id and subject line Bug#1018936: fixed in busco 5.4.3-2 has caused the Debian Bug report #1018936, regarding busco: unsatisfiable dependency on arm64 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.) -- 1018936: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018936 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: busco Version: 5.4.3-1 Severity: serious Hi Maintainer Busco is unable to migrate to testing due to an unsatisfiable dependency on arm64. Britney only checks installability of arch:all packages on amd64 and arm64, so other architectures may also be affected. I noticed that the busco binary package recently gained a Depends on hmmer, which is not built everywhere. If the Depends on hmmer is really needed, then busco should become arch:any and have a Build-Depends on hmmer to prevent it from building on architectures where it will not be installable. Regards Graham --- End Message --- --- Begin Message --- Source: busco Source-Version: 5.4.3-2 Done: Andreas Tille We believe that the bug you reported is fixed in the latest version of busco, 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 1018...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated busco package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 29 Sep 2022 19:26:31 +0200 Source: busco Architecture: source Version: 5.4.3-2 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Andreas Tille Closes: 1018936 Changes: busco (5.4.3-2) unstable; urgency=medium . * Architecture: any Closes: #1018936 Checksums-Sha1: daea888bdda151225d55c79d5ec1bf97812cdcab 2069 busco_5.4.3-2.dsc 33fe756521f021a5ae1fb6cbc15f2cf23762b911 7840 busco_5.4.3-2.debian.tar.xz 807a43fa8ccc42c0859204975b4000c83f2ecfb8 8111 busco_5.4.3-2_amd64.buildinfo Checksums-Sha256: 6697ad671c78cb9c9efc6034035ddc5da15496e88b33dbb543337833387dca55 2069 busco_5.4.3-2.dsc 1302eda2b7b8a39e7073193464bc1e97321c431d18d4181635f0b34bf1c224f9 7840 busco_5.4.3-2.debian.tar.xz 62b0efda7534b1db1f6afbaaf1573926c62255542e20eee38a2e5989a3fbb901 8111 busco_5.4.3-2_amd64.buildinfo Files: 34fece94685f64b17fe224a6c7267980 2069 science optional busco_5.4.3-2.dsc 766f4b333abedb32db42dc6367253f88 7840 science optional busco_5.4.3-2.debian.tar.xz 4ae9c86cc43e05e050d5543ec3f5327d 8111 science optional busco_5.4.3-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmM11ecRHHRpbGxlQGRl Ymlhbi5vcmcACgkQV4oElNHGRtFaVg//T089G1ACtvV8b0u9z1QiIc2ldT2EWG+l 5fpRGuwrWjTRyTMRakby72mHIDIeg32otxeQjAVzIz1QNihJ/mYApSUwW7oKPze+ vYGMVodNYxn8ESlH+ojB6o5o/W47x6QhldfFwUMLkzTBJ1XStkMXJG9WEzkSLpf9 wXfrsw1Wkp0XVfKPgtS4DS4Hwtj72SdC8PyRZoGCLtF6e0/LqjNjw2U5ugNevhSW nbJndX7rSOteT2V8ZAh61B1pAIPysebkRs4c7pj+7C4R6hdA7VF5U6sefWqjqzLK x6vgc7PNQ56TrCkx3zMHMFGenlZpl2vLTdfH57pFch03jdjwYZNPgKnKtkUcZsjJ dwTdVrw+ejxWYlLbHp3W8J8DqonMT9NqRmyrkCPF8r4Av3FIo8SmoIpk45sJ2bRu EGD46r3t5ltNDbre26KgafwtW1QbqCtcJBlfSVkm/na20kCRbsT5fhI30xEnsxtd GUd+3uD+VRBKv0djASg28xodsqdv0jTfKAyv6tptbUSiUpk5UXuu86asYT3IY36J h2elIzb8S2tTbdwjq5G4LehVraJjtfMxd2Gr7pBxFk1RxTPzDGI3Zy5BCjz/QfB8 4YrI58OZud4Lo8xxrAQtMepoCp0O9402qodycnIYINMElsCQ+Y41xlh+7LF05pz6 oVbH5yVPOA8= =W3Xy -END PGP SIGNATURE End Message ---
Processed: [bts-link] source package src:nim
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:nim > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #1006989 (http://bugs.debian.org/1006989) > # Bug title: nim: incompatible with OpenSSL 3.0 > # * https://github.com/nim-lang/Nim/issues/19604 > # * remote status changed: closed -> open > # * reopen upstream > tags 1006989 - fixed-upstream Bug #1006989 [src:nim] nim: incompatible with OpenSSL 3.0 Removed tag(s) fixed-upstream. > usertags 1006989 - status-closed Usertags were: status-closed. There are now no usertags set. > usertags 1006989 + status-open There were no usertags set. Usertags are now: status-open. > thanks Stopping processing here. Please contact me if you need assistance. -- 1006989: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006989 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1014797: FTBFS: test failures with new libgd3
Control: tags -1 help Hi Aaron and Olivier, do you have some idea how to fix this bug? Kind regards Andreas. -- http://fam-tille.de
Processed: Re: FTBFS: test failures with new libgd3
Processing control commands: > tags -1 help Bug #1014797 [src:gbrowse] FTBFS: test failures with new libgd3 Added tag(s) help. -- 1014797: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014797 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1015102: heudiconv: FTBFS: FAILED heudiconv/tests/test_heuristics.py::test_reproin_largely_smoke[--files /<>/.pybuild/cpython3_3.10_heudiconv/build/heudiconv/tests/data-reproin]
Hi Yaroslav,
Since you are the upstream for heudiconv, could you please help fix this?
On Sat, 16 Jul 2022 15:49:48 +0200 Lucas Nussbaum wrote:
> Source: heudiconv
> Version: 0.11.3-1
> Severity: serious
> Justification: FTBFS
> Tags: bookworm sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20220716 ftbfs-bookworm
>
> Hi,
>
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
>
>
> Relevant part (hopefully):
>dh_auto_test -O--buildsystem=pybuild
> pybuild --test --test-pytest -i python{version} -p "3.9 3.10"
> I: pybuild pybuild:300: cp -a heudiconv/tests
> /<>/.pybuild/cpython3_3.9_heudiconv/build/heudiconv/
> I: pybuild base:239: cd
> /<>/.pybuild/cpython3_3.9_heudiconv/build; python3.9 -m pytest
> = test session starts
> ==
> platform linux -- Python 3.9.13, pytest-7.1.2, pluggy-1.0.0
> rootdir: /<>
> collected 99 items / 1 skipped
>
> heudiconv/external/tests/test_dlad.py . [
> 1%]
> heudiconv/heuristics/test_reproin.py [
> 9%]
> heudiconv/tests/test_bids.py ..s [
> 44%]
> heudiconv/tests/test_convert.py .. [
> 54%]
> heudiconv/tests/test_dicoms.py ... [
> 57%]
> heudiconv/tests/test_heuristics.py .F. [
> 68%]
> heudiconv/tests/test_main.py .. [
> 82%]
> heudiconv/tests/test_queue.py ...[
> 85%]
> heudiconv/tests/test_regression.py sss. [
> 89%]
> heudiconv/tests/test_tarballs.py . [
> 90%]
> heudiconv/tests/test_utils.py .
> [100%]
>
> === FAILURES
> ===
> _ test_reproin_largely_smoke[--files
> /<>/.pybuild/cpython3_3.9_heudiconv/build/heudiconv/tests/data-reproin]
> _
>
> tmpdir =
> local('/tmp/pytest-of-user42/pytest-9/test_reproin_largely_smoke___f0')
> heuristic = 'reproin'
> invocation = '--files
> /<>/.pybuild/cpython3_3.9_heudiconv/build/heudiconv/tests/data'
>
> @pytest.mark.parametrize('heuristic', ['reproin', 'convertall'])
> @pytest.mark.parametrize(
> 'invocation', [
> "--files %s" % TESTS_DATA_PATH,# our new way with automated
> groupping
> "-d %s/{subject}/* -s 01-fmap_acq-3mm" % TESTS_DATA_PATH # "old"
> way specifying subject
> # should produce the same results
> ])
> @pytest.mark.skipif(Dataset is None, reason="no datalad")
> def test_reproin_largely_smoke(tmpdir, heuristic, invocation):
> is_bids = True if heuristic == 'reproin' else False
> arg = "--random-seed 1 -f %s -c dcm2niix -o %s" \
> % (heuristic, tmpdir)
> if is_bids:
> arg += " -b"
> arg += " --datalad "
> args = (
> arg + invocation
> ).split(' ')
>
> # Test some safeguards
> if invocation == "--files %s" % TESTS_DATA_PATH:
> # Multiple subjects must not be specified -- only a single one
> could
> # be overridden from the command line
> with pytest.raises(ValueError):
> runner(args + ['--subjects', 'sub1', 'sub2'])
>
> if heuristic != 'reproin':
> # if subject is not overridden, raise error
> with pytest.raises(NotImplementedError):
> runner(args)
> return
>
> runner(args)
> ds = Dataset(str(tmpdir))
> assert ds.is_installed()
> assert not ds.repo.dirty
> head = ds.repo.get_hexsha()
>
> # and if we rerun -- should fail
> lgr.info(
> "RERUNNING, expecting to FAIL since the same everything "
> "and -c specified so we did conversion already"
> )
> with pytest.raises(RuntimeError):
> runner(args)
>
> # but there should be nothing new
> assert not ds.repo.dirty
> > assert head == ds.repo.get_hexsha()
> E AssertionError: assert '2c32d90c7252...452338c3a611a' ==
> '52121805b02b...b36be77769e34'
> E - 52121805b02b454149686a4ae12b36be77769e34
> E + 2c32d90c7252c966ebdba876f6f452338c3a611a
>
> /<>/.pybuild/cpython3_3.9_heudiconv/build/heudiconv/tests/test_heuristics.py:93:
> AssertionError
> - Captured stdout call
> -
--
Best,
Nilesh
signature.asc
Description: PGP signature
Bug#1006818: eye: (autopkgtest) failure on non-amd64
Ср 28 сен 2022 @ 18:59 Jonas Smedegaard : > Quoting Lev Lamberov (2022-09-28 09:35:00) >> Since now SWI-Prolog in Debian supports setting an arch-independent path >> to the interpreter (8.4.3+dfsg-1, uploaded on 2022-09-18, in testing >> since 2022-09-21), I'm reassigning this bug report to eye. The eye >> package needs rebuild against the mentioned new swi-prolog version using >> something like this command: >> >> swipl -o myexe --emulator=/usr/bin/swipl -c mycode.pl > > Hmm - seems I will need some additional guidance - the above does not > work for me. > > This is the command that was used previously: > > swipl -q -f eye.pl -g main -- --image eye.pvm > > I tried replacing with the following command: > > swipl -q -c eye.pl -g main --emulator=/usr/bin/swipl -o eye.pvm > > ...but that did *not* generate file "eye.pvm" but instead "a.out" which > did not behave as expected (running `./a.out --help` ended in some > prompt - I guess a SWI-Prolog prompt). > > I then tried this command: > > swipl -o myexe --emulator=/usr/bin/swipl -c eye.pl > > ...which generated expected file, but again it offered some prompt not > expected eye interface. > > Can you help suggest a command? Probably the command you need is /usr/bin/swipl -o eye.pvm --emulator=/usr/bin/swipl -g main -c eye.pl -- --image eye.pvm Cheers! Lev
Bug#1018972: marked as done (blasr autopkgtest regression with pbbam 2.1.0)
Your message dated Thu, 29 Sep 2022 15:34:28 + with message-id and subject line Bug#1018972: fixed in blasr 5.3.5+dfsg-5 has caused the Debian Bug report #1018972, regarding blasr autopkgtest regression with pbbam 2.1.0 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1018972: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018972 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pbbam Version: 2.1.0+dfsg-1 Severity: serious Affects: blasr 5.3.5+dfsg-4 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu kinetic Hi Andreas, blasr's autopkgtests fail on amd64 when blasr is rebuilt against pbbam 2.1.0: [...] autopkgtest [11:27:53]: test run-unit-test: [--- [INFO] 2022-08-28T11:27:53 [blasr] started. [INFO] 2022-08-28T11:27:53 [blasr] ended. [INFO] 2022-08-28T11:27:53 [blasr] started. [INFO] 2022-08-28T11:27:53 [blasr] ended. output: OK md5sum: alignment.sam.check: FAILED WARNING: 1 computed checksum did NOT match autopkgtest [11:27:54]: test run-unit-test: ---] [...] (https://ci.debian.net/packages/b/blasr/unstable/amd64/) Unfortunately, Debian's autopkgtest infrastructure does not appropriately handle autopkgtests for binNMUs, which means this regression did not block pbbam and the new blasr from entering testing. I am not sure what the severity of this regression is, but since an autopkgtest regression would normally block testing promotion, I have filed this bug as 'serious'. If it's determined that the impact on blasr doesn't make blasr unreleasable, feel free to downgrade. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer https://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: blasr Source-Version: 5.3.5+dfsg-5 Done: Nilesh Patra We believe that the bug you reported is fixed in the latest version of blasr, 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 1018...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Nilesh Patra (supplier of updated blasr package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 29 Sep 2022 20:51:45 +0530 Source: blasr Architecture: source Version: 5.3.5+dfsg-5 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Nilesh Patra Closes: 1018972 Changes: blasr (5.3.5+dfsg-5) unstable; urgency=medium . * Team Upload. * Update lintian overrides * Fix test file substitution regex in autopkgtest (Closes: #1018972) Checksums-Sha1: 1f9c8c6ce686a894a6d5e0f703c53574b75a5d5f 2158 blasr_5.3.5+dfsg-5.dsc f3c705b9f1670a8b7017278740b18dfcc5656ee1 11256 blasr_5.3.5+dfsg-5.debian.tar.xz c81744fa07aa07e4d673d84746f628c931c0aa04 8559 blasr_5.3.5+dfsg-5_amd64.buildinfo Checksums-Sha256: afa7e99ea57b07f79439bf26a6e1f84c3667446a4315f81d8d2c415cd0f5963f 2158 blasr_5.3.5+dfsg-5.dsc 8754bed6755bcd5583e71d59031a1ce0143666bb03f49ebc39d1efb9b143d48a 11256 blasr_5.3.5+dfsg-5.debian.tar.xz a63fdd18365f1efaef3897aa96bf97ceffcd9de4966d9134c6fe313544364925 8559 blasr_5.3.5+dfsg-5_amd64.buildinfo Files: 83dcefd378a4ff276809f7c46ce7832e 2158 science optional blasr_5.3.5+dfsg-5.dsc 0f84a517a483aae786e4b0a89c36a294 11256 science optional blasr_5.3.5+dfsg-5.debian.tar.xz 08719116957948fb4514d13c8c68b67d 8559 science optional blasr_5.3.5+dfsg-5_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEEPpmlJvXcwMu/HO6mALrnSzQzafEFAmM1ubESHG5pbGVzaEBk ZWJpYW4ub3JnAAoJEAC650s0M2nx/gYQAJCFFXtIiMr8k50ux/gjtNkG9YRnzqis iW37VcZMS1XgxyJvWDYEfpLKfm9MQpUiCQ1NR1EiAEiWSsYC2mY8bhgiBwFElzpL KiW1ymtncKBZwcISOs9OMOElD9gx539ccsYxj9QgVY1e2zsR7G6u9ockxXgrPVCy 36q0Zne8c/WF7tXX08byOt/J5g5vi4FVOmrNklQvne974o3d2LQJjMtvofR8hQs7 6tbs39xCjgK1O/OPuUDp2ZgSQCQ/+n1t0Lkq61CCOJAfJGx4hgQHfQiI0ofot90u ehh8oY+KgONpcP9Ycz4swVCuEaq/Br9UeYcGLF1U4PzLKfKJyet2AOSYGxT+sQY5 GOgBQmec/lnOwmdt2vcAxU8mgNkrmfgGLtrnGFelE/TytNMOQEt
Bug#1012893: [Help] anfo: ftbfs with GCC-12
Hi Étienne, Am Thu, Sep 29, 2022 at 03:38:23PM +0200 schrieb Étienne Mollier: > I believe in the case of anfo, that warnings about auto_ptr / > unique_ptr are red herrings. If I search for "error:"s, then I > get some errors about no match for operator<: > > In file included from /usr/include/c++/12/bits/refwrap.h:39, > from /usr/include/c++/12/deque:65, > from util.h:23: > /usr/include/c++/12/bits/stl_function.h: In instantiation of ‘constexpr bool > std::less<_Tp>::operator()(const _Tp&, const _Tp&) const [with _Tp = > config::Policy]’: > /usr/include/c++/12/bits/stl_tree.h:2533:33: required from > ‘std::_Rb_tree<_Key, _Val, _KeyOfValue, _Compare, _Alloc>::iterator > std::_Rb_tree<_Key, _Val, _KeyOfValue, _Compare, _Alloc>::find(const _Key&) > [with _Key = config::Policy; _Val = config::Policy; _KeyOfValue = > std::_Identity; _Compare = std::less; _Alloc > = std::allocator; iterator = std::_Rb_tree config::Policy, std::_Identity, std::less, > std::allocator >::iterator]’ > /usr/include/c++/12/bits/stl_set.h:795:25: required from ‘std::set<_Key, > _Compare, _Alloc>::iterator std::set<_Key, _Compare, _Alloc>::find(const > key_type&) [with _Key = config::Policy; _Compare = std::less; > _Alloc = std::allocator; iterator = > std::_Rb_tree, > std::less, std::allocator >::const_iterator; > key_type = config::Policy]’ > stream.cc:479:13: required from ‘void > streams::nub(google::protobuf::RepeatedPtrField&) [with E = > config::Policy]’ > stream.cc:531:5: required from here > /usr/include/c++/12/bits/stl_function.h:408:20: error: no match for > ‘operator<’ (operand types are ‘const config::Policy’ and ‘const > config::Policy’) Sounds like a valuable hint. > I've had a similar instance of this on #1012990, on which I have > been banging my head until I unraveled the similar case #1012911 > which has been fixed following a breadcrumb of patches stemming > from a case described in clang documentation[1]. My current fix > / workaround looks like [2] (keep in mind I studied C before > C++, which is not a good thing for the quality of my C++). I never ever studied C++ - so I'm afraid I need to leave this issue for somebody else. Kind regards Andreas. > [1]: https://clang.llvm.org/compatibility.html#dep_lookup > [2]: > https://salsa.debian.org/med-team/librostlab-blast/-/blob/debian/1.0.1-13/debian/patches/gcc-12.patch > > Have a nice day, :) > -- > Étienne Mollier > Fingerprint: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da > Sent from /dev/pts/2, please excuse my verbosity. > ___ > Debian-med-packaging mailing list > debian-med-packag...@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-med-packaging -- http://fam-tille.de
Processed: reassign
Processing commands for cont...@bugs.debian.org: > reassign 1018972 blasr 5.3.5+dfsg-4 Bug #1018972 [src:pbbam] blasr autopkgtest regression with pbbam 2.1.0 Bug reassigned from package 'src:pbbam' to 'blasr'. No longer marked as found in versions pbbam/2.1.0+dfsg-1. Ignoring request to alter fixed versions of bug #1018972 to the same values previously set Bug #1018972 [blasr] blasr autopkgtest regression with pbbam 2.1.0 Marked as found in versions blasr/5.3.5+dfsg-4. > stop Stopping processing here. Please contact me if you need assistance. -- 1018972: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018972 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#995224: marked as done (relion-cuda: FTBFS with cub 1.14)
Your message dated Thu, 29 Sep 2022 15:09:04 + with message-id and subject line Bug#995224: fixed in relion-cuda 3.1.3-1 has caused the Debian Bug report #995224, regarding relion-cuda: FTBFS with cub 1.14 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.) -- 995224: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995224 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: relion-cuda Version: 3.1.0-2 Severity: serious Tags: ftbfs sid bookworm Justification: fails to build from source Hi, relion-cuda FTBFS with cub 1.14 which was just uploaded to unstable: make[4]: Entering directory '/build/relion-cuda-3.1.0/build' [ 1%] Building NVCC (Device) object src/apps/CMakeFiles/relion_gpu_util.dir/__/acc/cuda/relion_gpu_util_generated_cuda_projector_plan.cu.o cd /build/relion-cuda-3.1.0/build/src/apps/CMakeFiles/relion_gpu_util.dir/__/acc/cuda && /usr/bin/cmake -E make_directory /build/relion-cuda-3.1.0/build/src/apps/CMakeFiles/relion_gpu_util.dir/__/acc/cuda/. cd /build/relion-cuda-3.1.0/build/src/apps/CMakeFiles/relion_gpu_util.dir/__/acc/cuda && /usr/bin/cmake -D verbose:BOOL=1 -D build_configuration:STRING=Release -D generated_file:STRING=/build/relion-cuda-3.1.0/build/src/apps/CMakeFiles/relion_gpu_util.dir/__/acc/cuda/./relion_gpu_util_generated_cuda_projector_plan.cu.o -D generated_cubin_file:STRING=/build/relion-cuda-3.1.0/build/src/apps/CMakeFiles/relion_gpu_util.dir/__/acc/cuda/./relion_gpu_util_generated_cuda_projector_plan.cu.o.cubin.txt -P /build/relion-cuda-3.1.0/build/src/apps/CMakeFiles/relion_gpu_util.dir/__/acc/cuda/relion_gpu_util_generated_cuda_projector_plan.cu.o.Release.cmake -- Removing /build/relion-cuda-3.1.0/build/src/apps/CMakeFiles/relion_gpu_util.dir/__/acc/cuda/./relion_gpu_util_generated_cuda_projector_plan.cu.o /usr/bin/cmake -E rm -f /build/relion-cuda-3.1.0/build/src/apps/CMakeFiles/relion_gpu_util.dir/__/acc/cuda/./relion_gpu_util_generated_cuda_projector_plan.cu.o -- Generating dependency file: /build/relion-cuda-3.1.0/build/src/apps/CMakeFiles/relion_gpu_util.dir/__/acc/cuda/relion_gpu_util_generated_cuda_projector_plan.cu.o.NVCC-depend /usr/bin/nvcc -M -D__CUDACC__ /build/relion-cuda-3.1.0/src/acc/cuda/cuda_projector_plan.cu -o /build/relion-cuda-3.1.0/build/src/apps/CMakeFiles/relion_gpu_util.dir/__/acc/cuda/relion_gpu_util_generated_cuda_projector_plan.cu.o.NVCC-depend -ccbin /usr/bin/cc -m64 -DINSTALL_LIBRARY_DIR=/usr/lib/ -DSOURCE_DIR=/build/relion-cuda-3.1.0/src/ -DACC_CUDA=2 -DACC_CPU=1 -DCUDA -DALLOW_CTF_IN_SGD -DHAVE_SINCOS -DHAVE_TIFF -Xcompiler ,\"-g\",\"-O2\",\"-ffile-prefix-map=/build/relion-cuda-3.1.0=.\",\"-fstack-protector-strong\",\"-Wformat\",\"-Werror=format-security\",\"-O3\",\"-DNDEBUG\" -arch=sm_35 -D__INTEL_COMPILER --default-stream per-thread --disable-warnings -DNVCC -I/usr/include -I/usr/lib/x86_64-linux-gnu/openmpi/include -I/usr/lib/x86_64-linux-gnu/openmpi/include/openmpi -I/build/relion-cuda-3.1.0 -I/usr/lib/fltk -I/usr/include/x86_64-linux-gnu nvcc warning : The 'compute_35', 'compute_37', 'compute_50', 'sm_35', 'sm_37' and 'sm_50' architectures are deprecated, and may be removed in a future release (Use -Wno-deprecated-gpu-targets to suppress warning). In file included from /usr/include/thrust/system/cuda/config.h:33, from /usr/include/thrust/system/cuda/detail/execution_policy.h:35, from /usr/include/thrust/iterator/detail/device_system_tag.h:23, from /usr/include/thrust/iterator/detail/iterator_facade_category.h:22, from /usr/include/thrust/iterator/iterator_facade.h:37, from /build/relion-cuda-3.1.0/src/acc/cuda/cub/device/../iterator/arg_index_input_iterator.cuh:48, from /build/relion-cuda-3.1.0/src/acc/cuda/cub/device/device_reduce.cuh:41, from /build/relion-cuda-3.1.0/src/acc/cuda/cuda_utils_cub.cuh:16, from /build/relion-cuda-3.1.0/src/acc/cuda/cuda_projector_plan.cu:10: /usr/include/cub/util_namespace.cuh:46:2: error: #error CUB requires a definition of CUB_NS_QUALIFIER when CUB_NS_PREFIX/POSTFIX are defined. 46 | #error CUB requires a definition of CUB_NS_QUALIFIER when CUB_NS_PREFIX/POSTFIX are defined. | ^ CMake Error at relion_gpu_util_generated_cuda_projector_plan.cu.o.Release.cmake:220 (message): Error generating /build/relion-cuda-3.1.0/build/src/apps/CMakeFiles/relion_gpu_util.dir/__/acc/cuda/./relion_gpu_util_generated_cuda_projector_plan.cu.o make[4]: *** [src/apps/CMakeFiles/relion_gpu_util.dir/build.make:14
Bug#1020566: git-buildpackage's autopkg tests fail with setuptools 65
Hi Stefano,
On Thu, Sep 29, 2022 at 02:41:33PM +0200, Stefano Rivera wrote:
> Control: tag -1 + patch
>
> Not quite sure what changed in setuptools here to trigger it, but it
> really seems to be a case of our default install layout breaking
> non-standard build-systems.
>
> This patchset fixes the FTBFS.
Thanks a lot! Applied and uploaded.
-- Guido
>
> SR
>
> --
> Stefano Rivera
> http://tumbleweed.org.za/
> +1 415 683 3272
> From e464acae335f3a0c0c2d04d06f8cb1a8f441cb24 Mon Sep 17 00:00:00 2001
> From: Stefano Rivera
> Date: Thu, 29 Sep 2022 13:10:19 +0200
> Subject: [PATCH 1/2] Specify a sysconfig scheme in smoke-rpm
>
> Debian uses the posix_local scheme by default, since Python 3.10,
> causing the rpm to be built with the incorrect layout.
> ---
> debian/tests/smoke-rpm | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/debian/tests/smoke-rpm b/debian/tests/smoke-rpm
> index 90598a28..b7694d1e 100755
> --- a/debian/tests/smoke-rpm
> +++ b/debian/tests/smoke-rpm
> @@ -25,7 +25,7 @@ if python3 -c "import setuptools"; then
> --git-export-dir="$GBP_TEMPDIR" \
> -D'%__python3 /usr/bin/python3' \
> -D'%__python /usr/bin/python3' \
> - -D'%python_sitelib %(%{__python3} -Ic "from sysconfig
> import get_path; print(get_path('"'platlib'"'))")' \
> + -D'%python_sitelib %(%{__python3} -Ic "from sysconfig
> import get_path; print(get_path('"'platlib'"', '"'posix_prefix'"'))")' \
> -D'%_arch noarch' \
> -bb --nodeps
> fi
> --
> 2.35.1
>
> From f75321fd63fe294d98f79e28e4891e1ad1f97f6a Mon Sep 17 00:00:00 2001
> From: Stefano Rivera
> Date: Thu, 29 Sep 2022 13:33:43 +0200
> Subject: [PATCH 2/2] Explicitly use the deb install layout when building our
> RPM
>
> Debian defaults to installing to /usr/local, unless told otherwise. This
> is usually done by passing --install-layout=deb to setup.py, when called
> directly. But that's only an option on Debian systems that have this
> patch. Set the environment variable equivalent, instead.
> ---
> packaging/git-buildpackage.spec | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/packaging/git-buildpackage.spec b/packaging/git-buildpackage.spec
> index 17d6ed44..dbf5567c 100644
> --- a/packaging/git-buildpackage.spec
> +++ b/packaging/git-buildpackage.spec
> @@ -180,7 +180,7 @@ GIT_CEILING_DIRECTORIES=%{_builddir} \
>
> %install
> rm -rf %{buildroot}
> -WITHOUT_NOSETESTS=1 %{__python3} ./setup.py install --root=%{buildroot}
> --prefix=/usr --install-lib=%{python_sitelib}
> +DEB_PYTHON_INSTALL_LAYOUT=deb_system WITHOUT_NOSETESTS=1 %{__python3}
> ./setup.py install --root=%{buildroot} --prefix=/usr
> --install-lib=%{python_sitelib}
> find %{buildroot} -name __pycache__ | xargs -r rm -r
> mkdir -p %{buildroot}/usr/share/%{name}
> mv %{buildroot}/usr/bin/gbp-builder-mock %{buildroot}/usr/share/%{name}/
> --
> 2.35.1
>
Processed: Re: Bug#1020024: git-buildpackage: FTBFS: ModuleNotFoundError: No module named 'filelock'
Processing control commands: > reassign -1 src:pydoctor Bug #1020024 [src:git-buildpackage] git-buildpackage: FTBFS: ModuleNotFoundError: No module named 'filelock' Bug reassigned from package 'src:git-buildpackage' to 'src:pydoctor'. No longer marked as found in versions git-buildpackage/0.9.28. Ignoring request to alter fixed versions of bug #1020024 to the same values previously set > affects -1 src:git-buildpackage Bug #1020024 [src:pydoctor] git-buildpackage: FTBFS: ModuleNotFoundError: No module named 'filelock' Added indication that 1020024 affects src:git-buildpackage -- 1020024: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020024 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1020024: git-buildpackage: FTBFS: ModuleNotFoundError: No module named 'filelock'
control: reassign -1 src:pydoctor control: affects -1 src:git-buildpackage Hi, as this comes out of pydoctor I'll reassign there but have added a workaround to git-buildpackage too. Cheers, -- Guido On Sun, Sep 18, 2022 at 08:00:34AM +0200, Lucas Nussbaum wrote: > Source: git-buildpackage > Version: 0.9.28 > Severity: serious > Justification: FTBFS > Tags: bookworm sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-20220917 ftbfs-bookworm > > Hi, > > During a rebuild of all packages in sid, your package failed to build > on amd64. > > > Relevant part (hopefully): > > make[3]: Entering directory '/<>' > > mkdir -p build > > pydoctor -v gbp tests/doctests/ > > Traceback (most recent call last): > > File "/usr/lib/python3/dist-packages/cachecontrol/caches/file_cache.py", > > line 74, in __init__ > > from filelock import FileLock > > ModuleNotFoundError: No module named 'filelock' > > > > During handling of the above exception, another exception occurred: > > > > Traceback (most recent call last): > > File "/usr/bin/pydoctor", line 8, in > > sys.exit(main()) > > File "/usr/lib/python3/dist-packages/pydoctor/driver.py", line 166, in > > main > > system = get_system(options) > > File "/usr/lib/python3/dist-packages/pydoctor/driver.py", line 26, in > > get_system > > cache = prepareCache(clearCache=options.clear_intersphinx_cache, > > File "/usr/lib/python3/dist-packages/pydoctor/sphinx.py", line 431, in > > prepareCache > > return IntersphinxCache.fromParameters( > > File "/usr/lib/python3/dist-packages/pydoctor/sphinx.py", line 385, in > > fromParameters > > cache=FileCache(cachePath), > > File "/usr/lib/python3/dist-packages/cachecontrol/caches/file_cache.py", > > line 84, in __init__ > > raise ImportError(notice) > > ImportError: > > NOTE: In order to use the FileCache you must have > > filelock installed. You can install it via pip: > > pip install filelock > > > > make[3]: *** [Makefile:34: apidocs] Error 1 > > > The full build log is available from: > http://qa-logs.debian.net/2022/09/17/git-buildpackage_0.9.28_unstable.log > > All bugs filed during this archive rebuild are listed at: > https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220917;users=lu...@debian.org > or: > https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20220917&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results > > A list of current common problems and possible solutions is available at > http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! > > If you reassign this bug to another package, please 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.
Bug#1020592: marked as done (nodejs: Testsuite is using smoil keys)
Your message dated Thu, 29 Sep 2022 14:55:55 + with message-id and subject line Bug#1020592: fixed in nodejs 18.10.0+dfsg-1 has caused the Debian Bug report #1020592, regarding nodejs: Testsuite is using smoil keys 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.) -- 1020592: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020592 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: nodejs Version: 8.7.0+dfsg-5 Severity: serious control: tags -1 patch The last OpenSSL upload moved the default security level from the openssl.cnf file to build-time default so I don't have to fiddle with the config file anymore. Unfortunately nodejs is using smoil keys in its testsuite so the testsuite fails now. Previously it didn't because it used the "default" openssl.cnf which did not specify any of this so the security level was never changed from its default - 1. Now it is 2 and nodejs needs either to increase the default key size or lower security level via the config file. A patch for the latter has been attached. Sebastian From: Sebastian Andrzej Siewior Date: Fri, 23 Sep 2022 22:39:50 +0200 Subject: [PATCH] Add a CipherString for nodejs If the default security level is overwritten at build time of openssl then it is needed to lower it again for nodejs in order to pass the testsuite because it is using smoil keys. Signed-off-by: Sebastian Andrzej Siewior --- deps/openssl/openssl/apps/openssl.cnf | 10 ++ 1 file changed, 10 insertions(+) diff --git a/deps/openssl/openssl/apps/openssl.cnf b/deps/openssl/openssl/apps/openssl.cnf index 03330e0120a2..65ae201e44aa 100644 --- a/deps/openssl/openssl/apps/openssl.cnf +++ b/deps/openssl/openssl/apps/openssl.cnf @@ -15,6 +15,7 @@ HOME = . # Use this in order to automatically load providers. openssl_conf = openssl_init +nodejs_conf = nodejs_init # Comment out the next line to ignore configuration errors config_diagnostics = 1 @@ -388,3 +389,12 @@ oldcert = $insta::certout # insta.cert.pem # Certificate revocation cmd = rr oldcert = $insta::certout # insta.cert.pem + +[nodejs_init] +ssl_conf = ssl_sect + +[ssl_sect] +system_default = system_default_sect + +[system_default_sect] +CipherString = DEFAULT:@SECLEVEL=1 -- 2.37.2 --- End Message --- --- Begin Message --- Source: nodejs Source-Version: 18.10.0+dfsg-1 Done: Jérémy Lal We believe that the bug you reported is fixed in the latest version of nodejs, 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 1020...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jérémy Lal (supplier of updated nodejs package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 29 Sep 2022 11:50:59 +0200 Source: nodejs Architecture: source Version: 18.10.0+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Jérémy Lal Closes: 1020592 Changes: nodejs (18.10.0+dfsg-1) unstable; urgency=medium . [ Yadd ] * Drop /usr/lib/nodejs support . [ Jérémy Lal ] * New upstream version 18.10.0+dfsg * Configurable builtins paths: + upstream patch implementing it + augment upstream patch to support acorn, acorn-walk + configure flags for acorn, undici, cjs-module-lexer + use pkgjs-ln for system-installed modules + exclude acorn, undici, cjs-module-lexer, they are all distributed and built in their own package * Allow custom flags to be set in /etc/defaults/nodejs * Patch openssl.conf used for tests to allow smoil keys, and disable some failing tests while waiting for upstream to upgrade their test keys. (Closes: #1020592) * Use shared ngtcp2, nghttp3 * doc-generator: + fix node_modules setup using pkgjs-ln + update type-parser.mjs Checksums-Sha1: 059e2ff43cc079cf91de7930f983f0bb81f0eed8 4174 nodejs_18.10.0+dfsg-1.dsc d3a242e7edbc4f323db50d82c2f648dc8c3ecb3f 248560 nodejs_18.10.0+dfsg.orig-types-node.tar.xz a7ef814992e81a7419c7cb42c5914e90cc48ea6d 25170560 nodejs_18.10.0+dfsg.orig.tar.xz 85f339e04d2782780d0453e4e80a15913c19fc1b 162532 nodejs_18.10.0+dfsg-1.debian.tar.xz e8582961091e4684d
Bug#1012893: [Help] anfo: ftbfs with GCC-12
Hi all, Andreas Tille, on 2022-09-29: > Am Wed, Sep 28, 2022 at 04:06:23PM -0400 schrieb Aaron M. Ucko: > > Per GCC's hint, please try formally substituting unique_ptr for > > auto_ptr. I haven't tested that approach for this package, but it's > > typically a safe drop-in replacement, and generally yields compilation > > errors in the rare cases where its usage would be problematic. I believe in the case of anfo, that warnings about auto_ptr / unique_ptr are red herrings. If I search for "error:"s, then I get some errors about no match for operator<: In file included from /usr/include/c++/12/bits/refwrap.h:39, from /usr/include/c++/12/deque:65, from util.h:23: /usr/include/c++/12/bits/stl_function.h: In instantiation of ‘constexpr bool std::less<_Tp>::operator()(const _Tp&, const _Tp&) const [with _Tp = config::Policy]’: /usr/include/c++/12/bits/stl_tree.h:2533:33: required from ‘std::_Rb_tree<_Key, _Val, _KeyOfValue, _Compare, _Alloc>::iterator std::_Rb_tree<_Key, _Val, _KeyOfValue, _Compare, _Alloc>::find(const _Key&) [with _Key = config::Policy; _Val = config::Policy; _KeyOfValue = std::_Identity; _Compare = std::less; _Alloc = std::allocator; iterator = std::_Rb_tree, std::less, std::allocator >::iterator]’ /usr/include/c++/12/bits/stl_set.h:795:25: required from ‘std::set<_Key, _Compare, _Alloc>::iterator std::set<_Key, _Compare, _Alloc>::find(const key_type&) [with _Key = config::Policy; _Compare = std::less; _Alloc = std::allocator; iterator = std::_Rb_tree, std::less, std::allocator >::const_iterator; key_type = config::Policy]’ stream.cc:479:13: required from ‘void streams::nub(google::protobuf::RepeatedPtrField&) [with E = config::Policy]’ stream.cc:531:5: required from here /usr/include/c++/12/bits/stl_function.h:408:20: error: no match for ‘operator<’ (operand types are ‘const config::Policy’ and ‘const config::Policy’) I've had a similar instance of this on #1012990, on which I have been banging my head until I unraveled the similar case #1012911 which has been fixed following a breadcrumb of patches stemming from a case described in clang documentation[1]. My current fix / workaround looks like [2] (keep in mind I studied C before C++, which is not a good thing for the quality of my C++). [1]: https://clang.llvm.org/compatibility.html#dep_lookup [2]: https://salsa.debian.org/med-team/librostlab-blast/-/blob/debian/1.0.1-13/debian/patches/gcc-12.patch Have a nice day, :) -- Étienne Mollier Fingerprint: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da Sent from /dev/pts/2, please excuse my verbosity. signature.asc Description: PGP signature
Bug#1012990: marked as done (librostlab-blast: ftbfs with GCC-12)
Your message dated Thu, 29 Sep 2022 13:21:01 +
with message-id
and subject line Bug#1012990: fixed in librostlab-blast 1.0.1-13
has caused the Debian Bug report #1012990,
regarding librostlab-blast: ftbfs with GCC-12
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.)
--
1012990: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012990
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:librostlab-blast
Version: 1.0.1-12
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-12
[This bug is targeted to the upcoming bookworm release]
Please keep this issue open in the bug tracker for the package it
was filed for. If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.
The package fails to build in a test rebuild on at least amd64 with
gcc-12/g++-12, but succeeds to build with gcc-11/g++-11. The
severity of this report will be raised before the bookworm release.
The full build log can be found at:
http://qa-logs.debian.net/2022/06/09/gcc12/librostlab-blast_1.0.1-12_unstable_gcc12.log
The last lines of the build log are at the end of this report.
To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.
apt-get -t=experimental install g++
Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-11/porting_to.html
GCC 11 defaults to the GNU++17 standard. If your package installs
header files in /usr/include, please don't work around C++17 issues
by choosing a lower C++ standard for the package build, but fix these
issues to build with the C++17 standard.
[...]
| ^~~~
/usr/include/c++/12/ostream:598:5: note: template argument
deduction/substitution failed:
/usr/include/rostlab/aux_functions.h:186:43: note: mismatched types ‘const
_CharT*’ and ‘rostlab::blast::hit’
186 | { if( v_i != v.begin() ) os << ", "; os << *v_i; }
|~~~^~~
/usr/include/c++/12/bits/ostream.tcc:302:5: note: candidate: ‘template std::basic_ostream<_CharT, _Traits>&
std::operator<<(basic_ostream<_CharT, _Traits>&, const char*)’
302 | operator<<(basic_ostream<_CharT, _Traits>& __out, const char* __s)
| ^~~~
/usr/include/c++/12/bits/ostream.tcc:302:5: note: template argument
deduction/substitution failed:
/usr/include/rostlab/aux_functions.h:186:43: note: cannot convert
‘v_i.__gnu_cxx::__normal_iterator >::operator*()’ (type ‘const
rostlab::blast::hit’) to type ‘const char*’
186 | { if( v_i != v.begin() ) os << ", "; os << *v_i; }
|~~~^~~
/usr/include/c++/12/ostream:615:5: note: candidate: ‘template
std::basic_ostream& std::operator<<(basic_ostream&, const char*)’
615 | operator<<(basic_ostream& __out, const char* __s)
| ^~~~
/usr/include/c++/12/ostream:615:5: note: template argument
deduction/substitution failed:
/usr/include/rostlab/aux_functions.h:186:43: note: cannot convert
‘v_i.__gnu_cxx::__normal_iterator >::operator*()’ (type ‘const
rostlab::blast::hit’) to type ‘const char*’
186 | { if( v_i != v.begin() ) os << ", "; os << *v_i; }
|~~~^~~
/usr/include/c++/12/ostream:628:5: note: candidate: ‘template
std::basic_ostream& std::operator<<(basic_ostream&, const signed char*)’
628 | operator<<(basic_ostream& __out, const signed char*
__s)
| ^~~~
/usr/include/c++/12/ostream:628:5: note: template argument
deduction/substitution failed:
/usr/include/rostlab/aux_functions.h:186:43: note: cannot convert
‘v_i.__gnu_cxx::__normal_iterator >::operator*()’ (type ‘const
rostlab::blast::hit’) to type ‘const signed char*’
186 | { if( v_i != v.begin() ) os << ", "; os << *v_i; }
|~~~^~~
/usr/include/c++/12/ostream:633:5: note: candidate: ‘template
std::basic_ostream& std::operator<<(basic_ostream&, const unsigned char*)’
633 | operator<<(basic_ostream& __out, const unsigned
char* __s)
| ^~~~
/usr/include/c++/12/ostream:633:5: note: template argument
deduction/substitution failed:
/usr/include/rostlab/aux_functions.h:186:43: note: cannot convert
Bug#1020570: marked as done (yoyo's autopkg tests fail with setuptools 65)
Your message dated Thu, 29 Sep 2022 13:03:49 +
with message-id
and subject line Bug#1020570: fixed in yoyo 7.3.2+dfsg1-4
has caused the Debian Bug report #1020570,
regarding yoyo's autopkg tests fail with setuptools 65
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.)
--
1020570: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020570
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:yoyo
Version: 7.3.2+dfsg1-2
Severity: serious
Tags: sid bookworm
https://ci.debian.net/data/autopkgtest/testing/amd64/y/yoyo/26325726/log.gz
[...]
self =
def get_original(self):
target = self.getter()
name = self.attribute
original = DEFAULT
local = False
try:
original = target.__dict__[name]
except (AttributeError, KeyError):
original = getattr(target, name, DEFAULT)
else:
local = True
if name in _builtins and isinstance(target, ModuleType):
self.create = True
if not self.create and original is DEFAULT:
> raise AttributeError(
"%s does not have the attribute %r" % (target, name)
)
E AttributeError: 'pkg_resources._vendor.pyparsing.common.pyparsing_common'> does not have the
attribute 'datetime'
/usr/lib/python3/dist-packages/mock/mock.py:1387: AttributeError
__ TestNewMigration.test_it_calls_post_create_command __
self =
tmpdir = local('/tmp/pytest-of-debci/pytest-0/test_it_calls_post_create_comm0')
def test_it_calls_post_create_command(self, tmpdir):
self.writeconfig(post_create_command="/bin/ls -l {} {}")
> with frozendate.freeze(2001, 1, 1):
/tmp/autopkgtest-lxc.weskrs7o/downtmp/build.pgf/src/yoyo/tests/test_cli_script.py:522:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
/usr/lib/python3.10/contextlib.py:135: in __enter__
return next(self.gen)
/tmp/autopkgtest-lxc.weskrs7o/downtmp/build.pgf/src/debian/tests/frozendate.py:251:
in freeze
_patch(modules, when)
/tmp/autopkgtest-lxc.weskrs7o/downtmp/build.pgf/src/debian/tests/frozendate.py:196:
in _patch
patches = sum((_patch_module(m, relnow) for m in modules), [])
/tmp/autopkgtest-lxc.weskrs7o/downtmp/build.pgf/src/debian/tests/frozendate.py:196:
in
patches = sum((_patch_module(m, relnow) for m in modules), [])
/tmp/autopkgtest-lxc.weskrs7o/downtmp/build.pgf/src/debian/tests/frozendate.py:169:
in _patch_module
p.start()
/usr/lib/python3/dist-packages/mock/mock.py:1550: in start
result = self.__enter__()
/usr/lib/python3/dist-packages/mock/mock.py:1414: in __enter__
original, local = self.get_original()
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
self =
def get_original(self):
target = self.getter()
name = self.attribute
original = DEFAULT
local = False
try:
original = target.__dict__[name]
except (AttributeError, KeyError):
original = getattr(target, name, DEFAULT)
else:
local = True
if name in _builtins and isinstance(target, ModuleType):
self.create = True
if not self.create and original is DEFAULT:
> raise AttributeError(
"%s does not have the attribute %r" % (target, name)
)
E AttributeError: 'pkg_resources._vendor.pyparsing.common.pyparsing_common'> does not have the
attribute 'datetime'
/usr/lib/python3/dist-packages/mock/mock.py:1387: AttributeError
--- End Message ---
--- Begin Message ---
Source: yoyo
Source-Version: 7.3.2+dfsg1-4
Done: Stefano Rivera
We believe that the bug you reported is fixed in the latest version of
yoyo, 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 1020...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Stefano Rivera (supplier of updated yoyo package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Thu, 29 Sep 2022 14:35:22 +0200
Source: yoyo
Architecture: source
Version: 7.3.2+dfsg1-4
Distribution: unstabl
Bug#1020566: git-buildpackage's autopkg tests fail with setuptools 65
Control: tag -1 + patch
Not quite sure what changed in setuptools here to trigger it, but it
really seems to be a case of our default install layout breaking
non-standard build-systems.
This patchset fixes the FTBFS.
SR
--
Stefano Rivera
http://tumbleweed.org.za/
+1 415 683 3272
From e464acae335f3a0c0c2d04d06f8cb1a8f441cb24 Mon Sep 17 00:00:00 2001
From: Stefano Rivera
Date: Thu, 29 Sep 2022 13:10:19 +0200
Subject: [PATCH 1/2] Specify a sysconfig scheme in smoke-rpm
Debian uses the posix_local scheme by default, since Python 3.10,
causing the rpm to be built with the incorrect layout.
---
debian/tests/smoke-rpm | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/debian/tests/smoke-rpm b/debian/tests/smoke-rpm
index 90598a28..b7694d1e 100755
--- a/debian/tests/smoke-rpm
+++ b/debian/tests/smoke-rpm
@@ -25,7 +25,7 @@ if python3 -c "import setuptools"; then
--git-export-dir="$GBP_TEMPDIR" \
-D'%__python3 /usr/bin/python3' \
-D'%__python /usr/bin/python3' \
- -D'%python_sitelib %(%{__python3} -Ic "from sysconfig import get_path; print(get_path('"'platlib'"'))")' \
+ -D'%python_sitelib %(%{__python3} -Ic "from sysconfig import get_path; print(get_path('"'platlib'"', '"'posix_prefix'"'))")' \
-D'%_arch noarch' \
-bb --nodeps
fi
--
2.35.1
From f75321fd63fe294d98f79e28e4891e1ad1f97f6a Mon Sep 17 00:00:00 2001
From: Stefano Rivera
Date: Thu, 29 Sep 2022 13:33:43 +0200
Subject: [PATCH 2/2] Explicitly use the deb install layout when building our
RPM
Debian defaults to installing to /usr/local, unless told otherwise. This
is usually done by passing --install-layout=deb to setup.py, when called
directly. But that's only an option on Debian systems that have this
patch. Set the environment variable equivalent, instead.
---
packaging/git-buildpackage.spec | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/packaging/git-buildpackage.spec b/packaging/git-buildpackage.spec
index 17d6ed44..dbf5567c 100644
--- a/packaging/git-buildpackage.spec
+++ b/packaging/git-buildpackage.spec
@@ -180,7 +180,7 @@ GIT_CEILING_DIRECTORIES=%{_builddir} \
%install
rm -rf %{buildroot}
-WITHOUT_NOSETESTS=1 %{__python3} ./setup.py install --root=%{buildroot} --prefix=/usr --install-lib=%{python_sitelib}
+DEB_PYTHON_INSTALL_LAYOUT=deb_system WITHOUT_NOSETESTS=1 %{__python3} ./setup.py install --root=%{buildroot} --prefix=/usr --install-lib=%{python_sitelib}
find %{buildroot} -name __pycache__ | xargs -r rm -r
mkdir -p %{buildroot}/usr/share/%{name}
mv %{buildroot}/usr/bin/gbp-builder-mock %{buildroot}/usr/share/%{name}/
--
2.35.1
Processed: Re: Bug#1020566: git-buildpackage's autopkg tests fail with setuptools 65
Processing control commands: > tag -1 + patch Bug #1020566 [src:git-buildpackage] git-buildpackage's autopkg tests fail with setuptools 65 Added tag(s) patch. -- 1020566: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020566 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1020570: marked as pending in yoyo
Control: tag -1 pending Hello, Bug #1020570 in yoyo 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/yoyo/-/commit/4ea2ea6a1e2fc7f872dd13e5ec6779574d05b147 frozendate.py: Explicitly avoid patching pkg_rosurces. (Closes: #1020570) (this message was generated automatically) -- Greetings https://bugs.debian.org/1020570
Processed: Bug#1020570 marked as pending in yoyo
Processing control commands: > tag -1 pending Bug #1020570 [src:yoyo] yoyo's autopkg tests fail with setuptools 65 Added tag(s) pending. -- 1020570: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020570 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1020952: gradle fails to start - org/fusesource/jansi/AnsiOutputStream error
Package: gradle Version: 4.4.1-15 Severity: grave Justification: renders package unusable Dear Maintainer, running on testing a simple "gradle -version" leads to this failure. FAILURE: Build failed with an exception. * What went wrong: org/fusesource/jansi/AnsiOutputStream * Try: Run with --stacktrace option to get the stack trace. Run with --info or -- debug option to get more log output. Run with --scan to get full insights. * Get more help at https://help.gradle.org The only way I could make it work is to manually downgrade libjansi-java to version from bullseye. Although you changed the dependency to libjansi1-java, libjansi-java is still installed because it is a dependency of groovy. Rgds Fab -- System Information: Debian Release: 11.5 APT prefers stable-updates APT policy: (991, 'stable-updates'), (991, 'stable'), (95, 'testing'), (90, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-18-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr:en_US Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gradle depends on: ii default-jre-headless [java8-runtime-headless] 2:1.11-72 ii libgradle-core-java 4.4.1-13 ii libgradle-plugins-java4.4.1-13 ii openjdk-11-jre-headless [java8-runtime-headless] 11.0.16+8-1~deb11u1 gradle recommends no packages. Versions of packages gradle suggests: pn gradle-doc
Bug#1004598: marked as done (audacity: FTBFS with ffmpeg 5.0)
Your message dated Thu, 29 Sep 2022 12:19:40 + with message-id and subject line Bug#1004598: fixed in audacity 3.2.0+dfsg-1 has caused the Debian Bug report #1004598, regarding audacity: FTBFS with ffmpeg 5.0 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1004598: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004598 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: audacity Version: 2.4.2~dfsg0-5 Severity: important X-Debbugs-Cc: sramac...@debian.org Tags: sid bookworm ftbfs Usertags: ffmpeg5.0 audacity FTBFS with ffmpeg 5.0 (available in experimental): | cd "/<>/obj-x86_64-linux-gnu/src" && /usr/bin/ccache /usr/lib/ccache/c++ -DAudacity_EXPORTS -DBUILDING_AUDACITY -DCMAKE -DHAVE_LRINT -DHAVE_LRINTF -DHAVE_MLOCK -DWXINTL_NO_GETTEXT_MACRO -DWXUSINGDLL -D_FILE_OFFSET_BITS=64 -D__WXGTK__ -I"/<>/obj-x86_64-linux-gnu/src/private" -I"/<>/include" -I"/<>/src" -I/usr/lib/x86_64-linux-gnu/wx/include/gtk3-unicode-3.0 -I/usr/include/wx-3.0 -I"/<>/lib-src/libnyquist" -I"/<>/lib-src/portmixer/include" -isystem /usr/include/opus -isystem /usr/include/lilv-0 -isystem /usr/include/sratom-0 -isystem /usr/include/sord-0 -isystem /usr/include/serd-0 -isystem /usr/include/suil-0 -isystem /usr/include/portSMF -isystem /usr/include/soundtouch -isystem /usr/include/glib-2.0 -isystem /usr/lib/x86_64-linux-gnu/glib-2.0/include -isystem /usr/include/gtk-3.0 -isystem /usr/include/at-spi2-atk/2.0 -isystem /usr/include/at-spi-2.0 -isystem /usr/include/dbus-1.0 -isystem /usr/lib/x86_64-linux-gnu/dbus-1.0/include -isystem /usr/include/gio-unix-2.0 -isystem /usr/include/cairo -isystem /usr/include/pango-1.0 -isystem /usr/include/harfbuzz -isystem /usr/include/fribidi -isystem /usr/include/atk-1.0 -isystem /usr/include/pixman-1 -isystem /usr/include/uuid -isystem /usr/include/freetype2 -isystem /usr/include/libpng16 -isystem /usr/include/gdk-pixbuf-2.0 -isystem /usr/include/libmount -isystem /usr/include/blkid -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -std=gnu++14 -MD -MT src/CMakeFiles/Audacity.dir/AutoRecoveryDialog.cpp.o -MF CMakeFiles/Audacity.dir/AutoRecoveryDialog.cpp.o.d -o CMakeFiles/Audacity.dir/AutoRecoveryDialog.cpp.o -c "/<>/src/AutoRecoveryDialog.cpp" | In file included from /<>/include/audacity/Types.h:49, | from /<>/src/AudacityApp.h:18, | from /<>/src/AudacityApp.cpp:19: | /<>/include/audacity/Types.h: In member function ‘size_t sampleCount::as_size_t() const’: | /<>/include/audacity/Types.h:630:75: error: ‘numeric_limits’ is not a member of ‘std’ | 630 | wxASSERT(static_cast::type>(value) <= std::numeric_limits::max()); | | ^~ | /usr/include/wx-3.0/wx/debug.h:280:42: note: in definition of macro ‘wxASSERT_MSG’ | 280 | if ( wxTheAssertHandler && !(cond) && \ | | ^~~~ | /<>/include/audacity/Types.h:630:7: note: in expansion of macro ‘wxASSERT’ | 630 | wxASSERT(static_cast::type>(value) <= std::numeric_limits::max()); | | ^~~~ | /<>/include/audacity/Types.h:630:96: error: expected primary-expression before ‘>’ token | 630 | wxASSERT(static_cast::type>(value) <= std::numeric_limits::max()); | | ^ | /usr/include/wx-3.0/wx/debug.h:280:42: note: in definition of macro ‘wxASSERT_MSG’ | 280 | if ( wxTheAssertHandler && !(cond) && \ | | ^~~~ | /<>/include/audacity/Types.h:630:7: note: in expansion of macro ‘wxASSERT’ | 630 | wxASSERT(static_cast::type>(value) <= std::numeric_limits::max()); | | ^~~~ | /<>/include/audacity/Types.h:630:99: error: ‘::max’ has not been declared; did you mean ‘std::max’? | 630 | wxASSERT(static_cast::type>(value) <= std::numeric_limits::max()); | | ^~~ | /usr/include/wx-3.0/wx/debug.h:280:42: note: in definition of macro ‘wxASSERT_MSG’ | 280 | if ( wxTheAssertHandler && !(cond) && \ | | ^~~~ | /<>/include/audacity/Types.h:630:7: note: in expansion of macro ‘wxASSERT’ | 630
Bug#1012990: marked as pending in librostlab-blast
Control: tag -1 pending Hello, Bug #1012990 in librostlab-blast reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/med-team/librostlab-blast/-/commit/53b1f65cf10e60c9893dfa7c4c604abfbcc9a4da gcc-12.patch: added; fix ftbfs with gcc-12. Closes: #1012990 (this message was generated automatically) -- Greetings https://bugs.debian.org/1012990
Processed: Bug#1012990 marked as pending in librostlab-blast
Processing control commands: > tag -1 pending Bug #1012990 [src:librostlab-blast] librostlab-blast: ftbfs with GCC-12 Added tag(s) pending. -- 1012990: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012990 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#995224: marked as done (relion-cuda: FTBFS with cub 1.14)
Your message dated Thu, 29 Sep 2022 11:53:06 + with message-id and subject line Bug#995224: fixed in relion 3.1.3-2 has caused the Debian Bug report #995224, regarding relion-cuda: FTBFS with cub 1.14 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.) -- 995224: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995224 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: relion-cuda Version: 3.1.0-2 Severity: serious Tags: ftbfs sid bookworm Justification: fails to build from source Hi, relion-cuda FTBFS with cub 1.14 which was just uploaded to unstable: make[4]: Entering directory '/build/relion-cuda-3.1.0/build' [ 1%] Building NVCC (Device) object src/apps/CMakeFiles/relion_gpu_util.dir/__/acc/cuda/relion_gpu_util_generated_cuda_projector_plan.cu.o cd /build/relion-cuda-3.1.0/build/src/apps/CMakeFiles/relion_gpu_util.dir/__/acc/cuda && /usr/bin/cmake -E make_directory /build/relion-cuda-3.1.0/build/src/apps/CMakeFiles/relion_gpu_util.dir/__/acc/cuda/. cd /build/relion-cuda-3.1.0/build/src/apps/CMakeFiles/relion_gpu_util.dir/__/acc/cuda && /usr/bin/cmake -D verbose:BOOL=1 -D build_configuration:STRING=Release -D generated_file:STRING=/build/relion-cuda-3.1.0/build/src/apps/CMakeFiles/relion_gpu_util.dir/__/acc/cuda/./relion_gpu_util_generated_cuda_projector_plan.cu.o -D generated_cubin_file:STRING=/build/relion-cuda-3.1.0/build/src/apps/CMakeFiles/relion_gpu_util.dir/__/acc/cuda/./relion_gpu_util_generated_cuda_projector_plan.cu.o.cubin.txt -P /build/relion-cuda-3.1.0/build/src/apps/CMakeFiles/relion_gpu_util.dir/__/acc/cuda/relion_gpu_util_generated_cuda_projector_plan.cu.o.Release.cmake -- Removing /build/relion-cuda-3.1.0/build/src/apps/CMakeFiles/relion_gpu_util.dir/__/acc/cuda/./relion_gpu_util_generated_cuda_projector_plan.cu.o /usr/bin/cmake -E rm -f /build/relion-cuda-3.1.0/build/src/apps/CMakeFiles/relion_gpu_util.dir/__/acc/cuda/./relion_gpu_util_generated_cuda_projector_plan.cu.o -- Generating dependency file: /build/relion-cuda-3.1.0/build/src/apps/CMakeFiles/relion_gpu_util.dir/__/acc/cuda/relion_gpu_util_generated_cuda_projector_plan.cu.o.NVCC-depend /usr/bin/nvcc -M -D__CUDACC__ /build/relion-cuda-3.1.0/src/acc/cuda/cuda_projector_plan.cu -o /build/relion-cuda-3.1.0/build/src/apps/CMakeFiles/relion_gpu_util.dir/__/acc/cuda/relion_gpu_util_generated_cuda_projector_plan.cu.o.NVCC-depend -ccbin /usr/bin/cc -m64 -DINSTALL_LIBRARY_DIR=/usr/lib/ -DSOURCE_DIR=/build/relion-cuda-3.1.0/src/ -DACC_CUDA=2 -DACC_CPU=1 -DCUDA -DALLOW_CTF_IN_SGD -DHAVE_SINCOS -DHAVE_TIFF -Xcompiler ,\"-g\",\"-O2\",\"-ffile-prefix-map=/build/relion-cuda-3.1.0=.\",\"-fstack-protector-strong\",\"-Wformat\",\"-Werror=format-security\",\"-O3\",\"-DNDEBUG\" -arch=sm_35 -D__INTEL_COMPILER --default-stream per-thread --disable-warnings -DNVCC -I/usr/include -I/usr/lib/x86_64-linux-gnu/openmpi/include -I/usr/lib/x86_64-linux-gnu/openmpi/include/openmpi -I/build/relion-cuda-3.1.0 -I/usr/lib/fltk -I/usr/include/x86_64-linux-gnu nvcc warning : The 'compute_35', 'compute_37', 'compute_50', 'sm_35', 'sm_37' and 'sm_50' architectures are deprecated, and may be removed in a future release (Use -Wno-deprecated-gpu-targets to suppress warning). In file included from /usr/include/thrust/system/cuda/config.h:33, from /usr/include/thrust/system/cuda/detail/execution_policy.h:35, from /usr/include/thrust/iterator/detail/device_system_tag.h:23, from /usr/include/thrust/iterator/detail/iterator_facade_category.h:22, from /usr/include/thrust/iterator/iterator_facade.h:37, from /build/relion-cuda-3.1.0/src/acc/cuda/cub/device/../iterator/arg_index_input_iterator.cuh:48, from /build/relion-cuda-3.1.0/src/acc/cuda/cub/device/device_reduce.cuh:41, from /build/relion-cuda-3.1.0/src/acc/cuda/cuda_utils_cub.cuh:16, from /build/relion-cuda-3.1.0/src/acc/cuda/cuda_projector_plan.cu:10: /usr/include/cub/util_namespace.cuh:46:2: error: #error CUB requires a definition of CUB_NS_QUALIFIER when CUB_NS_PREFIX/POSTFIX are defined. 46 | #error CUB requires a definition of CUB_NS_QUALIFIER when CUB_NS_PREFIX/POSTFIX are defined. | ^ CMake Error at relion_gpu_util_generated_cuda_projector_plan.cu.o.Release.cmake:220 (message): Error generating /build/relion-cuda-3.1.0/build/src/apps/CMakeFiles/relion_gpu_util.dir/__/acc/cuda/./relion_gpu_util_generated_cuda_projector_plan.cu.o make[4]: *** [src/apps/CMakeFiles/relion_gpu_util.dir/build.make:1439:
Bug#1020057: marked as done (libambix: FTBFS: sndfile.c:335:9: error: conflicting types for ‘_ambix_get_sndfile’; have ‘SNDFILE *(ambix_t *)’ {aka ‘struct sf_private_tag *(struct ambix_t_struct *)’})
Your message dated Thu, 29 Sep 2022 11:49:25 +
with message-id
and subject line Bug#1020057: fixed in libambix 0.1.2-1
has caused the Debian Bug report #1020057,
regarding libambix: FTBFS: sndfile.c:335:9: error: conflicting types for
‘_ambix_get_sndfile’; have ‘SNDFILE *(ambix_t *)’ {aka ‘struct sf_private_tag
*(struct ambix_t_struct *)’}
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.)
--
1020057: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020057
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libambix
Version: 0.1.1-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220917 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> /bin/bash ../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I.
> -I../.. -I../../libambix -DAMBIX_INTERNAL -Wdate-time -D_FORTIFY_SOURCE=2
> -fvisibility=hidden -I/usr/include/opus -g -O2
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat
> -Werror=format-security -c -o libambix_la-sndfile.lo `test -f 'sndfile.c' ||
> echo './'`sndfile.c
> marker_region_chunk.c: In function ‘_ambix_read_markersregions’:
> marker_region_chunk.c:234:50: warning: dereferencing ‘void *’ pointer
> 234 | caf_stringid = (CAFStringID*)(&strings_data[4]);
> | ^
> libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -I../../libambix
> -DAMBIX_INTERNAL -Wdate-time -D_FORTIFY_SOURCE=2 -fvisibility=hidden
> -I/usr/include/opus -g -O2 -ffile-prefix-map=/<>=.
> -fstack-protector-strong -Wformat -Werror=format-security -c matrix_invert.c
> -o libambix_la-matrix_invert.o >/dev/null 2>&1
> libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -I../../libambix
> -DAMBIX_INTERNAL -Wdate-time -D_FORTIFY_SOURCE=2 -fvisibility=hidden
> -I/usr/include/opus -g -O2 -ffile-prefix-map=/<>=.
> -fstack-protector-strong -Wformat -Werror=format-security -c sndfile.c -fPIC
> -DPIC -o .libs/libambix_la-sndfile.o
> libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -I../../libambix
> -DAMBIX_INTERNAL -Wdate-time -D_FORTIFY_SOURCE=2 -fvisibility=hidden
> -I/usr/include/opus -g -O2 -ffile-prefix-map=/<>=.
> -fstack-protector-strong -Wformat -Werror=format-security -c libambix.c -o
> libambix_la-libambix.o >/dev/null 2>&1
> sndfile.c:335:9: error: conflicting types for ‘_ambix_get_sndfile’; have
> ‘SNDFILE *(ambix_t *)’ {aka ‘struct sf_private_tag *(struct ambix_t_struct
> *)’}
> 335 | SNDFILE*_ambix_get_sndfile (ambix_t*ambix) {
> | ^~
> In file included from sndfile.c:30:
> private.h:146:20: note: previous declaration of ‘_ambix_get_sndfile’ with
> type ‘struct SNDFILE_tag *(ambix_t *)’ {aka ‘struct SNDFILE_tag *(struct
> ambix_t_struct *)’}
> 146 | struct SNDFILE_tag*_ambix_get_sndfile (ambix_t*ambix);
> |^~
> make[4]: *** [Makefile:633: libambix_la-sndfile.lo] Error 1
The full build log is available from:
http://qa-logs.debian.net/2022/09/17/libambix_0.1.1-3_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220917;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20220917&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please 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: libambix
Source-Version: 0.1.2-1
Done: IOhannes m zmölnig (Debian/GNU)
We believe that the bug you reported is fixed in the latest version of
libambix, 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 1020...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
IOhannes m zmölnig (Debian/GNU) (supplier of
Bug#1020571: marked as done (cppimport's autopkg tests fail with setuptools 65)
Your message dated Thu, 29 Sep 2022 11:34:13 + with message-id and subject line Bug#1020571: fixed in cppimport 22.08.02-1 has caused the Debian Bug report #1020571, regarding cppimport's autopkg tests fail with setuptools 65 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.) -- 1020571: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020571 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:cppimport Version: 22.05.11-1 Severity: serious Tags: sid bookworm https://ci.debian.net/data/autopkgtest/testing/amd64/c/cppimport/26322071/log.gz [...] autopkgtest [07:47:50]: summary unittests3 FAIL stderr: /usr/lib/python3/dist-packages/_distutils_hack/__init__.py:18: UserWarning: Distutils was imported before Setuptools, but importing Setuptools also replaces the `distutils` module in `sys.modules`. This may lead to undesirable behaviors or errors. To avoid these issues, avoid using distutils directly, ensure that setuptools is installed in the traditional way (e.g. not an editable install), and/or make sure that setuptools is always imported before distutils. --- End Message --- --- Begin Message --- Source: cppimport Source-Version: 22.08.02-1 Done: Stefano Rivera We believe that the bug you reported is fixed in the latest version of cppimport, 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 1020...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Stefano Rivera (supplier of updated cppimport package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 29 Sep 2022 13:01:23 +0200 Source: cppimport Architecture: source Version: 22.08.02-1 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Stefano Rivera Closes: 1020571 Changes: cppimport (22.08.02-1) unstable; urgency=medium . * Team upload. * New upstream release. * Run autopkgtests tests with pytest (as I think was intended). * Run tests at build time. * Reduce autopkgtest Depends to the minimum, to test built package dependencies. * Patch: Tests: There is no "python" binary in our test environment. * Patch: Support setuptools > 60, which brings its own distutils. Fixes FTBFS. (Closes: #1020571) Checksums-Sha1: 6dd3f83c6653556be98731e6e211861438e01aef 1695 cppimport_22.08.02-1.dsc a5f44bac04f9451d6e0fc284da84335d4e545b19 19461 cppimport_22.08.02.orig.tar.gz 4d90cf273b040b99adbb3b5ae987f42fb2297dcd 3660 cppimport_22.08.02-1.debian.tar.xz 5f6984c911543dec95647efa0fbbd10504a4565d 6902 cppimport_22.08.02-1_source.buildinfo Checksums-Sha256: f288a45b067139c1e8e7262cda31d4e6224ce868c4f5fbdf2e0fb0e5098cc832 1695 cppimport_22.08.02-1.dsc c267cd7d8583631858e1fcf493018385725fa7c2c1d87113e5a49a9e70cb0269 19461 cppimport_22.08.02.orig.tar.gz 2a9fc3b01436a2dac7a2cb2b0322b6b2457aa109566834a64e0fb33a8c7e3a36 3660 cppimport_22.08.02-1.debian.tar.xz 107ecab5c5d76ca00a8baf000c1d441ce6b64aacc9b0cf2295fb03c118d7ce80 6902 cppimport_22.08.02-1_source.buildinfo Files: 70b4fdd092ca73a5a7564477a31070f3 1695 python optional cppimport_22.08.02-1.dsc 06a5429956bb436d1545fe617be9dad3 19461 python optional cppimport_22.08.02.orig.tar.gz eaa1e5cb06ef1f09be70aa54b26c8fd5 3660 python optional cppimport_22.08.02-1.debian.tar.xz 62e00f403c35171fc6a57c60e7018b7f 6902 python optional cppimport_22.08.02-1_source.buildinfo -BEGIN PGP SIGNATURE- iIoEARYKADIWIQTumtb5BSD6EfafSCRHew2wJjpU2AUCYzV8IxQcc3RlZmFub3JA ZGViaWFuLm9yZwAKCRBHew2wJjpU2C8WAP9jiqlkEefVoaQ6MVj7AivpxQnq6nrd kbNeFGvSyH6FowEAr0LSGCWybeCxPpfm/0eO+BMVET5w65QaTL9O6qigKQ4= =4axc -END PGP SIGNATURE End Message ---
Processed: Bug#1020571 marked as pending in cppimport
Processing control commands: > tag -1 pending Bug #1020571 [src:cppimport] cppimport's autopkg tests fail with setuptools 65 Added tag(s) pending. -- 1020571: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020571 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1020571: marked as pending in cppimport
Control: tag -1 pending Hello, Bug #1020571 in cppimport 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/cppimport/-/commit/c59cc000dfb716802be4811ceb196f6e110cbc20 Patch: Support setuptools > 60, which brings its own distutils. Fixes FTBFS. (Closes: #1020571) (this message was generated automatically) -- Greetings https://bugs.debian.org/1020571
Bug#1017752: marked as done (nheko: FTBFS on mipsel: virtual memory exhausted: Cannot allocate memory)
Your message dated Thu, 29 Sep 2022 09:51:52 + with message-id and subject line Bug#1017752: fixed in nheko 0.10.2-1 has caused the Debian Bug report #1017752, regarding nheko: FTBFS on mipsel: virtual memory exhausted: Cannot allocate memory 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.) -- 1017752: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017752 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: nheko Version: 0.10.0-1 Severity: serious Tags: ftbfs X-Debbugs-Cc: z...@debian.org https://buildd.debian.org/status/fetch.php?pkg=nheko&arch=mipsel&ver=0.10.0-1&stamp=1659971124&raw=0 [ 68%] Building CXX object CMakeFiles/nheko.dir/src/ReadReceiptsModel.cpp.o virtual memory exhausted: Cannot allocate memory [ 69%] Building CXX object CMakeFiles/nheko.dir/src/RegisterPage.cpp.o make[4]: *** [CMakeFiles/nheko.dir/build.make:1043: CMakeFiles/nheko.dir/src/Cache.cpp.o] Error 1 make[4]: *** Waiting for unfinished jobs make[4]: Leaving directory '/<>/build' make[3]: *** [CMakeFiles/Makefile2:153: CMakeFiles/nheko.dir/all] Error 2 make[3]: Leaving directory '/<>/build' make[2]: *** [Makefile:139: all] Error 2 make[2]: Leaving directory '/<>/build' dh_auto_build: error: cd build && make -j4 "INSTALL=install --strip-program=true" VERBOSE=1 returned exit code 2 make[1]: *** [debian/rules:22: override_dh_auto_build] Error 25 make[1]: Leaving directory '/<>' make: *** [debian/rules:11: build-arch] Error 2 dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit status 2 And it blocks the package from migrating to testing. --- End Message --- --- Begin Message --- Source: nheko Source-Version: 0.10.2-1 Done: Andreas Tille We believe that the bug you reported is fixed in the latest version of nheko, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1017...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated nheko package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 29 Sep 2022 10:56:43 +0200 Source: nheko Architecture: source Version: 0.10.2-1 Distribution: unstable Urgency: medium Maintainer: Matrix Packaging Team Changed-By: Andreas Tille Closes: 1017752 Changes: nheko (0.10.2-1) unstable; urgency=medium . * Team upload. * Do not force upstream version name in debian/gbp.conf * Reorder sequence of d/control fields by cme (routine-update) * Remove trailing whitespace in debian/rules (routine-update) * Do not parse debian/changelog in debian/rules * Do not parse d/changelog (routine-update) * Rules-Requires-Root: no (routine-update) * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository, Repository-Browse. * Lower memory requirements on architectures with only 2 GB address space (Thanks for the hint to Mathieu Malaterre) Closes: #1017752 Checksums-Sha1: 0671fd407b1bcba732e32c19bf9def9b724999d2 3212 nheko_0.10.2-1.dsc f49100d491796c29fb0b2c718bc1e2488df285ff 51894 nheko_0.10.2.orig-coeurl.tar.gz 8314c731a1b32b5f4e33d030dc934b4fe72b8abd 52441 nheko_0.10.2.orig-lmdbxx.tar.gz 97f185d9144affc58e2255c631a1940fe42d9e03 609627 nheko_0.10.2.orig-mtxclient.tar.gz e910c1c0cb28e33aa27370d96b107ffcd38a3ec6 1608905 nheko_0.10.2.orig.tar.gz 943741e479b086c6b5bbfc6a84dc7f2168f35e16 8964 nheko_0.10.2-1.debian.tar.xz 8228f0bbf19746cdf20e525e5d23be0014d6ebd5 24207 nheko_0.10.2-1_amd64.buildinfo Checksums-Sha256: f2cc60f0d4bc7f44036910f665163e418e8584d50f7ba195689cc07600e18bf7 3212 nheko_0.10.2-1.dsc 099feb59512fdd321f777547f0d4f1fc3c2d919369330f318b8c36dc646c0764 51894 nheko_0.10.2.orig-coeurl.tar.gz 5e12eb3aefe9050068af7df2c663edabc977ef34c9e7ba7b9d2c43e0ad47d8df 52441 nheko_0.10.2.orig-lmdbxx.tar.gz 4caa12ddf954b9492d1ec9b6ca32ef0fc6478555f229db074d43bc5cc29a9c89 609627 nheko_0.10.2.orig-mtxclient.tar.gz 00a0da9f134e070753efefc3bc86802b60fe385f2dea937979c0824634b4c248 1608905 nheko_0.10.2.orig.tar.gz 8808a0b69bb55fbefe69203347ebfa56030c7f18bdd0485bea71c9dcfb0c215e 8964 nheko_0.10.2-1.debian.tar.xz 0e6cc0c95059db6005d4b5346eed944fc1811479b582f37f1894fa81c4c4de60 24207 nh
Bug#1019997: marked as done (libsamplerate: FTBFS: configure.ac:54: error: macro PKG_INSTALLDIR is not defined; is a m4 file missing?)
Your message dated Thu, 29 Sep 2022 09:21:56 + with message-id and subject line Bug#1019997: fixed in libsamplerate 0.2.2-2 has caused the Debian Bug report #1019997, regarding libsamplerate: FTBFS: configure.ac:54: error: macro PKG_INSTALLDIR is not defined; is a m4 file missing? 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.) -- 1019997: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019997 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libsamplerate Version: 0.2.2-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220917 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 > configure.ac:54: error: macro PKG_INSTALLDIR is not defined; is a m4 file > missing? > m4/ax_require_defined.m4:35: AX_REQUIRE_DEFINED is expanded from... > configure.ac:54: the top level > autom4te: error: /usr/bin/m4 failed with exit status: 1 > aclocal: error: /usr/bin/autom4te failed with exit status: 1 > autoreconf: error: aclocal failed with exit status: 1 > dh_autoreconf: error: autoreconf -f -i returned exit code 1 > make: *** [debian/rules:12: binary] Error 25 The full build log is available from: http://qa-logs.debian.net/2022/09/17/libsamplerate_0.2.2-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220917;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20220917&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please 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: libsamplerate Source-Version: 0.2.2-2 Done: IOhannes m zmölnig (Debian/GNU) We believe that the bug you reported is fixed in the latest version of libsamplerate, 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 1019...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. IOhannes m zmölnig (Debian/GNU) (supplier of updated libsamplerate package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 29 Sep 2022 10:23:59 +0200 Source: libsamplerate Architecture: source Version: 0.2.2-2 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: IOhannes m zmölnig (Debian/GNU) Closes: 1019997 Changes: libsamplerate (0.2.2-2) unstable; urgency=medium . [ Jenkins ] * Avoid explicitly specifying -Wl,--as-needed linker flag. . [ Dennis Braun ] * Add pkg-config to B-Ds (Closes: #1019997) * Bump Standards Version to 4.6.1 . [ IOhannes m zmölnig (Debian/GNU) ] * Apply 'wrap-and-sort -ast' Checksums-Sha1: 3478aca23ecbb9e14295905da7d9368274f23f16 2300 libsamplerate_0.2.2-2.dsc bf3e3ce4b62dac59b2a31e11f06a0b92ebebdb90 7360 libsamplerate_0.2.2-2.debian.tar.xz Checksums-Sha256: f3d8743726841723f17126b119cd2d77a0f8678d853ec38c5ac12e53098e2fbb 2300 libsamplerate_0.2.2-2.dsc 2d73ff24333205a360d07fc4aacc04149259fb84901013970529698ebad3124f 7360 libsamplerate_0.2.2-2.debian.tar.xz Files: 61d64f1582e71b6ff316d61b230ae491 2300 sound optional libsamplerate_0.2.2-2.dsc 25c280b4c05a5bb146901cb44fe4550f 7360 sound optional libsamplerate_0.2.2-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEdAXnRVdICXNIABVttlAZxH96NvgFAmM1VqkACgkQtlAZxH96 NvgkUw//RthnJZHDs3J1MSxetWr5HQ4xDhbtVWvd3dAI/5fUNRDiRnrqnoToCA7+ gP2A1xvm/hmpKjsx7L1sTEuQNkisYURWdsx1TABODixY65Bkg6x2CZW4ttqme4Z2 L6GH8v2TjSgVB8Lcrs6oAQsCUlzjN8YuKGFgu3Y3mtp5ngQDtt78EtryDSoUtA6u s7V
Bug#1017752: Do you see any chance to fix the "virtual memory exhausted" for nheko on mipsel VM
On Wed, Sep 28, 2022 at 10:06 PM Andreas Tille wrote: > > Hi mips porters, > > in bug #1017752 a > >FTBFS on mipsel: virtual memory exhausted: Cannot allocate memory > > is reported. This remains for the new upstream version I've just > uploaded to experimental[1]. Do you see any chance to fix the memory > constraint for the autobuilder VM? If not I'll remove mipsel from the > list of supported architectures to enable testing migration. Here is the trick I used on those arches for openvdb: [...] # Disable optimization on mipsel because the compiler is running out of memory # see #847752 / #879636 ifneq (,$(filter $(DEB_BUILD_ARCH), armel armhf i386 mipsel hppa riscv64 sh4 x32)) CXXFLAGS:=$(filter-out -O2,$(CXXFLAGS)) --param ggc-min-expand=10 -O1 endif [...] https://salsa.debian.org/multimedia-team/openvdb/-/blob/debian/9.1.0-7/debian/rules#L22-26
Bug#1017752: Do you see any chance to fix the "virtual memory exhausted" for nheko on mipsel VM
On Thu, Sep 29, 2022 at 9:14 AM Mathieu Malaterre wrote: > > On Wed, Sep 28, 2022 at 10:06 PM Andreas Tille wrote: > > > > Hi mips porters, > > > > in bug #1017752 a > > > >FTBFS on mipsel: virtual memory exhausted: Cannot allocate memory > > > > is reported. This remains for the new upstream version I've just > > uploaded to experimental[1]. Do you see any chance to fix the memory > > constraint for the autobuilder VM? If not I'll remove mipsel from the > > list of supported architectures to enable testing migration. > > Here is the trick I used on those arches for openvdb: > > [...] > # Disable optimization on mipsel because the compiler is running out of memory > # see #847752 / #879636 > ifneq (,$(filter $(DEB_BUILD_ARCH), armel armhf i386 mipsel hppa > riscv64 sh4 x32)) > CXXFLAGS:=$(filter-out -O2,$(CXXFLAGS)) --param ggc-min-expand=10 -O1 > endif > [...] > > https://salsa.debian.org/multimedia-team/openvdb/-/blob/debian/9.1.0-7/debian/rules#L22-26 Here is another simpler one: * https://salsa.debian.org/webkit-team/webkit/-/blob/debian/2.38.0-1/debian/rules#L66
Bug#1012893: [Help] anfo: ftbfs with GCC-12
Hi Aaron, Am Wed, Sep 28, 2022 at 04:06:23PM -0400 schrieb Aaron M. Ucko: > > Per GCC's hint, please try formally substituting unique_ptr for > auto_ptr. I haven't tested that approach for this package, but it's > typically a safe drop-in replacement, and generally yields compilation > errors in the rare cases where its usage would be problematic. Thanks a lot for your hint. In b37ea9fe211292d63bbc5174c6f85a71eb442390 I simply replaced std::auto_ptr by std:unique_ptr. Since this ended up in a compile error at some auto_ptr (without std::) instances I replaced in commit adfab8681fe2abc495178691a95b5bd53bde4a67 auto_ptr by unique_ptr. This also failed and thus my last attempt 24384abbcc03a54c793bd34e241617e809078223 was to replace unique_ptr by std:unique_ptr which fails as well[1]. I will stop here with my wild-guessing now and hope for further helpful hints. Kind regards Andreas. [1] https://salsa.debian.org/med-team/anfo/-/jobs/3313737 -- http://fam-tille.de
