Bug#980601: marked as done (chatty: FTBFS: phonenumber.pb.h:47:51: error: ‘AuxiliaryParseTableField’ in namespace ‘google::protobuf::internal’ does not name a type; did you mean ‘AuxillaryParseTableFi
Your message dated Thu, 21 Jan 2021 08:55:17 +0100 with message-id <20210121075517.ga8...@xanadu.blop.info> and subject line Re: [Debian-on-mobile-maintainers] Bug#980601: Bug#980601: chatty: FTBFS: phonenumber.pb.h:47:51: error: ‘AuxiliaryParseTableField’ in namespace ‘google::protobuf::internal’ does not name a type; did you mean ‘AuxillaryParseTableField’? has caused the Debian Bug report #980601, regarding chatty: FTBFS: phonenumber.pb.h:47:51: error: ‘AuxiliaryParseTableField’ in namespace ‘google::protobuf::internal’ does not name a type; did you mean ‘AuxillaryParseTableField’? 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.) -- 980601: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980601 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: chatty Version: 0.2.0-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20210120 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > c++ -Isrc/libchatty.so.p -Isrc -I../src -I/usr/include/libmount > -I/usr/include/blkid -I/usr/include/glib-2.0 > -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/gtk-3.0 > -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 > -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include > -I/usr/include/gio-unix-2.0 -I/usr/include/cairo -I/usr/include/pango-1.0 > -I/usr/include/fribidi -I/usr/include/harfbuzz -I/usr/include/atk-1.0 > -I/usr/include/pixman-1 -I/usr/include/uuid -I/usr/include/freetype2 > -I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 > -I/usr/include/libpurple -I/usr/include/libhandy-1 > -I/usr/include/evolution-data-server -I/usr/include/nss -I/usr/include/nspr > -I/usr/include/libsecret-1 -I/usr/include/libsoup-2.4 -I/usr/include/libxml2 > -I/usr/include/gsettings-desktop-schemas -I/usr/include/libfeedback-0.0 > -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch > -Wnon-virtual-dtor -g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > -D_FORTIFY_SOURCE=2 -fPIC -pthread -MD -MQ > src/libchatty.so.p/chatty-phone-utils.cpp.o -MF > src/libchatty.so.p/chatty-phone-utils.cpp.o.d -o > src/libchatty.so.p/chatty-phone-utils.cpp.o -c ../src/chatty-phone-utils.cpp > In file included from /usr/include/phonenumbers/phonenumberutil.h:34, > from ../src/chatty-phone-utils.cpp:18: > /usr/include/phonenumbers/phonenumber.pb.h:47:51: error: > ‘AuxiliaryParseTableField’ in namespace ‘google::protobuf::internal’ does not > name a type; did you mean ‘AuxillaryParseTableField’? >47 | static const > ::PROTOBUF_NAMESPACE_ID::internal::AuxiliaryParseTableField aux[] > | > ^~~~ > | > AuxillaryParseTableField > In file included from /usr/include/phonenumbers/phonenumberutil.h:34, > from ../src/chatty-phone-utils.cpp:18: > /usr/include/phonenumbers/phonenumber.pb.h:88:30: error: ‘ConstStringParam’ > is not a member of ‘google::protobuf’ >88 | ::PROTOBUF_NAMESPACE_ID::ConstStringParam name, > PhoneNumber_CountryCodeSource* value); > | ^~~~ > /usr/include/phonenumbers/phonenumber.pb.h:88:82: error: expected > primary-expression before ‘*’ token >88 | ::PROTOBUF_NAMESPACE_ID::ConstStringParam name, > PhoneNumber_CountryCodeSource* value); > | >^ > /usr/include/phonenumbers/phonenumber.pb.h:88:84: error: ‘value’ was not > declared in this scope >88 | ::PROTOBUF_NAMESPACE_ID::ConstStringParam name, > PhoneNumber_CountryCodeSource* value); > | > ^ > /usr/include/phonenumbers/phonenumber.pb.h:88:89: error: expression list > treated as compound expression in initializer [-fpermissive] >88 | ::PROTOBUF_NAMESPACE_ID::ConstStringParam name, > PhoneNumber_CountryCodeSource* value); > | > ^ > /usr/include/phonenumbers/phonenumber.pb.
Bug#980585: marked as done (ruby-in-parallel: FTBFS: ERROR: Test "ruby2.7" failed: Failure/Error: expect(@result_3).to_not eq(true))
Your message dated Thu, 21 Jan 2021 07:48:20 + with message-id and subject line Bug#980585: fixed in ruby-in-parallel 0.1.17-1.3 has caused the Debian Bug report #980585, regarding ruby-in-parallel: FTBFS: ERROR: Test "ruby2.7" failed: Failure/Error: expect(@result_3).to_not eq(true) 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.) -- 980585: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980585 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-in-parallel Version: 0.1.17-1.2 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20210120 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This is the same failure as #979700 -- I can still reproduce it with the updated package. Relevant part (hopefully): > Failure/Error: expect(@result_3).to_not eq(true) > >expected: value != true > got: true > >(compared using ==) > # ./spec/in-paralell_spec.rb:137:in `block (2 levels) in (required)>' > > Finished in 9.92 seconds (files took 0.10551 seconds to load) > 19 examples, 1 failure > > Failed examples: > > rspec ./spec/in-paralell_spec.rb:130 # .run_in_parallel should raise an > exception and return immediately with kill_all_on_error and one of the > processes errors. > > /usr/bin/ruby2.7 > -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/exe/rspec > --pattern ./spec/\*\*/\*_spec.rb --format documentation failed > ERROR: Test "ruby2.7" failed: The full build log is available from: http://qa-logs.debian.net/2021/01/20/ruby-in-parallel_0.1.17-1.2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with me so that we can identify if something relevant changed in the meantime. About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Source: ruby-in-parallel Source-Version: 0.1.17-1.3 Done: Utkarsh Gupta We believe that the bug you reported is fixed in the latest version of ruby-in-parallel, 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 980...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Utkarsh Gupta (supplier of updated ruby-in-parallel 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, 21 Jan 2021 12:57:41 +0530 Source: ruby-in-parallel Architecture: source Version: 0.1.17-1.3 Distribution: unstable Urgency: medium Maintainer: Freexian Packaging Team Changed-By: Utkarsh Gupta Closes: 980585 Changes: ruby-in-parallel (0.1.17-1.3) unstable; urgency=medium . * Non-maintainer upload. * Add patch to skip random test failure. (Closes: #980585) Checksums-Sha1: c4551c25313fe5e08be3bb48accd00b45a992a20 2117 ruby-in-parallel_0.1.17-1.3.dsc a7960e381659c0efd6fbaeb63544684a29364b8c 2616 ruby-in-parallel_0.1.17-1.3.debian.tar.xz 32db3e13397593bac379ba1592605c0effbae602 9587 ruby-in-parallel_0.1.17-1.3_amd64.buildinfo Checksums-Sha256: ac10f8e61960af1a820262b70247fd74e074fa2f272a0f72c52930f31cf90f3f 2117 ruby-in-parallel_0.1.17-1.3.dsc f993ebdcfcec07e9f24422601d173a888f12aa9cf83ece980a669a6fd3692bae 2616 ruby-in-parallel_0.1.17-1.3.debian.tar.xz a21a5d83555e1964e4d1ca9e99a4b66fc1cf5d36a05a2d4a1ad891241655c361 9587 ruby-in-parallel_0.1.17-1.3_amd64.buildinfo Files: 64064facc362fba7dcfc6c34dc2d1c14 2117 ruby optional ruby-in-parallel_0.1.17-1.3.dsc a23116463d859dc5cee5db066e214eb4 2616 r
Processed: forcibly merging 980526 980717
Processing commands for cont...@bugs.debian.org:
> forcemerge 980526 980717
Bug #980526 {Done: Emmanuel Bourg } [maven] maven: Update to
maven 3.6.3-2 drops dependency to libcommons-cli-java, renders package unusable
Bug #980717 [maven] kazocsaba-imageviewer FTBFS
Severity set to 'grave' from 'serious'
Marked Bug as done
Marked as fixed in versions maven/3.6.3-3.
Marked as found in versions maven/3.6.3-2.
Bug #980526 {Done: Emmanuel Bourg } [maven] maven: Update to
maven 3.6.3-2 drops dependency to libcommons-cli-java, renders package unusable
Added tag(s) ftbfs.
Merged 980526 980717
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
980526: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980526
980717: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980717
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: reassign 980717 to maven
Processing commands for cont...@bugs.debian.org: > reassign 980717 maven Bug #980717 [src:kazocsaba-imageviewer] kazocsaba-imageviewer FTBFS Bug reassigned from package 'src:kazocsaba-imageviewer' to 'maven'. No longer marked as found in versions kazocsaba-imageviewer/1.2.3-2. Ignoring request to alter fixed versions of bug #980717 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 980717: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980717 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#980658: pygame-sdl2: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2
On 20/01/21 at 23:05 +, Simon McVittie wrote: > On Wed, 20 Jan 2021 at 22:01:14 +0100, Lucas Nussbaum wrote: > > > dpkg-source -b . > > Are you deliberately rebuilding the source package? That seems unusual > for testing whether packages FTBFS... Yes, it's not that much additional effort and catches some problems such as the one below from time to time. Lucas
Bug#972134: chromium: please, consider moving the package to team-maintenance to properly maintain it
Hi, In that case what does it take to become a maintainer for this package? Are there any docs on how the build process works? Regards,Patrick On Wed, 20 Jan 2021 18:00:45 +0100 Salvatore Bonaccorso < car...@debian.org> wrote:> Hi,> > On Mon, Jan 11, 2021 at 05:23:50PM +0100, Michel Le Bihan wrote:> [...]> > The window for getting in Bullseye will close soon and this issue is> > blocking. Will you be able to maintain Chromium in Bullseye? I can help> > with it if needed.> > Thanks for you both which were involved in the last two rounds of> updates for chromium.> > To make it supportable in bullseye the problem is still that due to> the hight flux of issues which appear in chromium, one person (with> uploading permissions) commiting either as part of the team or> commiting to regularly sponsor uploads, would not be enought. As said> there is a high and frequent flux of issues appering, that means if we> only have one such person, and the person temporarily have to step> from chromium maintenance we run in the same situation as we right now> had for buster.> > For redundancy there should be at least a second person available up> for doing so. The task is quite time consuming and so cannot fall back> at some point due to need to the security team members.> > it can be for instance Mike Gilbert (as member of the team) and Mattia> (not part of it, but commiting to sponsoring) to make this sort of> commitment.> > Continuing including chromium in bullseye might be the most desirable> option indeed, but running in the situation where in the stable> release is sitting a old version, would be worse than not having it> and users for instance just installing it from flathub.> > Hope this clarifies enough the security team perspective.> > Regards,> Salvatore
Bug#980585: ruby-in-parallel: FTBFS: ERROR: Test "ruby2.7" failed: Failure/Error: expect(@result_3).to_not eq(true)
On Thu, Jan 21, 2021 at 12:50 PM Sébastien Delafond wrote: > I'm not expecting upstream to fix it either, but it'd feel more > comfortable to close this bug on our side while still linking to an > existing upstream issue. Of course. Here it is: https://github.com/samwoods1/in-parallel/issues/8 Feel free to add more if I missed something. > Ideally we'd only skip this test in 2.x, while keeping it in 3.0 to see > if same race eventually pops up on debci. Yeah, but I'd rather keep it disabled now and then re-work it when working on the interpreter transition. That said, I am preparing an upload for this as we speak! :) Best, Utkarsh
Bug#980585: ruby-in-parallel: FTBFS: ERROR: Test "ruby2.7" failed: Failure/Error: expect(@result_3).to_not eq(true)
On 21/01 12:46, Utkarsh Gupta wrote: > I can create an issue in the original fork. However, just know that > this library is *not* being maintained at all. So there won't be much > help from anywhere. I'm not expecting upstream to fix it either, but it'd feel more comfortable to close this bug on our side while still linking to an existing upstream issue. > Either way, I'd also like to mention that we did a build for > ruby-in-parallel against ruby3.0 and everything seems to work, > including those tests as well. Ideally we'd only skip this test in 2.x, while keeping it in 3.0 to see if same race eventually pops up on debci. Cheers, -- Seb
Processed (with 1 error): forcibly merging 980526 980717
Processing commands for cont...@bugs.debian.org:
> forcemerge 980526 980717
Bug #980526 {Done: Emmanuel Bourg } [maven] maven: Update to
maven 3.6.3-2 drops dependency to libcommons-cli-java, renders package unusable
Unable to merge bugs because:
package of #980717 is 'src:kazocsaba-imageviewer' not 'maven'
Failed to forcibly merge 980526: Did not alter merged bugs.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
980526: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980526
980717: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980717
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#980585: ruby-in-parallel: FTBFS: ERROR: Test "ruby2.7" failed: Failure/Error: expect(@result_3).to_not eq(true)
Hi Sébastien, On Thu, Jan 21, 2021 at 12:42 PM Sébastien Delafond wrote: > > Aah, okay. So I ran sbuild + autopkgtest 10 times, all passed for me. > > But when I ran these tests locally with rake, it failed for me exactly > > like the report just for the first time. And then passed all 9 times > > afterward. > > I haven't been able to reproduce it here: local rake, autopkgtest+lxc, > autopkgtest+qemu. Aah. > > Then I tried to trace back the origin of this problem but couldn't > > find anything. I am not sure what's causing this (I haven't gone > > through the source thoroughly) but I am inclined towards skipping this > > test if that's OK with you? > > It definitely looks like a race, so I agree we can skip it if we create > an upstream bug documenting the issue. I can create an issue in the original fork. However, just know that this library is *not* being maintained at all. So there won't be much help from anywhere. Either way, I'd also like to mention that we did a build for ruby-in-parallel against ruby3.0 and everything seems to work, including those tests as well. See logs here: https://people.debian.org/~kanashiro/ruby3.0/builds/3/ruby-in-parallel/ruby-in-parallel_0.1.17-1.1+rebuild1610557786_amd64-2021-01-13T17:09:48Z.build Best, Utkarsh
Bug#980585: ruby-in-parallel: FTBFS: ERROR: Test "ruby2.7" failed: Failure/Error: expect(@result_3).to_not eq(true)
On 21/01 12:31, Utkarsh Gupta wrote: > Aah, okay. So I ran sbuild + autopkgtest 10 times, all passed for me. > But when I ran these tests locally with rake, it failed for me exactly > like the report just for the first time. And then passed all 9 times > afterward. I haven't been able to reproduce it here: local rake, autopkgtest+lxc, autopkgtest+qemu. > Then I tried to trace back the origin of this problem but couldn't > find anything. I am not sure what's causing this (I haven't gone > through the source thoroughly) but I am inclined towards skipping this > test if that's OK with you? It definitely looks like a race, so I agree we can skip it if we create an upstream bug documenting the issue. Cheers, -- Seb
Bug#980585: ruby-in-parallel: FTBFS: ERROR: Test "ruby2.7" failed: Failure/Error: expect(@result_3).to_not eq(true)
Hi Sébastien, On Thu, Jan 21, 2021 at 11:51 AM Utkarsh Gupta wrote: > I've started to look into it already but I wasn't able to reproduce > it. All tests pass for me + autopkgtest (which is what I fixed last > time). So I am not sure what's going wrong here. Aah, okay. So I ran sbuild + autopkgtest 10 times, all passed for me. But when I ran these tests locally with rake, it failed for me exactly like the report just for the first time. And then passed all 9 times afterward. Then I tried to trace back the origin of this problem but couldn't find anything. I am not sure what's causing this (I haven't gone through the source thoroughly) but I am inclined towards skipping this test if that's OK with you? It'd be best if we fix it but I am not sure if it's worth a lot of time. Let me know what you think? Best, Utkarsh
Bug#980585: ruby-in-parallel: FTBFS: ERROR: Test "ruby2.7" failed: Failure/Error: expect(@result_3).to_not eq(true)
Hi Sébastien, On Thu, Jan 21, 2021 at 11:37 AM Sébastien Delafond wrote: > since you took care of the last upload, do you also plan to fix this > FTBFS? If not, please let me know and I'll look into it. I've started to look into it already but I wasn't able to reproduce it. All tests pass for me + autopkgtest (which is what I fixed last time). So I am not sure what's going wrong here. If you have some time and can take a look as well, that'd be really helpful. If you find something, let me know. - u
Bug#980672: marked as done (node-string-decoder: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1)
Your message dated Thu, 21 Jan 2021 06:04:19 +
with message-id
and subject line Bug#980672: fixed in node-string-decoder 1.3.0-2
has caused the Debian Bug report #980672,
regarding node-string-decoder: FTBFS: dh_auto_test: error: /bin/sh -ex
debian/tests/pkg-js/test returned exit code 1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
980672: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980672
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-string-decoder
Version: 1.3.0-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210120 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> dpkg-buildpackage
> -
>
> Command: dpkg-buildpackage -us -uc -sa -rfakeroot
> dpkg-buildpackage: info: source package node-string-decoder
> dpkg-buildpackage: info: source version 1.3.0-1
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Xavier Guimard
> dpkg-source --before-build .
> dpkg-buildpackage: info: host architecture amd64
> debian/rules clean
> dh clean --with nodejs
>dh_auto_clean --buildsystem=nodejs
> rm -rf ./node_modules/.cache
>dh_clean
> dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building node-string-decoder using existing
> ./node-string-decoder_1.3.0.orig.tar.gz
> dpkg-source: info: using patch list from debian/patches/series
> dpkg-source: info: building node-string-decoder in
> node-string-decoder_1.3.0-1.debian.tar.xz
> dpkg-source: info: building node-string-decoder in
> node-string-decoder_1.3.0-1.dsc
> debian/rules binary
> dh binary --with nodejs
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure --buildsystem=nodejs
>dh_auto_build --buildsystem=nodejs
> No build command found, searching known files
>dh_auto_test --buildsystem=nodejs
> mkdir -p node_modules
> ln -s ../. node_modules/string_decoder
> /bin/sh -ex debian/tests/pkg-js/test
> + tap -R spec test/parallel/test-string-decoder-end.js
> test/parallel/test-string-decoder.js test/ours/*.js
>
> internal/modules/cjs/loader.js:818
> throw err;
> ^
>
> Error: Cannot find module '@babel/polyfill'
> Require stack:
> - /<>/test/common/index.js
> - /<>/test/parallel/test-string-decoder-end.js
> at Function.Module._resolveFilename
> (internal/modules/cjs/loader.js:815:15)
> at Function.Module._load (internal/modules/cjs/loader.js:667:27)
> at Module.require (internal/modules/cjs/loader.js:887:19)
> at require (internal/modules/cjs/helpers.js:74:18)
> at Object. (/<>/test/common/index.js:6:1)
> at Module._compile (internal/modules/cjs/loader.js:999:30)
> at Object.Module._extensions..js (internal/modules/cjs/loader.js:1027:10)
> at Module.load (internal/modules/cjs/loader.js:863:32)
> at Function.Module._load (internal/modules/cjs/loader.js:708:14)
> at Module.require (internal/modules/cjs/loader.js:887:19) {
> code: 'MODULE_NOT_FOUND',
> requireStack: [
> '/<>/test/common/index.js',
> '/<>/test/parallel/test-string-decoder-end.js'
> ]
> }
> internal/modules/cjs/loader.js:818
> throw err;
> ^
>
> Error: Cannot find module '@babel/polyfill'
> Require stack:
> - /<>/test/common/index.js
> - /<>/test/parallel/test-string-decoder.js
> at Function.Module._resolveFilename
> (internal/modules/cjs/loader.js:815:15)
> at Function.Module._load (internal/modules/cjs/loader.js:667:27)
> at Module.require (internal/modules/cjs/loader.js:887:19)
> at require (internal/modules/cjs/helpers.js:74:18)
> at Object. (/<>/test/common/index.js:6:1)
> at Module._compile (internal/modules/cjs/loader.js:999:30)
> at Object.Module._extensions..js (internal/modules/cjs/loader.js:1027:10)
> at Module.load (internal/modules/cjs/loader.js:863:32)
> at Function.Module._load (internal/modules/cjs/loader.js:708:14)
> at Module.require (internal/modules/cjs/loader.js:887:19) {
> code: 'MODULE_NOT_FOUND',
> requireStack: [
> '/<>/test/common/index.js',
> '/<>/test/parallel/test-string-decoder.js'
> ]
Bug#980585: ruby-in-parallel: FTBFS: ERROR: Test "ruby2.7" failed: Failure/Error: expect(@result_3).to_not eq(true)
Hi Utkarsh, since you took care of the last upload, do you also plan to fix this FTBFS? If not, please let me know and I'll look into it. Cheers, -- Seb
Bug#980702: marked as done (node-nodemailer: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 3)
Your message dated Thu, 21 Jan 2021 05:48:33 + with message-id and subject line Bug#980702: fixed in node-nodemailer 6.4.17-2 has caused the Debian Bug report #980702, regarding node-nodemailer: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 3 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 980702: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980702 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-nodemailer Version: 6.4.17-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20210120 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > dpkg-buildpackage > - > > Command: dpkg-buildpackage -us -uc -sa -rfakeroot > dpkg-buildpackage: info: source package node-nodemailer > dpkg-buildpackage: info: source version 6.4.17-1 > dpkg-buildpackage: info: source distribution unstable > dpkg-buildpackage: info: source changed by Xavier Guimard > dpkg-source --before-build . > dpkg-buildpackage: info: host architecture amd64 > debian/rules clean > dh clean >dh_auto_clean --buildsystem=nodejs > rm -rf ./node_modules/.cache >dh_clean > dpkg-source -b . > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-source: info: building node-nodemailer using existing > ./node-nodemailer_6.4.17.orig.tar.gz > dpkg-source: info: building node-nodemailer in > node-nodemailer_6.4.17-1.debian.tar.xz > dpkg-source: info: building node-nodemailer in node-nodemailer_6.4.17-1.dsc > debian/rules binary > dh binary >dh_update_autotools_config >dh_autoreconf >dh_auto_configure --buildsystem=nodejs >dh_auto_build --buildsystem=nodejs > No build command found, searching known files > cd ./. && grunt > Can't exec "grunt": No such file or directory at > /usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line 522. > dh_auto_build: warning: ### Command "grunt" failed in . > > dh_auto_build: warning: > > 1 failures, unable to build automatically. > Install a debian/nodejs/./build or add a "override_dh_auto_build:" target > in debian/rules > > > dh_auto_build: warning: Aborting auto_build > > Command "grunt" succeeded in . >dh_auto_test --buildsystem=nodejs > mkdir -p node_modules > ln -s ../debian/tests/test_modules/libbase64 node_modules/libbase64 > ln -s ../debian/tests/test_modules/base32.js node_modules/base32.js > ln -s ../debian/tests/test_modules/libmime node_modules/libmime > ln -s ../debian/tests/test_modules/proxy-test-server > node_modules/proxy-test-server > ln -s ../debian/tests/test_modules/libqp node_modules/libqp > ln -s ../debian/tests/test_modules/safer-buffer > node_modules/safer-buffer > ln -s ../debian/tests/test_modules/proxy node_modules/proxy > ln -s ../debian/tests/test_modules/ipv6-normalize > node_modules/ipv6-normalize > ln -s ../debian/tests/test_modules/smtp-server node_modules/smtp-server > ln -s ../. node_modules/nodemailer > /bin/sh -ex debian/tests/pkg-js/test > + set -e > + ln -s .. node_modules/nodemailer > ln: failed to create symbolic link 'node_modules/nodemailer/..': File exists > + true > + mocha --timeout 5 test/addressparser/addressparser-test.js > test/base64/base64-test.js test/dkim/dkim-test.js > test/dkim/message-parser-test.js test/dkim/relaxed-body-test.js > test/dkim/sign-test.js test/fetch/cookies-test.js test/fetch/fetch-test.js > test/json-transport/json-transport-test.js > test/mail-composer/mail-composer-test.js test/mime-funcs/mime-funcs-test.js > test/mime-funcs/mime-types-test.js test/mime-node/mime-node-test.js > test/qp/qp-test.js test/sendmail/le-windows-test.js > test/sendmail/sendmail-test.js test/ses-transport/ses-transport-test.js > test/shared/shared-test.js test/smtp-connection/http-proxy-client-test.js > test/smtp-connection/smtp-connection-test.js test/smtp-pool/smtp-pool-test.js > test/smtp-transport/smtp-tranport-test.js > test/stream-transport/stream-transport-test.js > test/well-known/well-kn
Bug#980595: marked as done (arping: FTBFS: arping_test.c:239:8: error: ‘test_mkpacket’ redeclared as different kind of symbol)
Your message dated Thu, 21 Jan 2021 05:48:21 + with message-id and subject line Bug#980595: fixed in arping 2.21-2 has caused the Debian Bug report #980595, regarding arping: FTBFS: arping_test.c:239:8: error: ‘test_mkpacket’ redeclared as different kind of symbol 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.) -- 980595: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980595 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: arping Version: 2.21-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20210120 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 > -D_DEFAULT_SOURCE=1 -g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -c -o > arping_test.o arping_test.c > In file included from arping_test.c:29: > arping_test.c:239:8: error: ‘test_mkpacket’ redeclared as different kind of > symbol > 239 | MYTEST(test_mkpacket) > |^ > arping_test.c:239:1: note: in expansion of macro ‘MYTEST’ > 239 | MYTEST(test_mkpacket) > | ^~ > arping_test.c:239:8: note: previous declaration of ‘test_mkpacket’ was here > 239 | MYTEST(test_mkpacket) > |^ > arping_test.c:58:31: note: in definition of macro ‘MYTEST’ >58 | #define MYTEST(a) static void a(int);__attribute__((constructor)) \ > | ^ > In file included from arping_test.c:29: > arping_test.c:264:8: error: ‘pingip_uninteresting_packet’ redeclared as > different kind of symbol > 264 | MYTEST(pingip_uninteresting_packet) > |^~~ > arping_test.c:264:1: note: in expansion of macro ‘MYTEST’ > 264 | MYTEST(pingip_uninteresting_packet) > | ^~ > arping_test.c:264:8: note: previous declaration of > ‘pingip_uninteresting_packet’ was here > 264 | MYTEST(pingip_uninteresting_packet) > |^~~ > arping_test.c:58:31: note: in definition of macro ‘MYTEST’ >58 | #define MYTEST(a) static void a(int);__attribute__((constructor)) \ > | ^ > In file included from arping_test.c:29: > arping_test.c:392:8: error: ‘pingip_interesting_packet’ redeclared as > different kind of symbol > 392 | MYTEST(pingip_interesting_packet) > |^ > arping_test.c:392:1: note: in expansion of macro ‘MYTEST’ > 392 | MYTEST(pingip_interesting_packet) > | ^~ > arping_test.c:392:8: note: previous declaration of > ‘pingip_interesting_packet’ was here > 392 | MYTEST(pingip_interesting_packet) > |^ > arping_test.c:58:31: note: in definition of macro ‘MYTEST’ >58 | #define MYTEST(a) static void a(int);__attribute__((constructor)) \ > | ^ > In file included from arping_test.c:29: > arping_test.c: In function ‘pingip_interesting_packet_fn’: > arping_test.c:445:21: warning: too many arguments for format > [-Wformat-extra-args] > 445 | "numrecvd not incremented"); > | ^~ > arping_test.c:449:21: warning: too many arguments for format > [-Wformat-extra-args] > 449 | "numrecvd not incremented second time"); > | ^~ > arping_test.c: At top level: > arping_test.c:452:8: error: ‘strip_newline_test’ redeclared as different kind > of symbol > 452 | MYTEST(strip_newline_test) > |^~ > arping_test.c:452:1: note: in expansion of macro ‘MYTEST’ > 452 | MYTEST(strip_newline_test) > | ^~ > arping_test.c:452:8: note: previous declaration of ‘strip_newline_test’ was > here > 452 | MYTEST(strip_newline_test) > |^~ > arping_test.c:58:31: note: in definition of macro ‘MYTEST’ >58 | #define MYTEST(a) static void a(int);__attribute__((constructor)) \ > | ^ > In file included from arping_test.c:29: > arping_test.c:472:8: error: ‘get_mac_addr_success’ redeclared as different > kind of symbol > 472 |
Processed: Bug#980672 marked as pending in node-string-decoder
Processing control commands: > tag -1 pending Bug #980672 [src:node-string-decoder] node-string-decoder: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1 Added tag(s) pending. -- 980672: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980672 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#980672: marked as pending in node-string-decoder
Control: tag -1 pending Hello, Bug #980672 in node-string-decoder reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-string-decoder/-/commit/cf598cc32d865c2025dc64a6b63dfc92f7ea22c2 Update babel7 patch Closes: #980672 (this message was generated automatically) -- Greetings https://bugs.debian.org/980672
Bug#980690: marked as pending in node-readable-stream
Control: tag -1 pending Hello, Bug #980690 in node-readable-stream reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-readable-stream/-/commit/13ce86038479eda2493ff111013ed96ce503ef87 Fix test Closes: #980690 (this message was generated automatically) -- Greetings https://bugs.debian.org/980690
Processed: Bug#980690 marked as pending in node-readable-stream
Processing control commands: > tag -1 pending Bug #980690 [src:node-readable-stream] node-readable-stream: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1 Added tag(s) pending. -- 980690: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980690 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#980702 marked as pending in node-nodemailer
Processing control commands: > tag -1 pending Bug #980702 [src:node-nodemailer] node-nodemailer: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 3 Added tag(s) pending. -- 980702: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980702 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#980702: marked as pending in node-nodemailer
Control: tag -1 pending Hello, Bug #980702 in node-nodemailer reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-nodemailer/-/commit/787b67c9d639e0ff97fc8dcf754c2f5536a693fb Ignore cookie test Closes: #980702 (this message was generated automatically) -- Greetings https://bugs.debian.org/980702
Processed: Bug#980595 marked as pending in arping
Processing control commands: > tag -1 pending Bug #980595 [src:arping] arping: FTBFS: arping_test.c:239:8: error: ‘test_mkpacket’ redeclared as different kind of symbol Added tag(s) pending. -- 980595: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980595 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#980595: marked as pending in arping
Control: tag -1 pending Hello, Bug #980595 in arping reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/debian/arping/-/commit/fc1e7c5fa6ca636e381d4e15b50f2df13a21588b unit tests: Remove test registry code in favour of code duplication Closes: #980595 (this message was generated automatically) -- Greetings https://bugs.debian.org/980595
Bug#980595: libcheck made a breaking change
Hi, On Wed, Jan 20, 2021 at 10:23:30PM +, Thomas Habets wrote: > libcheck made a breaking change. > Patch for arping to make it build: > https://github.com/ThomasHabets/arping/commit/e0773bc26ae14d4a19825023307d1496d7c7d0f1 > > I aim to release 2.22 tomorrow with this change. > But there are no changes between 2.21 and 2.22, so you can just patch in > the commit, if you prefer. Thanks! > I see the tag is set to "serious". To be clear this is a failure of the > TEST to compile only. I agree that this should be seen as serious, but it's > just the test. I do agree, in context of Debian policy though serious is warranted as it makes the package fail to build. But yes, if there would not have a quick solution, and known that it is only the test which is broken, then we could not run the testsuite as workaround and fixing the issue. In any case, thanks for your fast bugfix, amazing :) Regards, Salvatore
Bug#980648: marked as done (node-execa: FTBFS: dh_auto_test: error: cd ./human-signals && sh -ex ../debian/nodejs/human-signals/test returned exit code 1)
Your message dated Thu, 21 Jan 2021 05:18:22 +
with message-id
and subject line Bug#980648: fixed in node-execa 4.1.0+dfsg+~cs19.3.6-5
has caused the Debian Bug report #980648,
regarding node-execa: FTBFS: dh_auto_test: error: cd ./human-signals && sh -ex
../debian/nodejs/human-signals/test returned exit code 1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
980648: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980648
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-execa
Version: 4.1.0+dfsg+~cs19.3.6-4
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210120 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> echo 'int main() { return 0; }' | gcc -x c -o test/fixtures/fast-exit-linux -
> dh_auto_build --buildsystem=nodejs
> No build command found, searching known files
> Found debian/nodejs/human-signals/build
> cd ./human-signals && sh -ex ../debian/nodejs/human-signals/build
> + babeljs -d build/src --presets=@babel/preset-env src/
> Successfully compiled 4 files with Babel (685ms).
> No build command found, searching known files
> No build command found, searching known files
> No build command found, searching known files
> No build command found, searching known files
> make[1]: Leaving directory '/<>'
>dh_auto_test --buildsystem=nodejs
> ln -s ../debian/tests/test_modules/test-each node_modules/test-each
> ln -s ../debian/tests/test_modules/big-cartesian
> node_modules/big-cartesian
> ln -s ../. node_modules/execa
> cd ./human-signals && sh -ex ../debian/nodejs/human-signals/test
> + jest --ci --testRegex test/main.js
> FAIL test/main.js
> ● Test suite failed to run
>
> Cannot find module 'ajv' from 'test/main.js'
>
> 235 |
> 236 | const relativePath = (0,
> _slash().default)(path().relative(this._options.rootDir, from)) || '.';
> > 237 | throw new _ModuleNotFoundError.default(`Cannot find module
> '${moduleName}' from '${relativePath}'`, moduleName);
> | ^
> 238 | }
> 239 |
> 240 | _isAliasModule(moduleName) {
>
> at Resolver.resolveModule
> (../../../../usr/share/nodejs/jest-resolve/build/index.js:237:11)
> at Object. (test/main.js:4:1)
>
> Test Suites: 1 failed, 1 total
> Tests: 0 total
> Snapshots: 0 total
> Time:1.746 s
> Ran all test suites.
> dh_auto_test: error: cd ./human-signals && sh -ex
> ../debian/nodejs/human-signals/test returned exit code 1
The full build log is available from:
http://qa-logs.debian.net/2021/01/20/node-execa_4.1.0+dfsg+~cs19.3.6-4_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with me
so that we can identify if something relevant changed in the meantime.
About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: node-execa
Source-Version: 4.1.0+dfsg+~cs19.3.6-5
Done: Xavier Guimard
We believe that the bug you reported is fixed in the latest version of
node-execa, 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 980...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Xavier Guimard (supplier of updated node-execa 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, 21 Jan 2021 06:01:35 +0100
Source: node-execa
Architecture:
Bug#957055: bristol: ftbfs with GCC-10
Control: tags -1 patch
Hi,
In Ubuntu, the attached patch was applied to achieve the following:
* d/p/04-gcc_10.patch: Fix FTBFS with GCC 10 by adjusting some variables.
Thanks for considering the patch.
Logan
diff -Nru bristol-0.60.11/debian/patches/04-gcc_10.patch
bristol-0.60.11/debian/patches/04-gcc_10.patch
--- bristol-0.60.11/debian/patches/04-gcc_10.patch 1969-12-31
19:00:00.0 -0500
+++ bristol-0.60.11/debian/patches/04-gcc_10.patch 2021-01-20
22:48:15.0 -0500
@@ -0,0 +1,243 @@
+--- a/brighton/brightonCLI.c
b/brighton/brightonCLI.c
+@@ -136,7 +136,6 @@
+ //if (RESOURCES->resources[btty.p].devlocn[btty.i].to == 1.0f)
+ //if (DEVICE(btty.i).to == 1.0f)
+
+-brightonEvent event;
+ extern void printBrightonHelp(int);
+
+ typedef int (*clicom)();
+--- a/brighton/brightonMixerMenu.c
b/brighton/brightonMixerMenu.c
+@@ -1179,11 +1179,10 @@
+ return(NULL);
+ }
+
+-brightonEvent event;
+-
+ int
+ doAlarm()
+ {
++ brightonEvent event;
+ event.type = BRIGHTON_FLOAT;
+ event.value = 0.0;
+
+--- a/include/bristol/bristolblo.h
b/include/bristol/bristolblo.h
+@@ -39,7 +39,7 @@
+ #define BLO_COSINE6
+ #define BLO_PULSE 7
+
+-struct {
++struct blo {
+ int flags;
+ int harmonics;
+ int cutin;
+@@ -47,7 +47,8 @@
+ int min;
+ float fraction;
+ float samplerate;
+-} blo;
++};
++extern struct blo blo;
+
+ extern float blosine[BRISTOL_BLO_SIZE];
+ extern float blosquare[BRISTOL_BLO_SIZE];
+--- a/bristol/blo.c
b/bristol/blo.c
+@@ -33,6 +33,8 @@
+
+ static int init = 1;
+
++struct blo blo;
++
+ float blosine[BRISTOL_BLO_SIZE];
+ float blocosine[BRISTOL_BLO_SIZE];
+ float blosquare[BRISTOL_BLO_SIZE];
+--- a/bristol/arpdco.c
b/bristol/arpdco.c
+@@ -39,7 +39,8 @@
+ #include "bristolblo.h"
+ #include "arpdco.h"
+
+-float note_diff, *zbuf;
++static float note_diff;
++float *zbuf;
+
+ #define BRISTOL_SQR 4
+
+--- a/bristol/cs80osc.c
b/bristol/cs80osc.c
+@@ -41,8 +41,8 @@
+ #include "cs80osc.h"
+ #include "bristolcs80.h"
+
+-float note_diff;
+-int samplecount;
++static float note_diff;
++static int samplecount;
+
+ static void fillWave(float *, int, int);
+ static void buildCs80Sound(bristolOP *, bristolOPParams *);
+--- a/bristol/dco.c
b/bristol/dco.c
+@@ -39,7 +39,7 @@
+ #include "bristolblo.h"
+ #include "dco.h"
+
+-float note_diff;
++static float note_diff;
+
+ /*
+ * The name of this operator, IO count, and IO names.
+--- a/bristol/expdco.c
b/bristol/expdco.c
+@@ -40,7 +40,7 @@
+ #include "bristolblo.h"
+ #include "expdco.h"
+
+-float note_diff;
++static float note_diff;
+
+ /*
+ * The name of this operator, IO count, and IO names.
+--- a/bristol/filter2.c
b/bristol/filter2.c
+@@ -147,7 +147,6 @@
+ }
+
+ #define ROOT2 1.4142135623730950488
+-double pidsr;
+
+ /*
+ * Reset any local memory information.
+--- a/bristol/granulardco.c
b/bristol/granulardco.c
+@@ -38,8 +38,8 @@
+ #include "bristol.h"
+ #include "granulardco.h"
+
+-float note_diff;
+-float samplerate;
++static float note_diff;
++static float samplerate;
+
+ #define BRISTOL_SQR 4
+
+--- a/bristol/hammond.c
b/bristol/hammond.c
+@@ -45,8 +45,8 @@
+ #include "bristol.h"
+ #include "hammond.h"
+
+-float note_diff;
+-int samplecount;
++static float note_diff;
++static int samplecount;
+
+ static void fillWave(float *, int, int);
+ static void buildHammondSound(bristolOP *, unsigned char);
+@@ -70,8 +70,8 @@
+ static int *waveindex;
+ static int *percussion;
+
+-float *wave1;
+-float *wave2;
++static float *wave1;
++static float *wave2;
+
+ /*
+ * This can be a single list, it is used to generate the different pipes.
+--- a/bristol/junodco.c
b/bristol/junodco.c
+@@ -39,7 +39,7 @@
+ #include "bristolblo.h"
+ #include "junodco.h"
+
+-float note_diff;
++static float note_diff;
+
+ #define BRISTOL_SQR 8
+
+--- a/bristol/lfo.c
b/bristol/lfo.c
+@@ -38,7 +38,7 @@
+ #include "bristol.h"
+ #include "lfo.h"
+
+-float note_diff;
++static float note_diff;
+
+ /*
+ * The name of this operator, IO count, and IO names.
+--- a/bristol/midihandlers.c
b/bristol/midihandlers.c
+@@ -633,7 +633,7 @@
+ *previous frequency * (2^^(1/12))
+ * Since A is constand whole numbers we can calcuate each octave from A.
+ */
+-float samplerate;
++static float samplerate;
+
+ int
+ initFrequencyTable(float rate)
+--- a/bristol/prophetdco.c
b/bristol/prophetdco.c
+@@ -47,7 +47,7 @@
+ #include "bristolblo.h"
+ #include "prophetdco.h"
+
+-float note_diff;
++static float note_diff;
+
+ #define BRISTOL_SQR 4
+
+--- a/bristol/sdco.c
b/bristol/sdco.c
+@@ -41,7 +41,7 @@
+ #include "bristol.h"
+ #include "sdco.h"
+
+-float note_diff;
++static float note_diff;
+
+ /*
+ * The name of this operator, IO count, and IO names.
+--- a/bristol/trilogyosc.c
b/bristol/trilogyosc.c
+@@ -40,8 +40,8 @@
+ #include "bristolblo.h"
+ #include "trilogyosc.h"
+
+-float note_diff;
+-int
Processed: Re: bristol: ftbfs with GCC-10
Processing control commands: > tags -1 patch Bug #957055 [src:bristol] bristol: ftbfs with GCC-10 Added tag(s) patch. -- 957055: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957055 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#980601: [Debian-on-mobile-maintainers] Bug#980601: Bug#980601: chatty: FTBFS: phonenumber.pb.h:47:51: error: ‘AuxiliaryParseTableField’ in namespace ‘google::protobuf::internal’ does not name a ty
On 1/21/21 4:00 AM, Evangelos Ribeiro Tzaras wrote: Hi, On 1/20/21 9:25 PM, Lucas Nussbaum wrote: Source: chatty Version: 0.2.0-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20210120 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. thanks for your report! Relevant part (hopefully): c++ -Isrc/libchatty.so.p -Isrc -I../src -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/gio-unix-2.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/fribidi -I/usr/include/harfbuzz -I/usr/include/atk-1.0 -I/usr/include/pixman-1 -I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpurple -I/usr/include/libhandy-1 -I/usr/include/evolution-data-server -I/usr/include/nss -I/usr/include/nspr -I/usr/include/libsecret-1 -I/usr/include/libsoup-2.4 -I/usr/include/libxml2 -I/usr/include/gsettings-desktop-schemas -I/usr/include/libfeedback-0.0 -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wnon-virtual-dtor -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -MD -MQ src/libchatty.so.p/chatty-phone-utils.cpp.o -MF src/libchatty.so.p/chatty-phone-utils.cpp.o.d -o src/libchatty.so.p/chatty-phone-utils.cpp.o -c ../src/chatty-phone-utils.cpp In file included from /usr/include/phonenumbers/phonenumberutil.h:34, from ../src/chatty-phone-utils.cpp:18: /usr/include/phonenumbers/phonenumber.pb.h:47:51: error: ‘AuxiliaryParseTableField’ in namespace ‘google::protobuf::internal’ does not name a type; did you mean ‘AuxillaryParseTableField’? 47 | static const ::PROTOBUF_NAMESPACE_ID::internal::AuxiliaryParseTableField aux[] | ^~~~ | AuxillaryParseTableField In file included from /usr/include/phonenumbers/phonenumberutil.h:34, from ../src/chatty-phone-utils.cpp:18: /usr/include/phonenumbers/phonenumber.pb.h:88:30: error: ‘ConstStringParam’ is not a member of ‘google::protobuf’ 88 | ::PROTOBUF_NAMESPACE_ID::ConstStringParam name, PhoneNumber_CountryCodeSource* value); | ^~~~ /usr/include/phonenumbers/phonenumber.pb.h:88:82: error: expected primary-expression before ‘*’ token 88 | ::PROTOBUF_NAMESPACE_ID::ConstStringParam name, PhoneNumber_CountryCodeSource* value); | ^ /usr/include/phonenumbers/phonenumber.pb.h:88:84: error: ‘value’ was not declared in this scope 88 | ::PROTOBUF_NAMESPACE_ID::ConstStringParam name, PhoneNumber_CountryCodeSource* value); | ^ /usr/include/phonenumbers/phonenumber.pb.h:88:89: error: expression list treated as compound expression in initializer [-fpermissive] 88 | ::PROTOBUF_NAMESPACE_ID::ConstStringParam name, PhoneNumber_CountryCodeSource* value); | ^ /usr/include/phonenumbers/phonenumber.pb.h:218:71: error: ‘google::protobuf::ConstStringParam’ has not been declared 218 | static inline bool CountryCodeSource_Parse(::PROTOBUF_NAMESPACE_ID::ConstStringParam name, | ^~~~ /usr/include/phonenumbers/phonenumber.pb.h: In static member function ‘static bool i18n::phonenumbers::PhoneNumber::CountryCodeSource_Parse(int, i18n::phonenumbers::PhoneNumber::CountryCodeSource*)’: /usr/include/phonenumbers/phonenumber.pb.h:220:59: error: ‘i18n::phonenumbers::PhoneNumber_CountryCodeSource_Parse’ cannot be used as a function 220 | return PhoneNumber_CountryCodeSource_Parse(name, value); | ^ [36/65] cc -Isrc/chatty.p -Isrc -I../src -I../src/xeps/prpl/jabber -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/gio-unix-2.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/fribidi -I/usr/include/harfbuzz -I/usr/include/atk-1.0 -I/usr/include/pixman-1 -I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/gdk-
Bug#980434: Boot failure triggered by USB on rockpro64-rk3399 and pinebook-pro-rk3399
Hi Vagrant, Do you know which version is the last version that works in this case? The firmware is from eMMC and it's wired for USB to affect the boot process. Thanks, - Kever On 2021/1/21 上午8:08, Vagrant Cascadian wrote: It seems rockpro64-rk3399 and pinebook-pro-rk3399 fail to boot when usb is started. It hangs indefinitely at: ## Flattened Device Tree blob at 01f0 Booting using the fdt blob at 0x1f0 I have observed this also using 2020.10 on rockpro64-rk3399, though on pinebook-pro-rk3399 usb does not work and so it basically avoids triggering the issue. Setting CONFIG_USE_PREBOOT=n in the config works around the problem, though obviously by breaking usb keyboard support or booting from USB devices. Related bugs in Debian and manjaro: https://bugs.debian.org/973323 https://bugs.debian.org/980434 https://gitlab.manjaro.org/manjaro-arm/packages/core/uboot-rockpro64/-/issues/4 Boot log: U-Boot 2021.01+dfsg-1 (Jan 17 2021 - 03:50:13 +) SoC: Rockchip rk3399 Reset cause: POR Model: Pine64 RockPro64 v2.1 DRAM: 3.9 GiB PMIC: RK808 MMC: mmc@fe31: 2, mmc@fe32: 1, sdhci@fe33: 0 Loading Environment from SPIFlash... SF: Detected gd25q128 with page size 256 Bytes, erase size 4 KiB, total 16 MiB *** Warning - bad CRC, using default environment In:serial Out: serial Err: serial Model: Pine64 RockPro64 v2.1 Net: eth0: ethernet@fe30 starting USB... Bus usb@fe38: USB EHCI 1.00 Bus usb@fe3a: USB OHCI 1.0 Bus usb@fe3c: USB EHCI 1.00 Bus usb@fe3e: USB OHCI 1.0 Bus dwc3: usb maximum-speed not found Register 2000140 NbrPorts 2 Starting the controller USB XHCI 1.10 scanning bus usb@fe38 for devices... 1 USB Device(s) found scanning bus usb@fe3a for devices... 1 USB Device(s) found scanning bus usb@fe3c for devices... 1 USB Device(s) found scanning bus usb@fe3e for devices... 1 USB Device(s) found scanning bus dwc3 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Hit any key to stop autoboot: 0 => printenv preboot preboot=usb start => usb reset resetting USB... Bus usb@fe38: USB EHCI 1.00 Bus usb@fe3a: USB OHCI 1.0 Bus usb@fe3c: USB EHCI 1.00 Bus usb@fe3e: USB OHCI 1.0 Bus dwc3: usb maximum-speed not found Register 2000140 NbrPorts 2 Starting the controller USB XHCI 1.10 scanning bus usb@fe38 for devices... 1 USB Device(s) found scanning bus usb@fe3a for devices... 1 USB Device(s) found scanning bus usb@fe3c for devices... 1 USB Device(s) found scanning bus usb@fe3e for devices... 1 USB Device(s) found scanning bus dwc3 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found => boot Card did not respond to voltage select! : -110 switch to partitions #0, OK mmc1 is current device Scanning mmc 1:1... Found /extlinux/extlinux.conf Retrieving file: /extlinux/extlinux.conf 144 bytes read in 5 ms (27.3 KiB/s) 1: Debian-Installer Retrieving file: /initrd.gz 28995285 bytes read in 1287 ms (21.5 MiB/s) Retrieving file: /vmlinuz 26922864 bytes read in 1195 ms (21.5 MiB/s) Retrieving file: /dtbs/rockchip/rk3399-rockpro64.dtb 56849 bytes read in 13 ms (4.2 MiB/s) Moving Image from 0x208 to 0x220, end=3c5 ## Flattened Device Tree blob at 01f0 Booting using the fdt blob at 0x1f0 live well, vagrant
Processed: Re: cde: ftbfs with GCC-10
Processing control commands: > tags -1 patch Bug #957070 [src:cde] cde: ftbfs with GCC-10 Added tag(s) patch. -- 957070: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957070 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#957070: cde: ftbfs with GCC-10
Control: tags -1 patch Hi, In Ubuntu, the attached patch was applied to achieve the following: * d/p/gcc_10: Mark variables as extern to fix FTBFS with GCC 10. Thanks for considering the patch. Logan diff -Nru cde-0.1+git9-g551e54d/debian/patches/gcc_10 cde-0.1+git9-g551e54d/debian/patches/gcc_10 --- cde-0.1+git9-g551e54d/debian/patches/gcc_10 1969-12-31 19:00:00.0 -0500 +++ cde-0.1+git9-g551e54d/debian/patches/gcc_10 2021-01-20 22:27:38.0 -0500 @@ -0,0 +1,24 @@ +--- a/strace-4.6/defs.h b/strace-4.6/defs.h +@@ -34,8 +34,8 @@ + #define CDE_OPTIONS_VERSION_NUM "# cde.options v1" + #define CDE_ROOT_NAME "cde-root" + // pgbovine - these are both ABSOLUTE paths +-char* CDE_PACKAGE_DIR; +-char* CDE_ROOT_DIR; ++extern char* CDE_PACKAGE_DIR; ++extern char* CDE_ROOT_DIR; + + + #ifdef HAVE_CONFIG_H +--- a/readelf-mini/dwarf.c b/readelf-mini/dwarf.c +@@ -61,7 +61,7 @@ + int do_debug_macinfo; + int do_debug_str; + int do_debug_loc; +-int do_wide; ++extern int do_wide; + + /* Values for do_debug_lines. */ + #define FLAG_DEBUG_LINES_RAW 1 diff -Nru cde-0.1+git9-g551e54d/debian/patches/series cde-0.1+git9-g551e54d/debian/patches/series --- cde-0.1+git9-g551e54d/debian/patches/series 2013-11-17 20:49:30.0 -0500 +++ cde-0.1+git9-g551e54d/debian/patches/series 2021-01-20 22:27:16.0 -0500 @@ -1,2 +1,3 @@ up_ignore-noMakefile_on_clean deb_install_usr +gcc_10
Bug#980601: [Debian-on-mobile-maintainers] Bug#980601: chatty: FTBFS: phonenumber.pb.h:47:51: error: ‘AuxiliaryParseTableField’ in namespace ‘google::protobuf::internal’ does not name a type; did you
Hi, On 1/20/21 9:25 PM, Lucas Nussbaum wrote: Source: chatty Version: 0.2.0-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20210120 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. thanks for your report! Relevant part (hopefully): c++ -Isrc/libchatty.so.p -Isrc -I../src -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/gio-unix-2.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/fribidi -I/usr/include/harfbuzz -I/usr/include/atk-1.0 -I/usr/include/pixman-1 -I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpurple -I/usr/include/libhandy-1 -I/usr/include/evolution-data-server -I/usr/include/nss -I/usr/include/nspr -I/usr/include/libsecret-1 -I/usr/include/libsoup-2.4 -I/usr/include/libxml2 -I/usr/include/gsettings-desktop-schemas -I/usr/include/libfeedback-0.0 -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wnon-virtual-dtor -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -MD -MQ src/libchatty.so.p/chatty-phone-utils.cpp.o -MF src/libchatty.so.p/chatty-phone-utils.cpp.o.d -o src/libchatty.so.p/chatty-phone-utils.cpp.o -c ../src/chatty-phone-utils.cpp In file included from /usr/include/phonenumbers/phonenumberutil.h:34, from ../src/chatty-phone-utils.cpp:18: /usr/include/phonenumbers/phonenumber.pb.h:47:51: error: ‘AuxiliaryParseTableField’ in namespace ‘google::protobuf::internal’ does not name a type; did you mean ‘AuxillaryParseTableField’? 47 | static const ::PROTOBUF_NAMESPACE_ID::internal::AuxiliaryParseTableField aux[] | ^~~~ | AuxillaryParseTableField In file included from /usr/include/phonenumbers/phonenumberutil.h:34, from ../src/chatty-phone-utils.cpp:18: /usr/include/phonenumbers/phonenumber.pb.h:88:30: error: ‘ConstStringParam’ is not a member of ‘google::protobuf’ 88 | ::PROTOBUF_NAMESPACE_ID::ConstStringParam name, PhoneNumber_CountryCodeSource* value); | ^~~~ /usr/include/phonenumbers/phonenumber.pb.h:88:82: error: expected primary-expression before ‘*’ token 88 | ::PROTOBUF_NAMESPACE_ID::ConstStringParam name, PhoneNumber_CountryCodeSource* value); | ^ /usr/include/phonenumbers/phonenumber.pb.h:88:84: error: ‘value’ was not declared in this scope 88 | ::PROTOBUF_NAMESPACE_ID::ConstStringParam name, PhoneNumber_CountryCodeSource* value); | ^ /usr/include/phonenumbers/phonenumber.pb.h:88:89: error: expression list treated as compound expression in initializer [-fpermissive] 88 | ::PROTOBUF_NAMESPACE_ID::ConstStringParam name, PhoneNumber_CountryCodeSource* value); | ^ /usr/include/phonenumbers/phonenumber.pb.h:218:71: error: ‘google::protobuf::ConstStringParam’ has not been declared 218 | static inline bool CountryCodeSource_Parse(::PROTOBUF_NAMESPACE_ID::ConstStringParam name, | ^~~~ /usr/include/phonenumbers/phonenumber.pb.h: In static member function ‘static bool i18n::phonenumbers::PhoneNumber::CountryCodeSource_Parse(int, i18n::phonenumbers::PhoneNumber::CountryCodeSource*)’: /usr/include/phonenumbers/phonenumber.pb.h:220:59: error: ‘i18n::phonenumbers::PhoneNumber_CountryCodeSource_Parse’ cannot be used as a function 220 | return PhoneNumber_CountryCodeSource_Parse(name, value); | ^ [36/65] cc -Isrc/chatty.p -Isrc -I../src -I../src/xeps/prpl/jabber -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/gio-unix-2.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/fribidi -I/usr/include/harfbuzz -I/usr/include/atk-1.0 -I/usr/include/pixman-1 -I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpurple -I/usr/include/libhandy-1 -I/usr/i
Bug#980554: lutris: Crash on first when opening ~/.local/share/lutris/runtime/dxvk/dxvk_versions.json
I have a suspicion, which is that this is due to the Lutris Runtime missing. Did you have an internet connection when you launched it the first time? I'll try it on a live image tomorrow as well. Regards Stephan
Bug#980651: quaternion: FTBFS: dh_auto_configure: error: cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATE
On Wed, 20 Jan 2021 21:48:37 +0100, Lucas Nussbaum said: > During a rebuild of all packages in sid, your package failed to build > on amd64. This was due to the new libquotient package erroneously creating a libqmatrixclient-dev binary package. The latest libquotient package does not do this, but the bad binary package still remains. But I will be uploading a new version of quaternion soon, which will use libquotient instead of libqmatrixclient, so this will be fixed then. -- Hubert Chathi -- https://www.uhoreg.ca/ Jabber: hub...@uhoreg.ca -- Matrix: @uhoreg:matrix.org PGP/GnuPG key: 4096R/F24C F749 6C73 DDB8 DCB8 72DE B2DE 88D3 113A 1368
Bug#919348: many new releases since -- still "too buggy"?
Hi! Since your last report of a crash, there's been six new releases: five in the 0.1.* version series, and now one 4.16.0-1. As the new version claims a stable release, is there still a reason to keep xfce4-screensaver out of Bullseye? I've been using it happily all the time, with no borkage to report. Meow! -- ⢀⣴⠾⠻⢶⣦⠀ .--[ Makefile ] ⣾⠁⢠⠒⠀⣿⡁ # beware of races ⢿⡄⠘⠷⠚⠋⠀ all: pillage burn ⠈⠳⣄ `
Bug#980629: nheko: FTBFS: internal compiler error
On Wed, 20 Jan 2021 21:42:22 +0100, Lucas Nussbaum said:
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
This version of nheko was just rebuilt 18 days ago as a binNMU.
https://buildd.debian.org/status/fetch.php?pkg=nheko=amd64=0.7.2-3%2Bb1=1609589163=0
That build used gcc-10_10.2.1-3 instead of gcc-10_10.2.1-6. Given that
the package was built successfully so recently, I suspect that there is
a bug elsewhere, but aside from blindly reassigning this bug to gcc-10
and crossing my fingers, I'm not sure what's the best way to proceed.
But I've Cc'ed doko, as gcc maintainer, on this email.
Coincidentally, I uploaded nheko 0.8.0 today, and it also failed in the
same spot (/usr/include/tweeny/easingresolve.h:62:27). In fact, I
thought that this bug was about the newly-uploaded package, until I
looked more closely at it. ;) It succeeded to build on my own machine,
which was using an older version of gcc (9.3.0, apparently).
> Relevant part (hopefully):
[...trim...]
>> [ 49%] Building CXX object CMakeFiles/nheko.dir/src/ui/Ripple.cpp.o
>> /usr/bin/c++ -DBOOST_ALL_NO_LIB -DBOOST_ATOMIC_DYN_LINK
> -DBOOST_IOSTREAMS_DYN_LINK -DBOOST_SYSTEM_DYN_LINK
> -DBOOST_THREAD_DYN_LINK -DFMT_LOCALE -DFMT_SHARED
> -DJSON_USE_IMPLICIT_CONVERSIONS=1 -DQAPPLICATION_CLASS=QApplication
> -DQT_CONCURRENT_LIB -DQT_CORE_LIB -DQT_DBUS_LIB -DQT_GUI_LIB
> -DQT_MULTIMEDIA_LIB -DQT_NETWORK_LIB -DQT_NO_DEBUG -DQT_QMLMODELS_LIB
> -DQT_QML_LIB -DQT_QUICKCONTROLS2_LIB -DQT_QUICKWIDGETS_LIB
> -DQT_QUICK_LIB -DQT_SVG_LIB -DQT_WIDGETS_LIB -DSPDLOG_COMPILED_LIB
> -DSPDLOG_FMT_EXTERNAL -DSPDLOG_SHARED_LIB -I/<>/build
> -I/<> -I/<>/src -I/<>/includes
> -I/<>/third_party/blurhash
> -I/<>/third_party/cpp-httplib-0.5.12
> -I/usr/include/tweeny
> -I/<>/third_party/SingleApplication-3.1.3.1 -isystem
> /usr/include/x86_64-linux-gnu/qt5 -isystem
> /usr/include/x86_64-linux-gnu/qt5/QtDBus -isystem
> /usr/include/x86_64-linux-gnu/qt5/QtCore -isystem
> /usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -isystem
> /<>/mtxclient/include -isystem
> /usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem
> /usr/include/x86_64-linux-gnu/qt5/QtGui -isystem
> /usr/include/x86_64-linux-gnu/qt5/QtSvg -isystem
> /usr/include/x86_64-linux-gnu/qt5/QtConcurrent -isystem
> /usr/include/x86_64-linux-gnu/qt5/QtMultimedia -isystem
> /usr/include/x86_64-linux-gnu/qt5/QtNetwork -isystem
> /usr/include/x86_64-linux-gnu/qt5/QtQml -isystem
> /usr/include/x86_64-linux-gnu/qt5/QtQuickControls2 -isystem
> /usr/include/x86_64-linux-gnu/qt5/QtQuick -isystem
> /usr/include/x86_64-linux-gnu/qt5/QtQmlModels -isystem
> /usr/include/x86_64-linux-gnu/qt5/QtQuickWidgets -g -O2
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wdate-time
> -D_FORTIFY_SOURCE=2 -Wall -Wextra -pipe -pedantic -fsized-deallocation
> -fdiagnostics-color=always -Wunreachable-code -std=c++17 -O2 -g
> -DNDEBUG -fPIE -fPIC -pthread -std=gnu++17 -Winvalid-pch -include
> /<>/build/CMakeFiles/nheko.dir/cmake_pch.hxx -o
> CMakeFiles/nheko.dir/src/ui/Ripple.cpp.o -c
> /<>/src/ui/Ripple.cpp
>> In file included from /usr/include/tweeny/tween.h:595, from
>> /usr/include/tweeny/tweeny.h:81, from
>> /<>/src/ui/SnackBar.cpp:3:
>> /usr/include/tweeny/tween.tcc:249:6: warning:
> extra ‘;’ [-Wpedantic]
>> 249 | }; | ^ /usr/include/tweeny/tween.tcc:257:6: warning:
> extra ‘;’ [-Wpedantic]
>> 257 | }; | ^ In file included from /usr/include/tweeny/tween.h:596,
>> from /usr/include/tweeny/tweeny.h:81, from
>> /<>/src/ui/SnackBar.cpp:3:
>> /usr/include/tweeny/tweenone.tcc:246:4:
> warning: extra ‘;’ [-Wpedantic]
>> 246 | }; | ^ In file included from
>> /usr/include/tweeny/tweenpoint.tcc:38, from
>> /usr/include/tweeny/tweenpoint.h:80, from
>> /usr/include/tweeny/tween.h:38, from /usr/include/tweeny/tweeny.h:81,
>> from /<>/src/ui/SnackBar.cpp:3:
>> /usr/include/tweeny/easingresolve.h: In substitution of
> ‘template std::function&
> std::function float)>::operator=<_Functor>(std::reference_wrapper<_Tp>) [with
> _Functor = ]’:
>> /usr/include/tweeny/easingresolve.h:62:27: required from
> ‘static void tweeny::detail::easingresolve FunctionTuple, tweeny::easing::linearEasing, Fs
> ...>::impl(FunctionTuple&, tweeny::easing::linearEasing, Fs ...)
> [with int I = 0; TypeTuple = std::array; FunctionTuple =
> std::tuple >; Fs = {}]’
>> /usr/include/tweeny/tweenpoint.tcc:49:75: required from
> ‘void tweeny::detail::easingfill(EasingCollectionT&, EasingT,
> tweeny::detail::int2type<0>) [with TypeTupleT = std::array;
> EasingCollectionT = std::tuple float)> >; EasingT = tweeny::easing::linearEasing]’
>> /usr/include/tweeny/tweenpoint.tcc:101:52: required from
> ‘void tweeny::detail::tweenpoint::via(F) [with F =
> tweeny::easing::linearEasing; Ts = {float}]’
>> /usr/include/tweeny/tweenpoint.tcc:72:16: required from
> ‘tweeny::detail::tweenpoint::tweenpoint(Ts ...) [with Ts =
> {float}]’
>> /usr/include/c++/10/ext/new_allocator.h:150:4: required
>
Bug#980434: Boot failure triggered by USB on rockpro64-rk3399 and pinebook-pro-rk3399
It seems rockpro64-rk3399 and pinebook-pro-rk3399 fail to boot when usb is started. It hangs indefinitely at: ## Flattened Device Tree blob at 01f0 Booting using the fdt blob at 0x1f0 I have observed this also using 2020.10 on rockpro64-rk3399, though on pinebook-pro-rk3399 usb does not work and so it basically avoids triggering the issue. Setting CONFIG_USE_PREBOOT=n in the config works around the problem, though obviously by breaking usb keyboard support or booting from USB devices. Related bugs in Debian and manjaro: https://bugs.debian.org/973323 https://bugs.debian.org/980434 https://gitlab.manjaro.org/manjaro-arm/packages/core/uboot-rockpro64/-/issues/4 Boot log: U-Boot 2021.01+dfsg-1 (Jan 17 2021 - 03:50:13 +) SoC: Rockchip rk3399 Reset cause: POR Model: Pine64 RockPro64 v2.1 DRAM: 3.9 GiB PMIC: RK808 MMC: mmc@fe31: 2, mmc@fe32: 1, sdhci@fe33: 0 Loading Environment from SPIFlash... SF: Detected gd25q128 with page size 256 Bytes, erase size 4 KiB, total 16 MiB *** Warning - bad CRC, using default environment In:serial Out: serial Err: serial Model: Pine64 RockPro64 v2.1 Net: eth0: ethernet@fe30 starting USB... Bus usb@fe38: USB EHCI 1.00 Bus usb@fe3a: USB OHCI 1.0 Bus usb@fe3c: USB EHCI 1.00 Bus usb@fe3e: USB OHCI 1.0 Bus dwc3: usb maximum-speed not found Register 2000140 NbrPorts 2 Starting the controller USB XHCI 1.10 scanning bus usb@fe38 for devices... 1 USB Device(s) found scanning bus usb@fe3a for devices... 1 USB Device(s) found scanning bus usb@fe3c for devices... 1 USB Device(s) found scanning bus usb@fe3e for devices... 1 USB Device(s) found scanning bus dwc3 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Hit any key to stop autoboot: 0 => printenv preboot preboot=usb start => usb reset resetting USB... Bus usb@fe38: USB EHCI 1.00 Bus usb@fe3a: USB OHCI 1.0 Bus usb@fe3c: USB EHCI 1.00 Bus usb@fe3e: USB OHCI 1.0 Bus dwc3: usb maximum-speed not found Register 2000140 NbrPorts 2 Starting the controller USB XHCI 1.10 scanning bus usb@fe38 for devices... 1 USB Device(s) found scanning bus usb@fe3a for devices... 1 USB Device(s) found scanning bus usb@fe3c for devices... 1 USB Device(s) found scanning bus usb@fe3e for devices... 1 USB Device(s) found scanning bus dwc3 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found => boot Card did not respond to voltage select! : -110 switch to partitions #0, OK mmc1 is current device Scanning mmc 1:1... Found /extlinux/extlinux.conf Retrieving file: /extlinux/extlinux.conf 144 bytes read in 5 ms (27.3 KiB/s) 1: Debian-Installer Retrieving file: /initrd.gz 28995285 bytes read in 1287 ms (21.5 MiB/s) Retrieving file: /vmlinuz 26922864 bytes read in 1195 ms (21.5 MiB/s) Retrieving file: /dtbs/rockchip/rk3399-rockpro64.dtb 56849 bytes read in 13 ms (4.2 MiB/s) Moving Image from 0x208 to 0x220, end=3c5 ## Flattened Device Tree blob at 01f0 Booting using the fdt blob at 0x1f0 live well, vagrant signature.asc Description: PGP signature
Processed: your mail
Processing commands for cont...@bugs.debian.org: > affects 980371 - src:fastddsgen Bug #980371 [src:libjsonp-java] libjsonp-java 1.1.2-1 breaks antlr4-maven-plugin Bug #980663 [src:libjsonp-java] eprosima-idl-parser: FTBFS: Could not resolve dependencies for project com.eprosima.idl:com.eprosima.idl:jar:1.0.0 Removed indication that 980371 affects src:fastddsgen Removed indication that 980663 affects src:fastddsgen > End of message, stopping processing here. Please contact me if you need assistance. -- 980371: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980371 980663: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980663 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: your mail
Processing commands for cont...@bugs.debian.org: > affects 980371 src:eprosima-idl-parser src:fastddsgen Bug #980371 [src:libjsonp-java] libjsonp-java 1.1.2-1 breaks antlr4-maven-plugin Bug #980663 [src:libjsonp-java] eprosima-idl-parser: FTBFS: Could not resolve dependencies for project com.eprosima.idl:com.eprosima.idl:jar:1.0.0 Added indication that 980371 affects src:eprosima-idl-parser and src:fastddsgen Added indication that 980663 affects src:eprosima-idl-parser and src:fastddsgen > End of message, stopping processing here. Please contact me if you need assistance. -- 980371: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980371 980663: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980663 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: your mail
Processing commands for cont...@bugs.debian.org: > reassign 980663 src:libjsonp-java Bug #980663 [src:eprosima-idl-parser] eprosima-idl-parser: FTBFS: Could not resolve dependencies for project com.eprosima.idl:com.eprosima.idl:jar:1.0.0 Bug reassigned from package 'src:eprosima-idl-parser' to 'src:libjsonp-java'. No longer marked as found in versions eprosima-idl-parser/1.0.2+dfsg-2. Ignoring request to alter fixed versions of bug #980663 to the same values previously set > merge 980663 980371 Bug #980663 [src:libjsonp-java] eprosima-idl-parser: FTBFS: Could not resolve dependencies for project com.eprosima.idl:com.eprosima.idl:jar:1.0.0 Bug #980663 [src:libjsonp-java] eprosima-idl-parser: FTBFS: Could not resolve dependencies for project com.eprosima.idl:com.eprosima.idl:jar:1.0.0 Marked as found in versions libjsonp-java/1.1.2-1. Bug #980371 [src:libjsonp-java] libjsonp-java 1.1.2-1 breaks antlr4-maven-plugin Added tag(s) sid, bullseye, and ftbfs. Merged 980371 980663 > thank you Stopping processing here. Please contact me if you need assistance. -- 980371: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980371 980663: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980663 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#980658: pygame-sdl2: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2
On Wed, 20 Jan 2021 at 22:01:14 +0100, Lucas Nussbaum wrote: > > dpkg-source -b . Are you deliberately rebuilding the source package? That seems unusual for testing whether packages FTBFS... > > dpkg-source: info: local changes detected, the modified files are: > > pygame-sdl2-7.4.0/gen3/color_dict.html > > pygame-sdl2-7.4.0/gen3/controller.html > > pygame-sdl2-7.4.0/gen3/event_list.html > > pygame-sdl2-7.4.0/gen3/event_names.html > > pygame-sdl2-7.4.0/gen3/glattr.html > > pygame-sdl2-7.4.0/gen3/keycode_list.html > > pygame-sdl2-7.4.0/gen3/pygame_sdl2.color.c > > pygame-sdl2-7.4.0/gen3/pygame_sdl2.color.html (etc.) This seems to be because pygame-sdl2 rebuilds parts of itself during `debian/rules clean`, possibly triggered by being built with a newer version of SDL. That seems strange, and at least arguably a bug in its own right? Deleting these files in debian/clean would probably resolve this. smcv
Bug#980606: supertuxkart: FTBFS: gamepad_config.cpp:35:45: error: static assertion failed: non continous name
On Wed, 20 Jan 2021 at 21:30:37 +0100, Lucas Nussbaum wrote: > >35 | static_assert(SDL_CONTROLLER_BUTTON_MAX - 1 == > > SDL_CONTROLLER_BUTTON_DPAD_RIGHT, "non continous name"); I think this is caused by SDL 2.0.14 adding support for more controller buttons, and supertuxkart assuming that this would never happen. Upstream commit https://github.com/supertuxkart/stk-code/commit/61833c9c26da5520f2eaa02f2458971ba07f2aad seems relevant. smcv
Bug#980664: marked as done (php-guzzlehttp-psr7: FTBFS: tests failed)
Your message dated Wed, 20 Jan 2021 22:49:37 + with message-id and subject line Bug#980664: fixed in php-guzzlehttp-psr7 1.7.0-1~deb11u2 has caused the Debian Bug report #980664, regarding php-guzzlehttp-psr7: FTBFS: tests failed to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 980664: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980664 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: php-guzzlehttp-psr7 Version: 1.7.0-1~deb11u1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20210120 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > phpunit > PHPUnit 9.5.1 by Sebastian Bergmann and contributors. > > Warning: Your XML configuration validates against a deprecated schema. > Suggestion:Migrate your XML configuration using "--migrate-configuration"! > > ... 63 / 833 ( > 7%) > ... 126 / 833 ( > 15%) > ... 189 / 833 ( > 22%) > ... 252 / 833 ( > 30%) > ... 315 / 833 ( > 37%) > ... 378 / 833 ( > 45%) > ... 441 / 833 ( > 52%) > ... 504 / 833 ( > 60%) > ... 567 / 833 ( > 68%) > ... 630 / 833 ( > 75%) > ... 693 / 833 ( > 83%) > F.. 756 / 833 ( > 90%) > ... 819 / 833 ( > 98%) > .. 833 / 833 > (100%) > > Time: 00:00.109, Memory: 14.00 MB > > There was 1 failure: > > 1) GuzzleHttp\Tests\Psr7\UriTest::testParseUriPortCannotBeZero > Failed asserting that exception of type "InvalidArgumentException" is thrown. > > FAILURES! > Tests: 833, Assertions: 1941, Failures: 1. > make[1]: *** [debian/rules:18: override_dh_auto_test] Error 1 The full build log is available from: http://qa-logs.debian.net/2021/01/20/php-guzzlehttp-psr7_1.7.0-1~deb11u1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with me so that we can identify if something relevant changed in the meantime. About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Source: php-guzzlehttp-psr7 Source-Version: 1.7.0-1~deb11u2 Done: David Prévot We believe that the bug you reported is fixed in the latest version of php-guzzlehttp-psr7, 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 980...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. David Prévot (supplier of updated php-guzzlehttp-psr7 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 20 Jan 2021 18:41:37 -0400 Source: php-guzzlehttp-psr7 Architecture: source Version: 1.7.0-1~deb11u2 Distribution: unstable Urgency: medium Maintainer: Debian PHP PEAR Maintainers Changed-By: David Pré
Bug#980659: marked as done (php-codesniffer: FTBFS: tests failed)
Your message dated Wed, 20 Jan 2021 22:49:31 + with message-id and subject line Bug#980659: fixed in php-codesniffer 3.5.8-3 has caused the Debian Bug report #980659, regarding php-codesniffer: FTBFS: tests failed to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 980659: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980659 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: php-codesniffer Version: 3.5.8-2 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20210120 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > cd PHP_CodeSniffer-* && phpunit > PHPUnit 9.5.1 by Sebastian Bergmann and contributors. > > ... 63 / 657 ( > 9%) > ... 126 / 657 ( > 19%) > ... 189 / 657 ( > 28%) > ...S... 252 / 657 ( > 38%) > ... 315 / 657 ( > 47%) > ... 378 / 657 ( > 57%) > ... 441 / 657 ( > 67%) > .....S. 504 / 657 ( > 76%) > S.. 567 / 657 ( > 86%) > SS. 630 / 657 ( > 95%) > .F. 657 / 657 > (100%) > > 437 sniff test files generated 784 unique error codes; 447 were fixable (57%) > > Time: 00:03.283, Memory: 50.00 MB > > There was 1 failure: > > 1) > PHP_CodeSniffer\Standards\Squiz\Tests\Commenting\FileCommentUnitTest::testSniff > Fixed version of FileCommentUnitTest.1.inc does not match expected version in > FileCommentUnitTest.1.inc.fixed; the diff is > [31m--- > src/Standards/Squiz/Tests/Commenting/FileCommentUnitTest.1.inc.fixed[0m > [32m+++ PHP_CodeSniffer[0m > @@ -25,7 +25,7 @@ > * @author > * @copyright 1997 Squiz Pty Ltd (ABN 77 084 670 600) > * @copyright 1994-1997 Squiz Pty Ltd (ABN 77 084 670 600) > [31m-* @copyright 2020 Squiz Pty Ltd (ABN 77 084 670 600)[0m > [32m+* @copyright 2021 Squiz Pty Ltd (ABN 77 084 670 600)[0m > * @licensehttp://www.php.net/license/3_0.txt > * @summaryAn unknown summary tag > * > Fixed version of FileCommentUnitTest.1.js does not match expected version in > FileCommentUnitTest.1.js.fixed; the diff is > [31m--- > src/Standards/Squiz/Tests/Commenting/FileCommentUnitTest.1.js.fixed[0m > [32m+++ PHP_CodeSniffer[0m > @@ -25,7 +25,7 @@ > * @author > * @copyright 1997 Squiz Pty Ltd (ABN 77 084 670 600) > * @copyright 1994-1997 Squiz Pty Ltd (ABN 77 084 670 600) > [31m-* @copyright 2020 Squiz Pty Ltd (ABN 77 084 670 600)[0m > [32m+* @copyright 2021 Squiz Pty Ltd (ABN 77 084 670 600)[0m > * @licensehttp://www.php.net/license/3_0.txt > * @summaryAn unknown summary tag > * > > /<>/PHP_CodeSniffer-3.5.8/tests/Standards/AbstractSniffUnitTest.php:206 > /<>/PHP_CodeSniffer-3.5.8/tests/TestSuite.php:28 > > FAILURES! > Tests: 657, Assertions: 3137, Failures: 1, Skipped: 9. > make[1]: *** [debian/rules:13: override_dh_auto_test] Error 1 The full build log is available from: http://qa-logs.debian.net/2021/01/20/php-codesniffer_3.5.8-2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with me so that we can identify if something relevant changed in the meantime. About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Source: php-codesniffer Source-Version:
Processed: limit source to php-codesniffer, tagging 980659
Processing commands for cont...@bugs.debian.org: > limit source php-codesniffer Limiting to bugs with field 'source' containing at least one of 'php-codesniffer' Limit currently set to 'source':'php-codesniffer' > tags 980659 + pending Bug #980659 [src:php-codesniffer] php-codesniffer: FTBFS: tests failed Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 980659: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980659 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: limit source to php-guzzlehttp-psr7, tagging 980664
Processing commands for cont...@bugs.debian.org: > limit source php-guzzlehttp-psr7 Limiting to bugs with field 'source' containing at least one of 'php-guzzlehttp-psr7' Limit currently set to 'source':'php-guzzlehttp-psr7' > tags 980664 + pending Bug #980664 [src:php-guzzlehttp-psr7] php-guzzlehttp-psr7: FTBFS: tests failed Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 980664: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980664 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#980617: racon: FTBFS: build-dependency not installable: libthread-pool-dev (>= 3.0.2)
On Wed, 20 Jan 2021 21:33:41 +0100 Lucas Nussbaum wrote: > Source: racon > Version: 1.4.20-1 > Severity: serious > Justification: FTBFS on amd64 > Tags: bullseye sid ftbfs > Usertags: ftbfs-20210120 ftbfs-bullseye > > Hi, > > During a rebuild of all packages in sid, your package failed to build > on amd64. > > Relevant part (hopefully): > > +--+ > > | Install package build dependencies | > > +--+ > > > > > > Setup apt archive > > - > > > > Merged Build-Depends: debhelper-compat (= 13), cmake, libgtest-dev, libbioparser-dev (>= 3.0.12), libcereal-dev, libedlib-dev, libspoa-dev, libthread-pool-dev (>= 3.0.2), rampler, build-essential, fakeroot > > Filtered Build-Depends: debhelper-compat (= 13), cmake, libgtest-dev, libbioparser-dev (>= 3.0.12), libcereal-dev, libedlib-dev, libspoa-dev, libthread-pool-dev (>= 3.0.2), rampler, build-essential, fakeroot > > dpkg-deb: building package 'sbuild-build-depends-main-dummy' in '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'. > > Ign:1 copy:/<>/apt_archive ./ InRelease > > Get:2 copy:/<>/apt_archive ./ Release [957 B] > > Ign:3 copy:/<>/apt_archive ./ Release.gpg > > Get:4 copy:/<>/apt_archive ./ Sources [433 B] > > Get:5 copy:/<>/apt_archive ./ Packages [518 B] > > Fetched 1908 B in 0s (187 kB/s) > > Reading package lists... > > Reading package lists... > > > > Install main build dependencies (apt-based resolver) > > > > > > Installing build dependencies > > Reading package lists... > > Building dependency tree... > > Some packages could not be installed. This may mean that you have > > requested an impossible situation or if you are using the unstable > > distribution that some required packages have not yet been created > > or been moved out of Incoming. > > The following information may help to resolve the situation: > > > > The following packages have unmet dependencies: > > sbuild-build-depends-main-dummy : Depends: libthread-pool-dev (>= 3.0.2) but it is not installable > > E: Unable to correct problems, you have held broken packages. > > apt-get failed. https://packages.debian.org/sid/libthread-pool-dev 3.0.2 is indeed available. Racon built just fine on the buildds.. https://buildd.debian.org/status/package.php?p=racon https://buildd.debian.org/status/fetch.php?pkg=racon=amd64=1.4.20-1=1611053002=0 -- Michael R. Crusoe
Bug#980574: marked as done (gitbrute: autopkgtest needs update for new version of git)
Your message dated Wed, 20 Jan 2021 22:33:34 + with message-id and subject line Bug#980574: fixed in gitbrute 0~12-4 has caused the Debian Bug report #980574, regarding gitbrute: autopkgtest needs update for new version of git 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.) -- 980574: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980574 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gitbrute Version: 0~12-3 Severity: serious X-Debbugs-CC: debian...@lists.debian.org, g...@packages.debian.org Tags: sid bullseye User: debian...@lists.debian.org Usertags: needs-update Control: affects -1 src:git Dear maintainer(s), With a recent upload of git the autopkgtest of gitbrute fails in testing when that autopkgtest is run with the binary packages of git from unstable. It passes when run with only packages from testing. In tabular form: passfail gitfrom testing1:2.30.0-1 gitbrute from testing0~12-3 all others from testingfrom testing I copied some of the output at the bottom of this report. git is printing a warning to stderr, and your autopkgtest fails on that (you can ignore it with the allow-stderr, you can of course prevent the output). Currently this regression is blocking the migration of git to testing [1]. Of course, git shouldn't just break your autopkgtest (or even worse, your package), but it seems to me that the change in git was intended and your package needs to update to the new situation. If this is a real problem in your package (and not only in your autopkgtest), the right binary package(s) from git should really add a versioned Breaks on the unfixed version of (one of your) package(s). Note: the Breaks is nice even if the issue is only in the autopkgtest as it helps the migration software to figure out the right versions to combine in the tests. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=git https://ci.debian.net/data/autopkgtest/testing/amd64/g/gitbrute/9861986/log.gz autopkgtest [14:12:27]: test beef: [--- hint: Using 'master' as the name for the initial branch. This default branch name hint: is subject to change. To configure the initial branch name to use in all hint: of your new repositories, which will suppress this warning, call: hint: hint: git config --global init.defaultBranch hint: hint: Names commonly chosen instead of 'master' are 'main', 'trunk' and hint: 'development'. The just-created branch can be renamed via this command: hint: hint: git branch -m Initialized empty Git repository in /tmp/autopkgtest-lxc.pdntqi1e/downtmp/autopkgtest_tmp/.git/ [master (root-commit) 299f06c] Meow! 1 file changed, 1 insertion(+) create mode 100644 meow [master beef688] Meow! Date: Wed Jan 20 14:10:57 2021 + 1 file changed, 1 insertion(+) create mode 100644 meow autopkgtest [14:12:28]: test beef: ---] autopkgtest [14:12:28]: test beef: - - - - - - - - - - results - - - - - - - - - - beef FAIL stderr: hint: Using 'master' as the name for the initial branch. This default branch name autopkgtest [14:12:28]: test beef: - - - - - - - - - - stderr - - - - - - - - - - hint: Using 'master' as the name for the initial branch. This default branch name hint: is subject to change. To configure the initial branch name to use in all hint: of your new repositories, which will suppress this warning, call: hint: hint: git config --global init.defaultBranch hint: hint: Names commonly chosen instead of 'master' are 'main', 'trunk' and hint: 'development'. The just-created branch can be renamed via this command: hint: hint: git branch -m autopkgtest [14:12:28]: summary beef FAIL stderr: hint: Using 'master' as the name for the initial branch. This default branch name OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: gitbrute Source-Version: 0~12-4 Done: Adam Borowski We believe that the bug you reported is fixed in the latest version of gitbrute, 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 980...@bugs.debian.org, and the maintainer will reopen the bug
Processed: Incompatibility of starjava-topcat and starjava-ttools with new starjava-table
Processing control commands: > block -1 by 980153 Bug #980610 [src:starjava-ttools] starjava-ttools: FTBFS: [javac] /<>/src/main/uk/ac/starlink/ttools/plot2/CoordSequence.java:3: error: cannot find symbol 980610 was not blocked by any bugs. 980610 was not blocking any bugs. Added blocking bug(s) of 980610: 980153 -- 980610: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980610 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#980610: Incompatibility of starjava-topcat and starjava-ttools with new starjava-table
Control: block -1 by 980153 The package starjava-table was recently updated; however it now has a split-off (source) package starjava-tjoin (ITP #980153). To fix the FTBFS, starjava-tjoin needs to be accepted, and the updated starjava-ttools resp. starjava-topcat packages must be uploaded with starjava-tjoin as a new dependency, Cheers Ole
Bug#980595: libcheck made a breaking change
libcheck made a breaking change.
Patch for arping to make it build:
https://github.com/ThomasHabets/arping/commit/e0773bc26ae14d4a19825023307d1496d7c7d0f1
I aim to release 2.22 tomorrow with this change.
But there are no changes between 2.21 and 2.22, so you can just patch in
the commit, if you prefer.
I see the tag is set to "serious". To be clear this is a failure of the
TEST to compile only. I agree that this should be seen as serious, but it's
just the test.
Tracking bug on arping (upstream) side:
https://github.com/ThomasHabets/arping/issues/39
--
typedef struct me_s {
char name[] = { "Thomas Habets" };
char email[] = { "tho...@habets.se " };
char kernel[]= { "Linux" };
char *pgpKey[] = { "http://www.habets.pp.se/pubkey.txt; };
char pgp[] = { "9907 8698 8A24 F52F 1C2E 87F6 39A4 9EEA 460A 0169" };
char coolcmd[] = { "echo '. ./_&. ./_'>_;. ./_" };
} me_t;
Bug#980717: kazocsaba-imageviewer FTBFS
Source: kazocsaba-imageviewer Version: 1.2.3-2 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=kazocsaba-imageviewer=all=1.2.3-2=1611094937=0 ... --- Exception in thread "main" java.lang.NoClassDefFoundError: org/apache/commons/cli/UnrecognizedOptionException at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:278) at org.apache.maven.cli.MavenCli.main(MavenCli.java:193) at org.apache.maven.cli.MavenCli.main(MavenCli.java:182) at org.debian.maven.Wrapper.main(Wrapper.java:89) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:566) at org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:321) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:234) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:406) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:347) Caused by: java.lang.ClassNotFoundException: org.apache.commons.cli.UnrecognizedOptionException at org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:50) at org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(ClassRealm.java:271) at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:247) at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:239) ... 12 more dh_auto_build: error: /usr/lib/jvm/default-java/bin/java -noverify -cp /usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.home=/usr/share/maven -Dmaven.multiModuleProjectDirectory=/<> -Dclassworlds.conf=/etc/maven/m2-debian.conf -Dproperties.file.manual=/<>/debian/maven.properties org.codehaus.plexus.classworlds.launcher.Launcher -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian -Dmaven.repo.local=/<>/debian/maven-repo --batch-mode package -DskipTests -Dnotimestamp=true -Dlocale=en_US returned exit code 1 make: *** [debian/rules:4: binary-indep] Error 25
Processed: Incompatibility of starjava-topcat and starjava-ttools with new starjava-table
Processing control commands: > block -1 by 980153 Bug #980613 [src:starjava-topcat] starjava-topcat: FTBFS: build-dependency not installable: starlink-ttools-java (>= 3.3~) 980613 was not blocked by any bugs. 980613 was not blocking any bugs. Added blocking bug(s) of 980613: 980153 -- 980613: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980613 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#980613: Incompatibility of starjava-topcat and starjava-ttools with new starjava-table
Control: block -1 by 980153 The package starjava-table was recently updated; however it now has a split-off (source) package starjava-tjoin (ITP #980153). To fix the FTBFS, starjava-tjoin needs to be accepted, and the updated starjava-ttools resp. starjava-topcat packages must be uploaded with starjava-tjoin as a new dependency, Cheers Ole
Bug#980423: 3.12.4 makes several packages FTBFS
Hi,
* Sebastian Ramacher [2021-01-20 22:20]:
On 2021-01-19 00:05:36 +0100, László Böszörményi wrote:
On Mon, Jan 18, 2021 at 10:24 PM Laurent Bigonville wrote:
> Several packages FTBFS since 3.12.4
>
> The autopkgtest catched ignition-msgs and ignition-transport, see
> https://packages.qa.debian.org/p/protobuf.html
>
> I can see that evolution-data-server also FTBFS
[...]
> This is a bit unfortunate that it's happening so late in the developpement
cycle.
Indeed, my fault. Investigating. Hope this can be resolved easily.
The autopkgtest failures indicate that ignition-msgs' and
ignition-transport's dependencies on libprotobuf-dev (>= X.Y), (<
X.{Y+1}) is not enough. It will need to be (>= X.Y.Z), (< X.Y.{Z+1})
instead.
I guess an other option would be to depend on the new API definition:
Package: libprotobuf-dev
Provides: protobuf-api-23-0
@László: would you agree? (We discussed this in #963247 before).
Cheers Jochen
signature.asc
Description: PGP signature
Bug#967010: (no subject)
Sorry not sorry~HM King MBS -- Sent from King Philps' NETWORKS & MORE 77
Bug#980623: marked as done (node-i18next-xhr-backend: FTBFS: build-dependency not installable: node-babel-polyfill (>= 7))
Your message dated Wed, 20 Jan 2021 22:04:20 + with message-id and subject line Bug#980623: fixed in node-i18next-xhr-backend 3.2.2+ds-10 has caused the Debian Bug report #980623, regarding node-i18next-xhr-backend: FTBFS: build-dependency not installable: node-babel-polyfill (>= 7) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 980623: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980623 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-i18next-xhr-backend Version: 3.2.2+ds-9 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20210120 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: debhelper-compat (= 13), nodejs (>= 6), pkg-js-tools > (>= 0.8.13~), rollup, node-babel-core (>= 7), > node-babel-plugin-transform-runtime (>= 7), node-babel-preset-env (>= 7), > node-babel-polyfill (>= 7), node-rollup-plugin-commonjs, > node-rollup-plugin-babel (>= 5.2~), node-rollup-plugin-node-resolve (>= 11~), > node-rollup-plugin-terser, node-babel-runtime (>= 7), build-essential, > fakeroot > Filtered Build-Depends: debhelper-compat (= 13), nodejs (>= 6), pkg-js-tools > (>= 0.8.13~), rollup, node-babel-core (>= 7), > node-babel-plugin-transform-runtime (>= 7), node-babel-preset-env (>= 7), > node-babel-polyfill (>= 7), node-rollup-plugin-commonjs, > node-rollup-plugin-babel (>= 5.2~), node-rollup-plugin-node-resolve (>= 11~), > node-rollup-plugin-terser, node-babel-runtime (>= 7), build-essential, > fakeroot > dpkg-deb: building package 'sbuild-build-depends-main-dummy' in > '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'. > Ign:1 copy:/<>/apt_archive ./ InRelease > Get:2 copy:/<>/apt_archive ./ Release [957 B] > Ign:3 copy:/<>/apt_archive ./ Release.gpg > Get:4 copy:/<>/apt_archive ./ Sources [488 B] > Get:5 copy:/<>/apt_archive ./ Packages [574 B] > Fetched 2019 B in 0s (198 kB/s) > Reading package lists... > Reading package lists... > > Install main build dependencies (apt-based resolver) > > > Installing build dependencies > Reading package lists... > Building dependency tree... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > sbuild-build-depends-main-dummy : Depends: node-babel-polyfill (>= 7) but it > is not going to be installed > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://qa-logs.debian.net/2021/01/20/node-i18next-xhr-backend_3.2.2+ds-9_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with me so that we can identify if something relevant changed in the meantime. About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Source: node-i18next-xhr-backend Source-Version: 3.2.2+ds-10 Done: Nicolas Mora We believe that the bug you reported is fixed in the latest version of node-i18next-xhr-backend, 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
Processed: Re: Processed (with 2 errors): fixup
Processing commands for cont...@bugs.debian.org: > reassign 980573 src:golang-github-cznic-lldb Bug #980573 [golang-github-cznic-lldb] golang-github-cznic-lldb 1.0.1-1 fails to build from source (ftbfs) Bug reassigned from package 'golang-github-cznic-lldb' to 'src:golang-github-cznic-lldb'. No longer marked as found in versions 1.0.1-1. Ignoring request to alter fixed versions of bug #980573 to the same values previously set > forcemerge 980573 980668 Bug #980573 [src:golang-github-cznic-lldb] golang-github-cznic-lldb 1.0.1-1 fails to build from source (ftbfs) Bug #980573 [src:golang-github-cznic-lldb] golang-github-cznic-lldb 1.0.1-1 fails to build from source (ftbfs) Marked as found in versions golang-github-cznic-lldb/1.0.1-1. Bug #980668 [src:golang-github-cznic-lldb] golang-github-cznic-lldb: FTBFS: expects import "modernc.org/fileutil" Merged 980573 980668 > reassign 980572 src:golang-github-cznic-ql Bug #980572 [golang-github-cznic-ql] golang-github-cznic-ql 1.0.6-1 fails to build from source (ftbfs) Bug reassigned from package 'golang-github-cznic-ql' to 'src:golang-github-cznic-ql'. No longer marked as found in versions 1.0.6-1. Ignoring request to alter fixed versions of bug #980572 to the same values previously set > forcemerge 980572 980706 Bug #980572 [src:golang-github-cznic-ql] golang-github-cznic-ql 1.0.6-1 fails to build from source (ftbfs) Bug #980572 [src:golang-github-cznic-ql] golang-github-cznic-ql 1.0.6-1 fails to build from source (ftbfs) Marked as found in versions golang-github-cznic-ql/1.0.6-1. Bug #980706 [src:golang-github-cznic-ql] golang-github-cznic-ql: FTBFS: expects import "modernc.org/mathutil" Merged 980572 980706 > thanks Stopping processing here. Please contact me if you need assistance. -- 980572: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980572 980573: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980573 980668: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980668 980706: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980706 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 980473
Processing commands for cont...@bugs.debian.org: > tags 980473 + pending Bug #980473 [python3-potr] ModuleNotFoundError: No module named 'Crypto' Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 980473: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980473 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed (with 2 errors): fixup
Processing commands for cont...@bugs.debian.org: > tags 980573 bullseye sid ftbfs Bug #980573 [golang-github-cznic-lldb] golang-github-cznic-lldb 1.0.1-1 fails to build from source (ftbfs) Added tag(s) ftbfs, sid, and bullseye. > forcemerge 980573 980668 Bug #980573 [golang-github-cznic-lldb] golang-github-cznic-lldb 1.0.1-1 fails to build from source (ftbfs) Unable to merge bugs because: package of #980668 is 'src:golang-github-cznic-lldb' not 'golang-github-cznic-lldb' Failed to forcibly merge 980573: Did not alter merged bugs. > tags 980572 bullseye sid ftbfs Bug #980572 [golang-github-cznic-ql] golang-github-cznic-ql 1.0.6-1 fails to build from source (ftbfs) Added tag(s) bullseye, sid, and ftbfs. > forcemerge 980572 980706 Bug #980572 [golang-github-cznic-ql] golang-github-cznic-ql 1.0.6-1 fails to build from source (ftbfs) Unable to merge bugs because: package of #980706 is 'src:golang-github-cznic-ql' not 'golang-github-cznic-ql' Failed to forcibly merge 980572: Did not alter merged bugs. > thanks Stopping processing here. Please contact me if you need assistance. -- 980572: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980572 980573: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980573 980668: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980668 980706: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980706 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#980619: marked as done (conntrack-tools: FTBFS: build-dependency not installable: libnetfilter-cthelper0 (= 1.0.0-1+b1))
Your message dated Wed, 20 Jan 2021 21:48:48 + with message-id and subject line Bug#980619: fixed in conntrack-tools 1:1.4.6-2 has caused the Debian Bug report #980619, regarding conntrack-tools: FTBFS: build-dependency not installable: libnetfilter-cthelper0 (= 1.0.0-1+b1) 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.) -- 980619: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980619 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: conntrack-tools Version: 1:1.4.6-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20210120 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: bison, debhelper (>= 11), flex, libmnl-dev (>= 1.0.1), > libnetfilter-conntrack-dev (>= 1.0.8), libnetfilter-cthelper0-dev, > libnetfilter-cttimeout-dev (>= 1.0.0), libnetfilter-queue-dev (>= 1.0.2), > libnfnetlink-dev (>= 1.0.1), libsystemd-dev (>= 227), autoconf, automake, > libtool, build-essential, fakeroot > Filtered Build-Depends: bison, debhelper (>= 11), flex, libmnl-dev (>= > 1.0.1), libnetfilter-conntrack-dev (>= 1.0.8), libnetfilter-cthelper0-dev, > libnetfilter-cttimeout-dev (>= 1.0.0), libnetfilter-queue-dev (>= 1.0.2), > libnfnetlink-dev (>= 1.0.1), libsystemd-dev (>= 227), autoconf, automake, > libtool, build-essential, fakeroot > dpkg-deb: building package 'sbuild-build-depends-main-dummy' in > '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'. > Ign:1 copy:/<>/apt_archive ./ InRelease > Get:2 copy:/<>/apt_archive ./ Release [957 B] > Ign:3 copy:/<>/apt_archive ./ Release.gpg > Get:4 copy:/<>/apt_archive ./ Sources [462 B] > Get:5 copy:/<>/apt_archive ./ Packages [545 B] > Fetched 1964 B in 0s (190 kB/s) > Reading package lists... > Reading package lists... > > Install main build dependencies (apt-based resolver) > > > Installing build dependencies > Reading package lists... > Building dependency tree... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > libnetfilter-cthelper0-dev : Depends: libnetfilter-cthelper0 (= 1.0.0-1+b1) > but it is not going to be installed > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://qa-logs.debian.net/2021/01/20/conntrack-tools_1.4.6-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with me so that we can identify if something relevant changed in the meantime. About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Source: conntrack-tools Source-Version: 1:1.4.6-2 Done: Arturo Borrero Gonzalez We believe that the bug you reported is fixed in the latest version of conntrack-tools, 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 980...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Arturo Borrero Gonzalez (supplier of updated conntrack-tools package) (This
Bug#980624: marked as done (node-i18next: FTBFS: build-dependency not installable: node-babel-polyfill (>= 7))
Your message dated Wed, 20 Jan 2021 21:49:50 + with message-id and subject line Bug#980624: fixed in node-i18next 19.8.4+dfsg-1 has caused the Debian Bug report #980624, regarding node-i18next: FTBFS: build-dependency not installable: node-babel-polyfill (>= 7) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 980624: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980624 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-i18next Version: 19.8.2+dfsg-4 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20210120 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: debhelper-compat (= 13), nodejs (>= 6), > dh-sequence-nodejs, rollup, node-rollup-plugin-commonjs, > node-rollup-plugin-babel (>= 5.2~), node-rollup-plugin-node-resolve (>= 11~), > node-rollup-plugin-terser, node-babel-core (>= 7), > node-babel-plugin-proposal-async-generator-functions (>= 7), > node-babel-plugin-proposal-object-rest-spread (>= 7), > node-babel-plugin-transform-modules-commonjs (>= 7), > node-babel-plugin-transform-runtime (>= 7), node-babel-polyfill (>= 7), > node-babel-preset-env (>= 7), node-babel-preset-react (>= 7), > node-babel-register (>= 7), node-babel-runtime (>= 7), node-tape, > build-essential, fakeroot > Filtered Build-Depends: debhelper-compat (= 13), nodejs (>= 6), > dh-sequence-nodejs, rollup, node-rollup-plugin-commonjs, > node-rollup-plugin-babel (>= 5.2~), node-rollup-plugin-node-resolve (>= 11~), > node-rollup-plugin-terser, node-babel-core (>= 7), > node-babel-plugin-proposal-async-generator-functions (>= 7), > node-babel-plugin-proposal-object-rest-spread (>= 7), > node-babel-plugin-transform-modules-commonjs (>= 7), > node-babel-plugin-transform-runtime (>= 7), node-babel-polyfill (>= 7), > node-babel-preset-env (>= 7), node-babel-preset-react (>= 7), > node-babel-register (>= 7), node-babel-runtime (>= 7), node-tape, > build-essential, fakeroot > dpkg-deb: building package 'sbuild-build-depends-main-dummy' in > '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'. > Ign:1 copy:/<>/apt_archive ./ InRelease > Get:2 copy:/<>/apt_archive ./ Release [963 B] > Ign:3 copy:/<>/apt_archive ./ Release.gpg > Get:4 copy:/<>/apt_archive ./ Sources [548 B] > Get:5 copy:/<>/apt_archive ./ Packages [639 B] > Fetched 2150 B in 0s (0 B/s) > Reading package lists... > Reading package lists... > > Install main build dependencies (apt-based resolver) > > > Installing build dependencies > Reading package lists... > Building dependency tree... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > sbuild-build-depends-main-dummy : Depends: node-babel-polyfill (>= 7) but it > is not going to be installed > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://qa-logs.debian.net/2021/01/20/node-i18next_19.8.2+dfsg-4_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with me so that we can identify if something relevant changed in the meantime. About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed b
Processed: Bug#980700 marked as pending in astropy
Processing control commands:
> tag -1 pending
Bug #980700 [src:astropy] astropy: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p 3.9 returned exit code 13
Added tag(s) pending.
--
980700: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980700
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#980700: marked as pending in astropy
Control: tag -1 pending Hello, Bug #980700 in astropy reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/debian-astro-team/astropy/-/commit/fecbf0764ffc4629be7bd44e0460b99415b7973e Ignore RuntimeWarnings from newer scipy Closes: #980700 (this message was generated automatically) -- Greetings https://bugs.debian.org/980700
Bug#980595: arping: FTBFS: arping_test.c:239:8: error: ‘test_mkpacket’ redeclared as different kind of symbol
Hi, On Wed, Jan 20, 2021 at 09:25:15PM +0100, Lucas Nussbaum wrote: > Source: arping > Version: 2.21-1 > Severity: serious > Justification: FTBFS on amd64 > Tags: bullseye sid ftbfs > Usertags: ftbfs-20210120 ftbfs-bullseye > > Hi, > > During a rebuild of all packages in sid, your package failed to build > on amd64. > > Relevant part (hopefully): > > gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 > > -D_DEFAULT_SOURCE=1 -g -O2 -ffile-prefix-map=/<>=. > > -fstack-protector-strong -Wformat -Werror=format-security -c -o > > arping_test.o arping_test.c > > In file included from arping_test.c:29: > > arping_test.c:239:8: error: ‘test_mkpacket’ redeclared as different kind of > > symbol > > 239 | MYTEST(test_mkpacket) > > |^ > > arping_test.c:239:1: note: in expansion of macro ‘MYTEST’ > > 239 | MYTEST(test_mkpacket) > > | ^~ > > arping_test.c:239:8: note: previous declaration of ‘test_mkpacket’ was here > > 239 | MYTEST(test_mkpacket) > > |^ > > arping_test.c:58:31: note: in definition of macro ‘MYTEST’ > >58 | #define MYTEST(a) static void a(int);__attribute__((constructor)) \ > > | ^ > > In file included from arping_test.c:29: > > arping_test.c:264:8: error: ‘pingip_uninteresting_packet’ redeclared as > > different kind of symbol > > 264 | MYTEST(pingip_uninteresting_packet) > > |^~~ > > arping_test.c:264:1: note: in expansion of macro ‘MYTEST’ > > 264 | MYTEST(pingip_uninteresting_packet) > > | ^~ > > arping_test.c:264:8: note: previous declaration of > > ‘pingip_uninteresting_packet’ was here > > 264 | MYTEST(pingip_uninteresting_packet) > > |^~~ > > arping_test.c:58:31: note: in definition of macro ‘MYTEST’ > >58 | #define MYTEST(a) static void a(int);__attribute__((constructor)) \ > > | ^ > > In file included from arping_test.c:29: > > arping_test.c:392:8: error: ‘pingip_interesting_packet’ redeclared as > > different kind of symbol > > 392 | MYTEST(pingip_interesting_packet) > > |^ > > arping_test.c:392:1: note: in expansion of macro ‘MYTEST’ > > 392 | MYTEST(pingip_interesting_packet) > > | ^~ > > arping_test.c:392:8: note: previous declaration of > > ‘pingip_interesting_packet’ was here > > 392 | MYTEST(pingip_interesting_packet) > > |^ > > arping_test.c:58:31: note: in definition of macro ‘MYTEST’ > >58 | #define MYTEST(a) static void a(int);__attribute__((constructor)) \ > > | ^ > > In file included from arping_test.c:29: > > arping_test.c: In function ‘pingip_interesting_packet_fn’: > > arping_test.c:445:21: warning: too many arguments for format > > [-Wformat-extra-args] > > 445 | "numrecvd not incremented"); > > | ^~ > > arping_test.c:449:21: warning: too many arguments for format > > [-Wformat-extra-args] > > 449 | "numrecvd not incremented second time"); > > | ^~ > > arping_test.c: At top level: > > arping_test.c:452:8: error: ‘strip_newline_test’ redeclared as different > > kind of symbol > > 452 | MYTEST(strip_newline_test) > > |^~ > > arping_test.c:452:1: note: in expansion of macro ‘MYTEST’ > > 452 | MYTEST(strip_newline_test) > > | ^~ > > arping_test.c:452:8: note: previous declaration of ‘strip_newline_test’ was > > here > > 452 | MYTEST(strip_newline_test) > > |^~ > > arping_test.c:58:31: note: in definition of macro ‘MYTEST’ > >58 | #define MYTEST(a) static void a(int);__attribute__((constructor)) \ > > | ^ > > In file included from arping_test.c:29: > > arping_test.c:472:8: error: ‘get_mac_addr_success’ redeclared as different > > kind of symbol > > 472 | MYTEST(get_mac_addr_success) > > |^~~~ > > arping_test.c:472:1: note: in expansion of macro ‘MYTEST’ > > 472 | MYTEST(get_mac_addr_success) > > | ^~ > > arping_test.c:472:8: note: previous declaration of ‘get_mac_addr_success’ > > was here > > 472 |
Bug#953544: marked as done (cclive: Uninstallable due to missing libboost packages)
Your message dated Wed, 20 Jan 2021 21:33:21 +
with message-id
and subject line Bug#953544: fixed in cclive 0.9.3-0.2
has caused the Debian Bug report #953544,
regarding cclive: Uninstallable due to missing libboost packages
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.)
--
953544: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953544
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cclive
Version: 0.9.3-0.1+b2
Severity: grave
Justification: renders package unusable
The following NEW packages will be installed:
cclive{b} libquvi-0.9-0.9.3{a} libquvi-scripts-0.9{a} lua-bitop{a}
lua-expat{a} lua-json{a} lua-socket{a}
0 packages upgraded, 7 newly installed, 0 to remove and 0 not upgraded.
Need to get 374 kB/387 kB of archives. After unpacking 1,870 kB will be used.
The following packages have unmet dependencies:
cclive : Depends: libboost-date-time1.62.0 which is a virtual package and is
not provided by any available package
Depends: libboost-filesystem1.62.0 which is a virtual package and is
not provided by any available package
Depends: libboost-iostreams1.62.0 which is a virtual package and is
not provided by any available package
Depends: libboost-program-options1.62.0 which is a virtual package
and is not provided by any available package
Depends: libboost-system1.62.0 which is a virtual package and is not
provided by any available package
The following actions will resolve these dependencies:
Keep the following packages at their current version:
1) cclive [Not Installed]
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.4.0-4-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: cclive
Source-Version: 0.9.3-0.2
Done: Sudip Mukherjee
We believe that the bug you reported is fixed in the latest version of
cclive, 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 953...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Sudip Mukherjee (supplier of updated cclive
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 18 Jan 2021 20:29:07 +
Source: cclive
Architecture: source
Version: 0.9.3-0.2
Distribution: unstable
Urgency: medium
Maintainer: Alejandro Garrido Mota
Changed-By: Sudip Mukherjee
Closes: 914056 953544
Changes:
cclive (0.9.3-0.2) unstable; urgency=medium
.
* Non-maintainer upload.
* Fix FTBFS with boost 1.67. (Closes: #914056)
- Thanks to Giovanni Mascellani.
- Rebuild will depend on current libboost packages. (Closes: #953544)
Checksums-Sha1:
20c4a4b8388b441d3fc846070a07bc2e7ce29571 2109 cclive_0.9.3-0.2.dsc
c9966fdafb37c3ac5a3f906adeb3c7fed6955568 5208 cclive_0.9.3-0.2.debian.tar.xz
31e365cb0901eaf95e79528eb5a5beb2da804621 9076 cclive_0.9.3-0.2_amd64.buildinfo
Checksums-Sha256:
badd66119c2e4e25d2695388e58d521a720fbfdda5709a3ec831077a8219b9ae 2109
cclive_0.9.3-0.2.dsc
dd3af18cb6af326d0bb2de298486cd8338e7e5a17cc720525b4cedb91004af05 5208
cclive_0.9.3-0.2.debian.tar.xz
fa8abd8271c4aad08c59f4ff904b1ca77e702410c00e549da880713d09e81282 9076
cclive_0.9.3-0.2_amd64.buildinfo
Files:
c3f59eee946b05b3b3dc7040354d77f4 2109 video optional cclive_0.9.3-0.2.dsc
2d43be354255592f71233902b445b633 5208 video optional
cclive_0.9.3-0.2.debian.tar.xz
b292d0929454e535f9eaedc1644d092f 9076 video optional
cclive_0.9.3-0.2_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEuDQJkCg9jZvBlJrHR5mjUUbRKzUFAmAF98MACgkQR5mjUUbR
KzW1CA//RFofeQacJsKb9NM20a5WxdOlIYmswhF2KpQhiE6n64C4kYlR5TQXNKvM
TO9cAJfjES3pcOjPYLAuG9SKp1iiwGmQ4wBZmxlf6dcYNswTqKJ3fPZcuWzoRG83
euoNPPQ+T0OqJ9/O4ApXign9iJ9t/TKuo4rV51lSz5+32JbtM2mElYEAPoImWyDZ
Bug#914056: marked as done (cclive FTBFS with boost 1.67)
Your message dated Wed, 20 Jan 2021 21:33:21 + with message-id and subject line Bug#914056: fixed in cclive 0.9.3-0.2 has caused the Debian Bug report #914056, regarding cclive FTBFS with boost 1.67 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.) -- 914056: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914056 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: cclive Version: 0.9.3-0.1 Severity: serious Tags: ftbfs buster sid https://buildd.debian.org/status/package.php?p=cclive=sid ... In file included from ./ccprogressbar:1, from cc/file.cpp:41: ./cc/progressbar.h: In static member function 'static std::__cxx11::string cc::progressbar::eta_from_seconds(double)': ./cc/progressbar.h:319:48: error: no matching function for call to 'boost::posix_time::seconds::seconds(const double&)' const pt::time_duration& td = pt::seconds(s); ^ In file included from /usr/include/boost/date_time/posix_time/posix_time_types.hpp:16, from /usr/include/boost/date_time/posix_time/time_formatters.hpp:16, from /usr/include/boost/date_time/posix_time/posix_time.hpp:24, from ./cc/progressbar.h:26, from ./ccprogressbar:1, from cc/file.cpp:41: /usr/include/boost/date_time/posix_time/posix_time_duration.hpp:57:16: note: candidate: 'template boost::posix_time::seconds::seconds(const T&, typename boost::enable_if >::type*)' explicit seconds(T const& s, ^~~ /usr/include/boost/date_time/posix_time/posix_time_duration.hpp:57:16: note: template argument deduction/substitution failed: /usr/include/boost/date_time/posix_time/posix_time_duration.hpp: In substitution of 'template boost::posix_time::seconds::seconds(const T&, typename boost::enable_if >::type*) [with T = double]': ./cc/progressbar.h:319:48: required from here /usr/include/boost/date_time/posix_time/posix_time_duration.hpp:57:16: error: no type named 'type' in 'struct boost::enable_if, void>' /usr/include/boost/date_time/posix_time/posix_time_duration.hpp:53:30: note: candidate: 'boost::posix_time::seconds::seconds(const boost::posix_time::seconds&)' class BOOST_SYMBOL_VISIBLE seconds : public time_duration ^~~ /usr/include/boost/date_time/posix_time/posix_time_duration.hpp:53:30: note: no known conversion for argument 1 from 'const double' to 'const boost::posix_time::seconds&' /usr/include/boost/date_time/posix_time/posix_time_duration.hpp:53:30: note: candidate: 'boost::posix_time::seconds::seconds(boost::posix_time::seconds&&)' /usr/include/boost/date_time/posix_time/posix_time_duration.hpp:53:30: note: no known conversion for argument 1 from 'const double' to 'boost::posix_time::seconds&&' make[3]: *** [Makefile:593: cc/file.o] Error 1 --- End Message --- --- Begin Message --- Source: cclive Source-Version: 0.9.3-0.2 Done: Sudip Mukherjee We believe that the bug you reported is fixed in the latest version of cclive, 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 914...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sudip Mukherjee (supplier of updated cclive package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 18 Jan 2021 20:29:07 + Source: cclive Architecture: source Version: 0.9.3-0.2 Distribution: unstable Urgency: medium Maintainer: Alejandro Garrido Mota Changed-By: Sudip Mukherjee Closes: 914056 953544 Changes: cclive (0.9.3-0.2) unstable; urgency=medium . * Non-maintainer upload. * Fix FTBFS with boost 1.67. (Closes: #914056) - Thanks to Giovanni Mascellani. - Rebuild will depend on current libboost packages. (Closes: #953544) Checksums-Sha1: 20c4a4b8388b441d3fc846070a07bc2e7ce29571 2109 cclive_0.9.3-0.2.dsc c9966fdafb37c3ac5a3f906adeb3c7fed6955568 5208 cclive_0.9.3-0.2.debian.tar.xz 31e365cb0901eaf95e79528eb5a5beb2da804621 9076 cclive_0.9.3-0.2_amd64.buildinfo Checksums-Sha256: badd66119c2e4e25d2695388e58d521a720fbfdda5709a3ec831077a8219b9ae 2109
Processed: bug 980606 is forwarded to https://github.com/supertuxkart/stk-code/issues/4467
Processing commands for cont...@bugs.debian.org: > forwarded 980606 https://github.com/supertuxkart/stk-code/issues/4467 Bug #980606 [src:supertuxkart] supertuxkart: FTBFS: gamepad_config.cpp:35:45: error: static assertion failed: non continous name Set Bug forwarded-to-address to 'https://github.com/supertuxkart/stk-code/issues/4467'. > thanks Stopping processing here. Please contact me if you need assistance. -- 980606: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980606 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bug 980595 is forwarded to https://github.com/ThomasHabets/arping/issues/39
Processing commands for cont...@bugs.debian.org: > forwarded 980595 https://github.com/ThomasHabets/arping/issues/39 Bug #980595 [src:arping] arping: FTBFS: arping_test.c:239:8: error: ‘test_mkpacket’ redeclared as different kind of symbol Set Bug forwarded-to-address to 'https://github.com/ThomasHabets/arping/issues/39'. > thanks Stopping processing here. Please contact me if you need assistance. -- 980595: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980595 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#980645: leiningen-clojure: FTBFS: Cannot access central (https://repo1.maven.org/maven2/) in offline mode and the artifact org.slf4j:slf4j-nop:jar:1.7.25 has not been downloaded from it before.
On 2021-01-20 12:58, Lucas Nussbaum wrote: Source: leiningen-clojure Version: 2.9.1-3 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20210120 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): make[1]: Entering directory '/<>' cd leiningen-core && lein bootstrap Leiningen's classpath: :/usr/share/java/leiningen-2.9.1.jar Applying task [with-profile base do install, classpath .lein-bootstrap] to [] Applying task do to (install, classpath .lein-bootstrap) Applying task install to [] Cannot access central (https://repo1.maven.org/maven2/) in offline mode and the artifact org.slf4j:slf4j-nop:jar:1.7.25 has not been downloaded from it before. Cannot access clojars (https://repo.clojars.org/) in offline mode and the artifact org.slf4j:slf4j-nop:jar:1.7.25 has not been downloaded from it before. Thanks, I'll TAL, probably this weekend at the latest... - e
Processed: Re: Bug#980423: 3.12.4 makes several packages FTBFS
Processing control commands: > clone -1 -2 -3 Bug #980423 [src:protobuf] 3.12.4 makes several packages FTBFS Bug 980423 cloned as bugs 980714-980715 > reassign -2 src:ignition-msgs 5.1.0+dfsg-6 Bug #980714 [src:protobuf] 3.12.4 makes several packages FTBFS Bug reassigned from package 'src:protobuf' to 'src:ignition-msgs'. No longer marked as found in versions protobuf/3.12.4-1. Ignoring request to alter fixed versions of bug #980714 to the same values previously set Bug #980714 [src:ignition-msgs] 3.12.4 makes several packages FTBFS Marked as found in versions ignition-msgs/5.1.0+dfsg-6. > retitle -2 tighten dependencies on libprotobuf-dev Bug #980714 [src:ignition-msgs] 3.12.4 makes several packages FTBFS Changed Bug title to 'tighten dependencies on libprotobuf-dev' from '3.12.4 makes several packages FTBFS'. > reassign -3 src:ignition-transport 8.0.0+dfsg-3 Bug #980715 [src:protobuf] 3.12.4 makes several packages FTBFS Bug reassigned from package 'src:protobuf' to 'src:ignition-transport'. No longer marked as found in versions protobuf/3.12.4-1. Ignoring request to alter fixed versions of bug #980715 to the same values previously set Bug #980715 [src:ignition-transport] 3.12.4 makes several packages FTBFS Marked as found in versions ignition-transport/8.0.0+dfsg-3. > retitle -3 tighten dependencies on libprotobuf-dev Bug #980715 [src:ignition-transport] 3.12.4 makes several packages FTBFS Changed Bug title to 'tighten dependencies on libprotobuf-dev' from '3.12.4 makes several packages FTBFS'. -- 980423: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980423 980714: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980714 980715: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980715 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#980423: 3.12.4 makes several packages FTBFS
Control: clone -1 -2 -3
Control: reassign -2 src:ignition-msgs 5.1.0+dfsg-6
Control: retitle -2 tighten dependencies on libprotobuf-dev
Control: reassign -3 src:ignition-transport 8.0.0+dfsg-3
Control: retitle -3 tighten dependencies on libprotobuf-dev
On 2021-01-19 00:05:36 +0100, László Böszörményi wrote:
> On Mon, Jan 18, 2021 at 10:24 PM Laurent Bigonville wrote:
> > Several packages FTBFS since 3.12.4
> >
> > The autopkgtest catched ignition-msgs and ignition-transport, see
> > https://packages.qa.debian.org/p/protobuf.html
> >
> > I can see that evolution-data-server also FTBFS
> [...]
> > This is a bit unfortunate that it's happening so late in the developpement
> > cycle.
> Indeed, my fault. Investigating. Hope this can be resolved easily.
The autopkgtest failures indicate that ignition-msgs' and
ignition-transport's dependencies on libprotobuf-dev (>= X.Y), (<
X.{Y+1}) is not enough. It will need to be (>= X.Y.Z), (< X.Y.{Z+1})
instead.
Cheers
--
Sebastian Ramacher
signature.asc
Description: PGP signature
Bug#980712: golang-github-dvsekhvalnov-jose2go: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 1 github.com/dvsekhvalnov/jose2go github.com/dvsekhvalnov/jose2go/aes gith
Source: golang-github-dvsekhvalnov-jose2go
Version: 1.3-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210120 ftbfs-bullseye
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: warning: Compatibility levels before 10 are deprecated (level 9 in use)
>dh_update_autotools_config -O--buildsystem=golang
>dh_auto_configure -O--buildsystem=golang
> dh_auto_configure: warning: Compatibility levels before 10 are deprecated
> (level 9 in use)
>dh_auto_build -O--buildsystem=golang
> dh_auto_build: warning: Compatibility levels before 10 are deprecated (level
> 9 in use)
> cd obj-x86_64-linux-gnu && go install -trimpath -v -p 1
> github.com/dvsekhvalnov/jose2go github.com/dvsekhvalnov/jose2go/aes
> github.com/dvsekhvalnov/jose2go/arrays
> github.com/dvsekhvalnov/jose2go/base64url
> github.com/dvsekhvalnov/jose2go/compact github.com/dvsekhvalnov/jose2go/kdf
> github.com/dvsekhvalnov/jose2go/keys/ecc
> github.com/dvsekhvalnov/jose2go/keys/rsa
> github.com/dvsekhvalnov/jose2go/padding
> internal/unsafeheader
> internal/cpu
> internal/bytealg
> runtime/internal/atomic
> runtime/internal/sys
> runtime/internal/math
> runtime
> internal/reflectlite
> errors
> internal/race
> sync/atomic
> sync
> io
> unicode
> unicode/utf8
> bytes
> strings
> bufio
> math/bits
> math
> strconv
> reflect
> sort
> internal/fmtsort
> internal/oserror
> syscall
> internal/syscall/unix
> time
> internal/poll
> internal/syscall/execenv
> internal/testlog
> os
> fmt
> compress/flate
> hash
> crypto
> crypto/internal/subtle
> crypto/subtle
> encoding/binary
> crypto/cipher
> crypto/aes
> math/rand
> math/big
> crypto/elliptic
> crypto/internal/randutil
> crypto/sha512
> unicode/utf16
> encoding/asn1
> vendor/golang.org/x/crypto/cryptobyte/asn1
> vendor/golang.org/x/crypto/cryptobyte
> crypto/ecdsa
> crypto/hmac
> crypto/rand
> crypto/rsa
> crypto/sha1
> crypto/sha256
> encoding
> encoding/base64
> encoding/json
> github.com/dvsekhvalnov/jose2go/base64url
> github.com/dvsekhvalnov/jose2go/arrays
> github.com/dvsekhvalnov/jose2go/aes
> github.com/dvsekhvalnov/jose2go/compact
> github.com/dvsekhvalnov/jose2go/kdf
> crypto/des
> crypto/dsa
> crypto/ed25519/internal/edwards25519
> crypto/ed25519
> crypto/md5
> encoding/hex
> crypto/x509/pkix
> encoding/pem
> path/filepath
> io/ioutil
> context
> vendor/golang.org/x/net/dns/dnsmessage
> internal/nettrace
> internal/singleflight
> runtime/cgo
> net
> net/url
> crypto/x509
> github.com/dvsekhvalnov/jose2go/keys/ecc
> github.com/dvsekhvalnov/jose2go/padding
> github.com/dvsekhvalnov/jose2go
> github.com/dvsekhvalnov/jose2go/keys/rsa
>dh_auto_test -O--buildsystem=golang
> dh_auto_test: warning: Compatibility levels before 10 are deprecated (level 9
> in use)
> cd obj-x86_64-linux-gnu && go test -vet=off -v -p 1
> github.com/dvsekhvalnov/jose2go github.com/dvsekhvalnov/jose2go/aes
> github.com/dvsekhvalnov/jose2go/arrays
> github.com/dvsekhvalnov/jose2go/base64url
> github.com/dvsekhvalnov/jose2go/compact github.com/dvsekhvalnov/jose2go/kdf
> github.com/dvsekhvalnov/jose2go/keys/ecc
> github.com/dvsekhvalnov/jose2go/keys/rsa
> github.com/dvsekhvalnov/jose2go/padding
> === RUN Test
>
> invalid sign 'alg' header err= jwt.Decode(): required 'alg' header is missing
> or of invalid type
>
> missing sign 'alg' header err= jwt.Decode(): required 'alg' header is missing
> or of invalid type
>
> two phased err= Test error
>
> invalid encrypt 'alg' header err= jwt.Decode(): required 'alg' header is
> missing or of invalid type
>
> invalid encrypt 'enc' header err= jwt.Decode(): required 'enc' header is
> missing or of invalid type
>
> missing encrypt 'alg' header err= jwt.Decode(): required 'alg' header is
> missing or of invalid type
>
> missing encrypt 'enc' header err= jwt.Decode(): required 'enc' header is
> missing or of invalid type
>
> --
> FAIL: jose_test.go:1588:
> TestSuite.TestDecrypt_PBSE2_HS256_A128KW_A128CBC_HS256
>
> jose_test.go:1596:
> //then
> c.Assert(err, IsNil)
> ... value *errors.errorString = {s:"aes.KeyUnwrap():
> integrity check failed."} ("aes.KeyUnwrap(): integrity check failed.")
>
>
> --
> FAIL: jose_test.go:1600:
>
Bug#980708: trapperkeeper-scheduler-clojure: FTBFS: Cannot access central (https://repo1.maven.org/maven2/) in offline mode and the artifact com.fasterxml.jackson.core:jackson-core:jar:debian has not
Source: trapperkeeper-scheduler-clojure Version: 1.1.3-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20210120 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > lein pom debian/pom.xml > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact com.fasterxml.jackson.core:jackson-core:jar:debian has not been > downloaded from it before. > Cannot access clojars (https://repo.clojars.org/) in offline mode and the > artifact com.fasterxml.jackson.core:jackson-core:jar:debian has not been > downloaded from it before. > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact > com.fasterxml.jackson.dataformat:jackson-dataformat-smile:jar:debian has not > been downloaded from it before. > Cannot access clojars (https://repo.clojars.org/) in offline mode and the > artifact com.fasterxml.jackson.dataformat:jackson-dataformat-smile:jar:debian > has not been downloaded from it before. > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact > com.fasterxml.jackson.dataformat:jackson-dataformat-cbor:jar:debian has not > been downloaded from it before. > Cannot access clojars (https://repo.clojars.org/) in offline mode and the > artifact com.fasterxml.jackson.dataformat:jackson-dataformat-cbor:jar:debian > has not been downloaded from it before. > This could be due to a typo in :dependencies, file system permissions, or > network issues. > If you are behind a proxy, try setting the 'http_proxy' environment variable. > make[1]: *** [debian/rules:17: override_dh_auto_build] Error 1 The full build log is available from: http://qa-logs.debian.net/2021/01/20/trapperkeeper-scheduler-clojure_1.1.3-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with me so that we can identify if something relevant changed in the meantime. About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures.
Bug#980711: gpaw: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 --test-pytest "--test-args=-v -m ci" returned exit code 13
Source: gpaw
Version: 20.10.0-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210120 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_test -- --test-pytest --test-args="-v -m ci"
> I: pybuild base:232: cd /<>/.pybuild/cpython3_3.9/build;
> python3.9 -m pytest -v -m ci
> = test session starts
> ==
> platform linux -- Python 3.9.1+, pytest-6.0.2, py-1.10.0, pluggy-0.13.0 --
> /usr/bin/python3.9
> cachedir: .pytest_cache
> rootdir: /<>, configfile: pytest.ini
> collecting ... collected 0 items / 1 error
>
> ERRORS
>
> ERROR collecting test session
> _
> /usr/lib/python3.9/importlib/__init__.py:127: in import_module
> return _bootstrap._gcd_import(name[level:], package, level)
> :1030: in _gcd_import
> ???
> :1007: in _find_and_load
> ???
> :972: in _find_and_load_unlocked
> ???
> :228: in _call_with_frames_removed
> ???
> :1030: in _gcd_import
> ???
> :1007: in _find_and_load
> ???
> :972: in _find_and_load_unlocked
> ???
> :228: in _call_with_frames_removed
> ???
> :1030: in _gcd_import
> ???
> :1007: in _find_and_load
> ???
> :986: in _find_and_load_unlocked
> ???
> :680: in _load_unlocked
> ???
> :790: in exec_module
> ???
> :228: in _call_with_frames_removed
> ???
> gpaw/__init__.py:35: in
> from ase.cli.run import str2dict
> gpaw/broadcast_imports.py:77: in load_module
> return self.load_from_cache(fullname)
> gpaw/broadcast_imports.py:87: in load_from_cache
> exec(code, module.__dict__)
> /usr/lib/python3/dist-packages/ase/cli/run.py:9: in
> from ase.eos import EquationOfState
> gpaw/broadcast_imports.py:77: in load_module
> return self.load_from_cache(fullname)
> gpaw/broadcast_imports.py:87: in load_from_cache
> exec(code, module.__dict__)
> /usr/lib/python3/dist-packages/ase/eos.py:7: in
> from scipy.optimize import curve_fit
> gpaw/broadcast_imports.py:77: in load_module
> return self.load_from_cache(fullname)
> gpaw/broadcast_imports.py:87: in load_from_cache
> exec(code, module.__dict__)
> /usr/lib/python3/dist-packages/scipy/optimize/__init__.py:413: in
> from ._linprog import linprog, linprog_verbose_callback
> gpaw/broadcast_imports.py:77: in load_module
> return self.load_from_cache(fullname)
> gpaw/broadcast_imports.py:87: in load_from_cache
> exec(code, module.__dict__)
> /usr/lib/python3/dist-packages/scipy/optimize/_linprog.py:25: in
> from ._linprog_highs import _linprog_highs
> gpaw/broadcast_imports.py:77: in load_module
> return self.load_from_cache(fullname)
> gpaw/broadcast_imports.py:87: in load_from_cache
> exec(code, module.__dict__)
> /usr/lib/python3/dist-packages/scipy/optimize/_linprog_highs.py:20: in
>
> from ._highs.highs_wrapper import highs_wrapper
> gpaw/broadcast_imports.py:109: in find_spec
> raise ImportError
> E ImportError
> === short test summary info
>
> ERROR ../../.. - ImportError
> Interrupted: 1 error during collection
>
> === 1 error in 0.58s
> ===
> E: pybuild pybuild:353: test: plugin distutils failed with: exit code=2: cd
> /<>/.pybuild/cpython3_3.9/build; python3.9 -m pytest -v -m ci
> dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9
> --test-pytest "--test-args=-v -m ci" returned exit code 13
The full build log is available from:
http://qa-logs.debian.net/2021/01/20/gpaw_20.10.0-2_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with me
so that we can identify if something relevant changed in the meantime.
About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
Bug#980710: mpi4py: FTBFS: ld: cannot find -llmpe
Source: mpi4py Version: 3.0.3-7 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20210120 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_auto_build override_dh_auto_build-arch -- \ > --build-args "--mpicc=/usr/bin/mpicc --mpicxx=/usr/bin/mpicxx" > I: pybuild base:232: /usr/bin/python3 setup.py build --mpicc=/usr/bin/mpicc > --mpicxx=/usr/bin/mpicxx > running build > running build_src > running build_py > creating /<>/.pybuild/cpython3_3.9/build/mpi4py > copying src/mpi4py/bench.py -> > /<>/.pybuild/cpython3_3.9/build/mpi4py > copying src/mpi4py/__init__.py -> > /<>/.pybuild/cpython3_3.9/build/mpi4py > copying src/mpi4py/__main__.py -> > /<>/.pybuild/cpython3_3.9/build/mpi4py > copying src/mpi4py/run.py -> > /<>/.pybuild/cpython3_3.9/build/mpi4py > creating /<>/.pybuild/cpython3_3.9/build/mpi4py/futures > copying src/mpi4py/futures/__init__.py -> > /<>/.pybuild/cpython3_3.9/build/mpi4py/futures > copying src/mpi4py/futures/__main__.py -> > /<>/.pybuild/cpython3_3.9/build/mpi4py/futures > copying src/mpi4py/futures/_base.py -> > /<>/.pybuild/cpython3_3.9/build/mpi4py/futures > copying src/mpi4py/futures/pool.py -> > /<>/.pybuild/cpython3_3.9/build/mpi4py/futures > copying src/mpi4py/futures/aplus.py -> > /<>/.pybuild/cpython3_3.9/build/mpi4py/futures > copying src/mpi4py/futures/_lib.py -> > /<>/.pybuild/cpython3_3.9/build/mpi4py/futures > copying src/mpi4py/futures/server.py -> > /<>/.pybuild/cpython3_3.9/build/mpi4py/futures > copying src/mpi4py/libmpi.pxd -> > /<>/.pybuild/cpython3_3.9/build/mpi4py > copying src/mpi4py/__init__.pxd -> > /<>/.pybuild/cpython3_3.9/build/mpi4py > copying src/mpi4py/MPI.pxd -> > /<>/.pybuild/cpython3_3.9/build/mpi4py > creating /<>/.pybuild/cpython3_3.9/build/mpi4py/include > creating /<>/.pybuild/cpython3_3.9/build/mpi4py/include/mpi4py > copying src/mpi4py/include/mpi4py/mpi4py.h -> > /<>/.pybuild/cpython3_3.9/build/mpi4py/include/mpi4py > copying src/mpi4py/include/mpi4py/mpi4py.MPI_api.h -> > /<>/.pybuild/cpython3_3.9/build/mpi4py/include/mpi4py > copying src/mpi4py/include/mpi4py/mpi4py.MPI.h -> > /<>/.pybuild/cpython3_3.9/build/mpi4py/include/mpi4py > copying src/mpi4py/include/mpi4py/mpi4py.i -> > /<>/.pybuild/cpython3_3.9/build/mpi4py/include/mpi4py > copying src/mpi4py/include/mpi4py/mpi.pxi -> > /<>/.pybuild/cpython3_3.9/build/mpi4py/include/mpi4py > running build_clib > MPI configuration: [mpi] from 'mpi.cfg' > MPI C compiler:/usr/bin/mpicc > MPI C++ compiler: /usr/bin/mpicxx > checking for library 'lmpe' ... > /usr/bin/mpicc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv > -O2 -Wall -g -fstack-protector-strong -Wformat -Werror=format-security -g > -fwrapv -O2 -g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > -D_FORTIFY_SOURCE=2 -fPIC -c _configtest.c -o _configtest.o > /usr/bin/mpicc -pthread -Wl,-z,relro -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 _configtest.o -llmpe > -o _configtest > /usr/bin/ld: cannot find -llmpe > collect2: error: ld returned 1 exit status The full build log is available from: http://qa-logs.debian.net/2021/01/20/mpi4py_3.0.3-7_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with me so that we can identify if something relevant changed in the meantime. About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures.
Bug#980709: dolfin: FTBFS: tests failed
Source: dolfin Version: 2019.2.0~git20200629.946dbd3+lfs-4 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20210120 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[8]: Entering directory '/<>/obj-x86_64-linux-gnu' > [ 98%] Building CXX object > demo/undocumented/waveguide/cpp/CMakeFiles/demo_waveguide.dir/main.cpp.o > cd "/<>/obj-x86_64-linux-gnu/demo/undocumented/waveguide/cpp" && > /usr/bin/c++ -DDOLFIN_VERSION=\"2019.2.0.dev0\" -DHAS_CHOLMOD -DHAS_HDF5 > -DHAS_MPI -DHAS_PETSC -DHAS_SCOTCH -DHAS_UMFPACK -DHAS_ZLIB -DNDEBUG > -I"/<>" -I"/<>/dolfin" > -I"/<>/obj-x86_64-linux-gnu" -isystem > /usr/lib/python3/dist-packages/ffc/backends/ufc -isystem /usr/include/eigen3 > -isystem /usr/include/hdf5/openmpi -isystem > /usr/lib/x86_64-linux-gnu/openmpi/include/openmpi -isystem > /usr/lib/x86_64-linux-gnu/openmpi/include -isystem > /usr/lib/petscdir/petsc3.14/x86_64-linux-gnu-real/include -Wno-comment > -fpermissive -O2 -g -DNDEBUG -std=c++11 -o > CMakeFiles/demo_waveguide.dir/main.cpp.o -c > "/<>/demo/undocumented/waveguide/cpp/main.cpp" > [ 98%] Linking CXX executable demo_spatial-coordinates > cd > "/<>/obj-x86_64-linux-gnu/demo/undocumented/spatial-coordinates/cpp" > && /usr/bin/cmake -E cmake_link_script > CMakeFiles/demo_spatial-coordinates.dir/link.txt --verbose=1 > /usr/bin/c++ -Wno-comment -fpermissive -O2 -g -DNDEBUG -Wl,-z,relro > CMakeFiles/demo_spatial-coordinates.dir/main.cpp.o -o > demo_spatial-coordinates ../../../../dolfin/libdolfin.so.2019.2.0.dev0 > /usr/lib/x86_64-linux-gnu/libboost_timer.so > /usr/lib/x86_64-linux-gnu/libboost_chrono.so > /usr/lib/x86_64-linux-gnu/hdf5/openmpi/libhdf5.so > /usr/lib/x86_64-linux-gnu/libsz.so /usr/lib/x86_64-linux-gnu/libz.so > /usr/lib/x86_64-linux-gnu/libdl.so -lm > /usr/lib/petscdir/petsc3.14/x86_64-linux-gnu-real/lib/libpetsc_real.so > /usr/lib/x86_64-linux-gnu/openmpi/lib/libmpi_cxx.so > /usr/lib/x86_64-linux-gnu/openmpi/lib/libmpi.so > make[8]: Leaving directory '/<>/obj-x86_64-linux-gnu' > [ 98%] Built target demo_spatial-coordinates > [ 98%] Linking CXX executable demo_waveguide > cd "/<>/obj-x86_64-linux-gnu/demo/undocumented/waveguide/cpp" && > /usr/bin/cmake -E cmake_link_script CMakeFiles/demo_waveguide.dir/link.txt > --verbose=1 > /usr/bin/c++ -Wno-comment -fpermissive -O2 -g -DNDEBUG -Wl,-z,relro > CMakeFiles/demo_waveguide.dir/main.cpp.o -o demo_waveguide > ../../../../dolfin/libdolfin.so.2019.2.0.dev0 > /usr/lib/x86_64-linux-gnu/libboost_timer.so > /usr/lib/x86_64-linux-gnu/libboost_chrono.so > /usr/lib/x86_64-linux-gnu/hdf5/openmpi/libhdf5.so > /usr/lib/x86_64-linux-gnu/libsz.so /usr/lib/x86_64-linux-gnu/libz.so > /usr/lib/x86_64-linux-gnu/libdl.so -lm > /usr/lib/petscdir/petsc3.14/x86_64-linux-gnu-real/lib/libpetsc_real.so > /usr/lib/x86_64-linux-gnu/openmpi/lib/libmpi_cxx.so > /usr/lib/x86_64-linux-gnu/openmpi/lib/libmpi.so > make[8]: Leaving directory '/<>/obj-x86_64-linux-gnu' > [ 98%] Built target demo_waveguide > [100%] Linking CXX executable demo_sym-dirichlet-bc > cd > "/<>/obj-x86_64-linux-gnu/demo/undocumented/sym-dirichlet-bc/cpp" > && /usr/bin/cmake -E cmake_link_script > CMakeFiles/demo_sym-dirichlet-bc.dir/link.txt --verbose=1 > /usr/bin/c++ -Wno-comment -fpermissive -O2 -g -DNDEBUG -Wl,-z,relro > CMakeFiles/demo_sym-dirichlet-bc.dir/main.cpp.o -o demo_sym-dirichlet-bc > ../../../../dolfin/libdolfin.so.2019.2.0.dev0 > /usr/lib/x86_64-linux-gnu/libboost_timer.so > /usr/lib/x86_64-linux-gnu/libboost_chrono.so > /usr/lib/x86_64-linux-gnu/hdf5/openmpi/libhdf5.so > /usr/lib/x86_64-linux-gnu/libsz.so /usr/lib/x86_64-linux-gnu/libz.so > /usr/lib/x86_64-linux-gnu/libdl.so -lm > /usr/lib/petscdir/petsc3.14/x86_64-linux-gnu-real/lib/libpetsc_real.so > /usr/lib/x86_64-linux-gnu/openmpi/lib/libmpi_cxx.so > /usr/lib/x86_64-linux-gnu/openmpi/lib/libmpi.so > make[8]: Leaving directory '/<>/obj-x86_64-linux-gnu' > [100%] Built target demo_sym-dirichlet-bc > [100%] Linking CXX executable demo_time-series > cd "/<>/obj-x86_64-linux-gnu/demo/undocumented/time-series/cpp" > && /usr/bin/cmake -E cmake_link_script > CMakeFiles/demo_time-series.dir/link.txt --verbose=1 > /usr/bin/c++ -Wno-comment -fpermissive -O2 -g -DNDEBUG -Wl,-z,relro > CMakeFiles/demo_time-series.dir/main.cpp.o -o demo_time-series > ../../../../dolfin/libdolfin.so.2019.2.0.dev0 > /usr/lib/x86_64-linux-gnu/libboost_timer.so > /usr/lib/x86_64-li
Bug#980706: golang-github-cznic-ql: FTBFS: expects import "modernc.org/mathutil"
Source: golang-github-cznic-ql Version: 1.0.6-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20210120 ftbfs-bullseye 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 --builddirectory=_build > dh: warning: Compatibility levels before 10 are deprecated (level 9 in use) >dh_update_autotools_config -O--buildsystem=golang -O--builddirectory=_build >dh_auto_configure -O--buildsystem=golang -O--builddirectory=_build > dh_auto_configure: warning: Compatibility levels before 10 are deprecated > (level 9 in use) >dh_auto_build -O--buildsystem=golang -O--builddirectory=_build > dh_auto_build: warning: Compatibility levels before 10 are deprecated (level > 9 in use) > cd _build && go install -trimpath -v -p 1 github.com/cznic/ql > github.com/cznic/ql/design github.com/cznic/ql/driver github.com/cznic/ql/ql > github.com/cznic/ql/vendored/github.com/camlistore/go4/lock > src/github.com/cznic/lldb/2pc.go:16:2: code in directory > /<>/_build/src/github.com/cznic/fileutil expects import > "modernc.org/fileutil" > src/github.com/cznic/lldb/2pc.go:17:2: code in directory > /<>/_build/src/github.com/cznic/mathutil expects import > "modernc.org/mathutil" > dh_auto_build: error: cd _build && go install -trimpath -v -p 1 > github.com/cznic/ql github.com/cznic/ql/design github.com/cznic/ql/driver > github.com/cznic/ql/ql > github.com/cznic/ql/vendored/github.com/camlistore/go4/lock returned exit > code 1 > make: *** [debian/rules:7: build] Error 25 The full build log is available from: http://qa-logs.debian.net/2021/01/20/golang-github-cznic-ql_1.0.6-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with me so that we can identify if something relevant changed in the meantime. About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures.
Bug#980705: golang-github-cznic-strutil: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 1 github.com/cznic/strutil returned exit code 1
Source: golang-github-cznic-strutil Version: 0.0~git20150430.0.1eb03e3-2 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20210120 ftbfs-bullseye 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: warning: Compatibility levels before 10 are deprecated (level 9 in use) >dh_update_autotools_config -O--buildsystem=golang >dh_auto_configure -O--buildsystem=golang > dh_auto_configure: warning: Compatibility levels before 10 are deprecated > (level 9 in use) >dh_auto_build -O--buildsystem=golang > dh_auto_build: warning: Compatibility levels before 10 are deprecated (level > 9 in use) > cd obj-x86_64-linux-gnu && go install -trimpath -v -p 1 > github.com/cznic/strutil > internal/unsafeheader > internal/cpu > internal/bytealg > runtime/internal/atomic > runtime/internal/sys > runtime/internal/math > runtime > internal/reflectlite > errors > internal/race > sync/atomic > sync > io > unicode > unicode/utf8 > bytes > math/bits > math > strconv > encoding/base32 > reflect > encoding/binary > encoding/base64 > sort > internal/fmtsort > internal/oserror > syscall > internal/syscall/unix > time > internal/poll > internal/syscall/execenv > internal/testlog > os > fmt > strings > github.com/cznic/strutil >dh_auto_test -O--buildsystem=golang > dh_auto_test: warning: Compatibility levels before 10 are deprecated (level 9 > in use) > cd obj-x86_64-linux-gnu && go test -vet=off -v -p 1 > github.com/cznic/strutil > # github.com/cznic/strutil > src/github.com/cznic/strutil/all_test.go:10:2: code in directory > /<>/obj-x86_64-linux-gnu/src/github.com/cznic/mathutil expects > import "modernc.org/mathutil" > FAIL github.com/cznic/strutil [setup failed] > FAIL > dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 1 > github.com/cznic/strutil returned exit code 1 The full build log is available from: http://qa-logs.debian.net/2021/01/20/golang-github-cznic-strutil_0.0~git20150430.0.1eb03e3-2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with me so that we can identify if something relevant changed in the meantime. About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures.
Bug#980704: node-is-reference: FTBFS: Error: Cannot find module '@types/estree'
Source: node-is-reference
Version: 1.2.1-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210120 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> dpkg-buildpackage
> -
>
> Command: dpkg-buildpackage -us -uc -sa -rfakeroot
> dpkg-buildpackage: info: source package node-is-reference
> dpkg-buildpackage: info: source version 1.2.1-2
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Xavier Guimard
> dpkg-source --before-build .
> dpkg-buildpackage: info: host architecture amd64
> debian/rules clean
> dh clean --with nodejs
>dh_auto_clean --buildsystem=nodejs
> rm -rf ./node_modules/.cache
>dh_clean
> dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building node-is-reference using existing
> ./node-is-reference_1.2.1.orig.tar.gz
> dpkg-source: info: building node-is-reference in
> node-is-reference_1.2.1-2.debian.tar.xz
> dpkg-source: info: building node-is-reference in node-is-reference_1.2.1-2.dsc
> debian/rules binary
> dh binary --with nodejs
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure --buildsystem=nodejs
> mkdir node_modules
> internal/modules/cjs/loader.js:818
> throw err;
> ^
>
> Error: Cannot find module '@types/estree'
> Require stack:
> - /<>/[eval]
> at Function.Module._resolveFilename
> (internal/modules/cjs/loader.js:815:15)
> at Function.resolve (internal/modules/cjs/helpers.js:80:19)
> at [eval]:1:21
> at Script.runInThisContext (vm.js:120:18)
> at Object.runInThisContext (vm.js:309:38)
> at Object. ([eval]-wrapper:10:26)
> at Module._compile (internal/modules/cjs/loader.js:999:30)
> at evalScript (internal/process/execution.js:94:25)
> at internal/main/eval_string.js:23:3 {
> code: 'MODULE_NOT_FOUND',
> requireStack: [ '/<>/[eval]' ]
> }
> ### @types/estree is required by debian/nodejs/./extlinks but not available
> make: *** [debian/rules:4: binary] Error 1
The full build log is available from:
http://qa-logs.debian.net/2021/01/20/node-is-reference_1.2.1-2_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with me
so that we can identify if something relevant changed in the meantime.
About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
Bug#980702: node-nodemailer: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 3
Source: node-nodemailer Version: 6.4.17-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20210120 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > dpkg-buildpackage > - > > Command: dpkg-buildpackage -us -uc -sa -rfakeroot > dpkg-buildpackage: info: source package node-nodemailer > dpkg-buildpackage: info: source version 6.4.17-1 > dpkg-buildpackage: info: source distribution unstable > dpkg-buildpackage: info: source changed by Xavier Guimard > dpkg-source --before-build . > dpkg-buildpackage: info: host architecture amd64 > debian/rules clean > dh clean >dh_auto_clean --buildsystem=nodejs > rm -rf ./node_modules/.cache >dh_clean > dpkg-source -b . > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-source: info: building node-nodemailer using existing > ./node-nodemailer_6.4.17.orig.tar.gz > dpkg-source: info: building node-nodemailer in > node-nodemailer_6.4.17-1.debian.tar.xz > dpkg-source: info: building node-nodemailer in node-nodemailer_6.4.17-1.dsc > debian/rules binary > dh binary >dh_update_autotools_config >dh_autoreconf >dh_auto_configure --buildsystem=nodejs >dh_auto_build --buildsystem=nodejs > No build command found, searching known files > cd ./. && grunt > Can't exec "grunt": No such file or directory at > /usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line 522. > dh_auto_build: warning: ### Command "grunt" failed in . > > dh_auto_build: warning: > > 1 failures, unable to build automatically. > Install a debian/nodejs/./build or add a "override_dh_auto_build:" target > in debian/rules > > > dh_auto_build: warning: Aborting auto_build > > Command "grunt" succeeded in . >dh_auto_test --buildsystem=nodejs > mkdir -p node_modules > ln -s ../debian/tests/test_modules/libbase64 node_modules/libbase64 > ln -s ../debian/tests/test_modules/base32.js node_modules/base32.js > ln -s ../debian/tests/test_modules/libmime node_modules/libmime > ln -s ../debian/tests/test_modules/proxy-test-server > node_modules/proxy-test-server > ln -s ../debian/tests/test_modules/libqp node_modules/libqp > ln -s ../debian/tests/test_modules/safer-buffer > node_modules/safer-buffer > ln -s ../debian/tests/test_modules/proxy node_modules/proxy > ln -s ../debian/tests/test_modules/ipv6-normalize > node_modules/ipv6-normalize > ln -s ../debian/tests/test_modules/smtp-server node_modules/smtp-server > ln -s ../. node_modules/nodemailer > /bin/sh -ex debian/tests/pkg-js/test > + set -e > + ln -s .. node_modules/nodemailer > ln: failed to create symbolic link 'node_modules/nodemailer/..': File exists > + true > + mocha --timeout 5 test/addressparser/addressparser-test.js > test/base64/base64-test.js test/dkim/dkim-test.js > test/dkim/message-parser-test.js test/dkim/relaxed-body-test.js > test/dkim/sign-test.js test/fetch/cookies-test.js test/fetch/fetch-test.js > test/json-transport/json-transport-test.js > test/mail-composer/mail-composer-test.js test/mime-funcs/mime-funcs-test.js > test/mime-funcs/mime-types-test.js test/mime-node/mime-node-test.js > test/qp/qp-test.js test/sendmail/le-windows-test.js > test/sendmail/sendmail-test.js test/ses-transport/ses-transport-test.js > test/shared/shared-test.js test/smtp-connection/http-proxy-client-test.js > test/smtp-connection/smtp-connection-test.js test/smtp-pool/smtp-pool-test.js > test/smtp-transport/smtp-tranport-test.js > test/stream-transport/stream-transport-test.js > test/well-known/well-known-test.js test/xoauth2/xoauth2-test.js > > > #addressparser > ✓ should handle single address correctly > ✓ should handle multiple addresses correctly > ✓ should handle unquoted name correctly > ✓ should handle quoted name correctly > ✓ should handle quoted semicolons correctly > ✓ should handle unquoted name, unquoted address correctly > ✓ should handle emtpy group correctly > ✓ should handle address group correctly > ✓ should handle semicolon as a delimiter > ✓ should handle mixed group correctly > ✓ should flatten mixed group correctly > ✓ semicolon as delimiter should not break group parsing > ✓ should handle name from comment correctly > ✓ should handle skip comment correctly > ✓ should handle missing address correctly > ✓ should handle a
Bug#980697: borgmatic: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13
Source: borgmatic Version: 1.5.12-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20210120 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_clean > rm -rf borgmatic.egg-info > for man in borgmatic generate-borgmatic-config upgrade-borgmatic-config > validate-borgmatic-config ; do \ > [ ! -f debian/$man.1 ] || rm debian/$man.1 ; \ > done > make[1]: Leaving directory '/<>' > dpkg-source -b . > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-source: info: building borgmatic using existing > ./borgmatic_1.5.12.orig.tar.gz > dpkg-source: info: using patch list from debian/patches/series > dpkg-source: info: building borgmatic in borgmatic_1.5.12-1.debian.tar.xz > dpkg-source: info: building borgmatic in borgmatic_1.5.12-1.dsc > debian/rules binary > dh binary --with python3 --buildsystem=pybuild >dh_update_autotools_config -O--buildsystem=pybuild >dh_autoreconf -O--buildsystem=pybuild >dh_auto_configure -O--buildsystem=pybuild > I: pybuild base:232: python3.9 setup.py config > running config >dh_auto_build -O--buildsystem=pybuild > I: pybuild base:232: /usr/bin/python3 setup.py build > running build > running build_py > creating /<>/.pybuild/cpython3_3.9/build/borgmatic > copying borgmatic/execute.py -> > /<>/.pybuild/cpython3_3.9/build/borgmatic > copying borgmatic/__init__.py -> > /<>/.pybuild/cpython3_3.9/build/borgmatic > copying borgmatic/verbosity.py -> > /<>/.pybuild/cpython3_3.9/build/borgmatic > copying borgmatic/logger.py -> > /<>/.pybuild/cpython3_3.9/build/borgmatic > copying borgmatic/signals.py -> > /<>/.pybuild/cpython3_3.9/build/borgmatic > creating /<>/.pybuild/cpython3_3.9/build/borgmatic/hooks > copying borgmatic/hooks/healthchecks.py -> > /<>/.pybuild/cpython3_3.9/build/borgmatic/hooks > copying borgmatic/hooks/__init__.py -> > /<>/.pybuild/cpython3_3.9/build/borgmatic/hooks > copying borgmatic/hooks/cronitor.py -> > /<>/.pybuild/cpython3_3.9/build/borgmatic/hooks > copying borgmatic/hooks/command.py -> > /<>/.pybuild/cpython3_3.9/build/borgmatic/hooks > copying borgmatic/hooks/dispatch.py -> > /<>/.pybuild/cpython3_3.9/build/borgmatic/hooks > copying borgmatic/hooks/postgresql.py -> > /<>/.pybuild/cpython3_3.9/build/borgmatic/hooks > copying borgmatic/hooks/monitor.py -> > /<>/.pybuild/cpython3_3.9/build/borgmatic/hooks > copying borgmatic/hooks/cronhub.py -> > /<>/.pybuild/cpython3_3.9/build/borgmatic/hooks > copying borgmatic/hooks/mysql.py -> > /<>/.pybuild/cpython3_3.9/build/borgmatic/hooks > copying borgmatic/hooks/pagerduty.py -> > /<>/.pybuild/cpython3_3.9/build/borgmatic/hooks > copying borgmatic/hooks/dump.py -> > /<>/.pybuild/cpython3_3.9/build/borgmatic/hooks > creating /<>/.pybuild/cpython3_3.9/build/borgmatic/config > copying borgmatic/config/validate.py -> > /<>/.pybuild/cpython3_3.9/build/borgmatic/config > copying borgmatic/config/convert.py -> > /<>/.pybuild/cpython3_3.9/build/borgmatic/config > copying borgmatic/config/__init__.py -> > /<>/.pybuild/cpython3_3.9/build/borgmatic/config > copying borgmatic/config/override.py -> > /<>/.pybuild/cpython3_3.9/build/borgmatic/config > copying borgmatic/config/load.py -> > /<>/.pybuild/cpython3_3.9/build/borgmatic/config > copying borgmatic/config/legacy.py -> > /<>/.pybuild/cpython3_3.9/build/borgmatic/config > copying borgmatic/config/normalize.py -> > /<>/.pybuild/cpython3_3.9/build/borgmatic/config > copying borgmatic/config/collect.py -> > /<>/.pybuild/cpython3_3.9/build/borgmatic/config > copying borgmatic/config/generate.py -> > /<>/.pybuild/cpython3_3.9/build/borgmatic/config > copying borgmatic/config/checks.py -> > /<>/.pybuild/cpython3_3.9/build/borgmatic/config > creating /<>/.pybuild/cpython3_3.9/build/borgmatic/commands > copying borgmatic/commands/__init__.py -> > /<>/.pybuild/cpython3_3.9/build/borgmatic/commands > copying borgmatic/commands/borgmatic.py -> > /<>/.pybuild/cpython3_3.9/build/borgmatic/commands > copying borgmatic/commands/generate_config.py -> > /<>/.pybuild/cpython3_3.9/build/borgmatic/commands > copying borgmatic/commands/arguments.py -> > /<>/.pybuild/cpython3_3.9/build/borgmatic/commands > copying borgmatic/commands/validate_config.py -> > /<>/.pybuild/cpython3_3.9/build/borgmatic/com
Bug#980699: grcompiler: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j4 test ARGS\+=-j4 returned exit code 2
Source: grcompiler Version: 5.2-2.1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20210120 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>/obj-x86_64-linux-gnu' > Running tests... > /usr/bin/ctest --force-new-ctest-process -j4 > Test project /<>/obj-x86_64-linux-gnu > Start 1: compile_SchTest > Start 4: compile_CharisTest > Start 7: compile_PigLatinTest_v2 > Start 10: compile_PigLatinTest_v3 > 1/15 Test #7: compile_PigLatinTest_v2 . Passed0.03 sec > Start 13: compile_PadaukTest_v3 > 2/15 Test #10: compile_PigLatinTest_v3 . Passed0.03 sec > Start 8: GrcRegressionTest_PigLatinTest_v2 > 3/15 Test #8: GrcRegressionTest_PigLatinTest_v2 ... Passed0.00 sec > Start 9: compare_PigLatinTest_v2 > 4/15 Test #9: compare_PigLatinTest_v2 .***Failed0.01 sec > Files "PigLatinTest_v2.ttf" to > "/<>/test/GrcRegressionTest/fonts/PigLatinBenchmark_v2.ttf" are > different. > > Start 11: GrcRegressionTest_PigLatinTest_v3 > 5/15 Test #11: GrcRegressionTest_PigLatinTest_v3 ... Passed0.00 sec > Start 12: compare_PigLatinTest_v3 > 6/15 Test #12: compare_PigLatinTest_v3 . Passed0.01 sec > 7/15 Test #13: compile_PadaukTest_v3 ... Passed0.21 sec > Start 14: GrcRegressionTest_PadaukTest_v3 > Start 15: compare_PadaukTest_v3 > 8/15 Test #14: GrcRegressionTest_PadaukTest_v3 . Passed0.00 sec > 9/15 Test #15: compare_PadaukTest_v3 ... Passed0.01 sec > 10/15 Test #1: compile_SchTest . Passed0.31 sec > Start 2: GrcRegressionTest_SchTest > Start 3: compare_SchTest > 11/15 Test #2: GrcRegressionTest_SchTest ... Passed0.00 sec > 12/15 Test #3: compare_SchTest . Passed0.01 sec > 13/15 Test #4: compile_CharisTest .. Passed2.03 sec > Start 5: GrcRegressionTest_CharisTest > Start 6: compare_CharisTest > 14/15 Test #5: GrcRegressionTest_CharisTest Passed0.00 sec > 15/15 Test #6: compare_CharisTest .. Passed0.01 sec > > 93% tests passed, 1 tests failed out of 15 > > Total Test time (real) = 2.04 sec > > The following tests FAILED: > 9 - compare_PigLatinTest_v2 (Failed) > Errors while running CTest > make[1]: *** [Makefile:140: test] Error 8 > make[1]: Leaving directory '/<>/obj-x86_64-linux-gnu' > dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j4 test ARGS\+=-j4 > returned exit code 2 The full build log is available from: http://qa-logs.debian.net/2021/01/20/grcompiler_5.2-2.1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with me so that we can identify if something relevant changed in the meantime. About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures.
Bug#980698: golang-github-cznic-sortutil: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 1 github.com/cznic/sortutil returned exit code 1
Source: golang-github-cznic-sortutil Version: 0.0~git20150617.0.4c73428-2 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20210120 ftbfs-bullseye 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: warning: Compatibility levels before 10 are deprecated (level 9 in use) >dh_update_autotools_config -O--buildsystem=golang >dh_auto_configure -O--buildsystem=golang > dh_auto_configure: warning: Compatibility levels before 10 are deprecated > (level 9 in use) >dh_auto_build -O--buildsystem=golang > dh_auto_build: warning: Compatibility levels before 10 are deprecated (level > 9 in use) > cd obj-x86_64-linux-gnu && go install -trimpath -v -p 1 > github.com/cznic/sortutil > internal/unsafeheader > internal/cpu > internal/bytealg > runtime/internal/atomic > runtime/internal/sys > runtime/internal/math > runtime > internal/reflectlite > errors > internal/race > sync/atomic > sync > io > unicode > unicode/utf8 > bytes > math/bits > math > strconv > reflect > encoding/binary > sort > internal/fmtsort > internal/oserror > syscall > internal/syscall/unix > time > internal/poll > internal/syscall/execenv > internal/testlog > os > fmt > math/rand > strings > math/big > github.com/cznic/sortutil >dh_auto_test -O--buildsystem=golang > dh_auto_test: warning: Compatibility levels before 10 are deprecated (level 9 > in use) > cd obj-x86_64-linux-gnu && go test -vet=off -v -p 1 > github.com/cznic/sortutil > # github.com/cznic/sortutil > src/github.com/cznic/sortutil/all_test.go:17:2: code in directory > /<>/obj-x86_64-linux-gnu/src/github.com/cznic/mathutil expects > import "modernc.org/mathutil" > FAIL github.com/cznic/sortutil [setup failed] > FAIL > dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 1 > github.com/cznic/sortutil returned exit code 1 The full build log is available from: http://qa-logs.debian.net/2021/01/20/golang-github-cznic-sortutil_0.0~git20150617.0.4c73428-2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with me so that we can identify if something relevant changed in the meantime. About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures.
Bug#980696: ceres-solver: FTBFS: make[3]: *** No rule to make target '/usr/lib/x86_64-linux-gnu/libunwind.so', needed by 'bin/visibility_based_preconditioner_test'. Stop.
Source: ceres-solver Version: 1.14.0-13 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20210120 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[3]: Entering directory '/<>/obj-x86_64-linux-gnu' > make[3]: *** No rule to make target '/usr/lib/x86_64-linux-gnu/libunwind.so', > needed by 'bin/visibility_based_preconditioner_test'. Stop. > make[3]: *** Waiting for unfinished jobs > [ 39%] Building CXX object > internal/ceres/CMakeFiles/visibility_based_preconditioner_test.dir/visibility_based_preconditioner_test.cc.o > cd /<>/obj-x86_64-linux-gnu/internal/ceres && /usr/bin/c++ > -DCERES_CXSPARSE_VERSION=\"3.2.0\" -DCERES_GFLAGS_NAMESPACE=google > -DCERES_SUITESPARSE_VERSION=\"5.8.1\" -DGFLAGS_IS_A_DLL=0 > -DGOOGLE_GLOG_DLL_DECL="" -DGOOGLE_GLOG_DLL_DECL_FOR_UNITTESTS="" > -I/<>/obj-x86_64-linux-gnu/config -I/<>/include > -I/<>/internal -I/<>/internal/ceres > -I/usr/include/suitesparse -isystem /usr/include/eigen3 -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fopenmp > -Wno-unknown-pragmas -Wno-sign-compare -Wno-unused-parameter > -Wno-missing-field-initializers -O3 -DNDEBUG -o > CMakeFiles/visibility_based_preconditioner_test.dir/visibility_based_preconditioner_test.cc.o > -c /<>/internal/ceres/visibility_based_preconditioner_test.cc > make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu' > make[2]: *** [CMakeFiles/Makefile2:501: > internal/ceres/CMakeFiles/thread_pool_test.dir/all] Error 2 The full build log is available from: http://qa-logs.debian.net/2021/01/20/ceres-solver_1.14.0-13_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with me so that we can identify if something relevant changed in the meantime. About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures.
Bug#980692: dask: FTBFS: dh_sphinxdoc: error: debian/python-dask-doc/usr/share/doc/python-dask-doc/html/_static/js/html5shiv.min.js is missing
Source: dask Version: 2.11.0+dfsg-3 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20210120 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > fakeroot debian/rules binary > dh binary --with python3,sphinxdoc --buildsystem=pybuild >dh_testroot -O--buildsystem=pybuild >dh_prep -O--buildsystem=pybuild >dh_auto_install -O--buildsystem=pybuild > I: pybuild base:232: /usr/bin/python3 setup.py install --root > /<>/debian/python3-dask > running install > running build > running build_py > running egg_info > writing dask.egg-info/PKG-INFO > writing dependency_links to dask.egg-info/dependency_links.txt > writing requirements to dask.egg-info/requires.txt > writing top-level names to dask.egg-info/top_level.txt > reading manifest file 'dask.egg-info/SOURCES.txt' > reading manifest template 'MANIFEST.in' > writing manifest file 'dask.egg-info/SOURCES.txt' > UPDATING /<>/.pybuild/cpython3_3.9_dask/build/dask/_version.py > set /<>/.pybuild/cpython3_3.9_dask/build/dask/_version.py to > '2.11.0+dfsg' > running install_lib > creating /<>/debian/python3-dask > creating /<>/debian/python3-dask/usr > creating /<>/debian/python3-dask/usr/lib > creating /<>/debian/python3-dask/usr/lib/python3.9 > creating /<>/debian/python3-dask/usr/lib/python3.9/dist-packages > creating > /<>/debian/python3-dask/usr/lib/python3.9/dist-packages/dask > copying /<>/.pybuild/cpython3_3.9_dask/build/dask/cache.py -> > /<>/debian/python3-dask/usr/lib/python3.9/dist-packages/dask > creating > /<>/debian/python3-dask/usr/lib/python3.9/dist-packages/dask/diagnostics > copying > /<>/.pybuild/cpython3_3.9_dask/build/dask/diagnostics/profile_visualize.py > -> > /<>/debian/python3-dask/usr/lib/python3.9/dist-packages/dask/diagnostics > copying > /<>/.pybuild/cpython3_3.9_dask/build/dask/diagnostics/profile.py > -> > /<>/debian/python3-dask/usr/lib/python3.9/dist-packages/dask/diagnostics > copying > /<>/.pybuild/cpython3_3.9_dask/build/dask/diagnostics/progress.py > -> > /<>/debian/python3-dask/usr/lib/python3.9/dist-packages/dask/diagnostics > copying > /<>/.pybuild/cpython3_3.9_dask/build/dask/diagnostics/__init__.py > -> > /<>/debian/python3-dask/usr/lib/python3.9/dist-packages/dask/diagnostics > creating > /<>/debian/python3-dask/usr/lib/python3.9/dist-packages/dask/diagnostics/tests > copying > /<>/.pybuild/cpython3_3.9_dask/build/dask/diagnostics/tests/__init__.py > -> > /<>/debian/python3-dask/usr/lib/python3.9/dist-packages/dask/diagnostics/tests > copying > /<>/.pybuild/cpython3_3.9_dask/build/dask/diagnostics/tests/test_progress.py > -> > /<>/debian/python3-dask/usr/lib/python3.9/dist-packages/dask/diagnostics/tests > copying > /<>/.pybuild/cpython3_3.9_dask/build/dask/diagnostics/tests/test_profiler.py > -> > /<>/debian/python3-dask/usr/lib/python3.9/dist-packages/dask/diagnostics/tests > copying /<>/.pybuild/cpython3_3.9_dask/build/dask/distributed.py > -> /<>/debian/python3-dask/usr/lib/python3.9/dist-packages/dask > copying > /<>/.pybuild/cpython3_3.9_dask/build/dask/multiprocessing.py -> > /<>/debian/python3-dask/usr/lib/python3.9/dist-packages/dask > copying /<>/.pybuild/cpython3_3.9_dask/build/dask/callbacks.py > -> /<>/debian/python3-dask/usr/lib/python3.9/dist-packages/dask > copying /<>/.pybuild/cpython3_3.9_dask/build/dask/core.py -> > /<>/debian/python3-dask/usr/lib/python3.9/dist-packages/dask > copying /<>/.pybuild/cpython3_3.9_dask/build/dask/__init__.py -> > /<>/debian/python3-dask/usr/lib/python3.9/dist-packages/dask > copying > /<>/.pybuild/cpython3_3.9_dask/build/dask/compatibility.py -> > /<>/debian/python3-dask/usr/lib/python3.9/dist-packages/dask > creating > /<>/debian/python3-dask/usr/lib/python3.9/dist-packages/dask/bag > copying /<>/.pybuild/cpython3_3.9_dask/build/dask/bag/avro.py -> > /<>/debian/python3-dask/usr/lib/python3.9/dist-packages/dask/bag > copying /<>/.pybuild/cpython3_3.9_dask/build/dask/bag/text.py -> > /<>/debian/python3-dask/usr/lib/python3.9/dist-packages/dask/bag > copying /<>/.pybuild/cpython3_3.9_dask/build/dask/bag/core.py -> > /<>/debian/python3-dask/usr/lib/python3.9/dist-packages/dask/bag > copying > /<>/.pybuild/cpython3_3.9_dask/build/dask/bag/__init__.py -> > /<>/debian/python3-dask/usr/lib/python3.9/dist-packages/das
Bug#980695: tellico: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j1 test XDG_DATA_DIRS=/<>/test_root/usr/share:/usr/local/share:/usr/share HOME=/tmp/tellico-home.OAHYcd T
Source: tellico Version: 3.3.4-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20210120 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[2]: Entering directory '/<>/obj-x86_64-linux-gnu' > Running tests... > /usr/bin/ctest --force-new-ctest-process -j1 > Test project /<>/obj-x86_64-linux-gnu > Start 1: entitytest > 1/36 Test #1: entitytest ... Passed0.01 sec > Start 2: cuecattest > 2/36 Test #2: cuecattest ... Passed0.01 sec > Start 3: isbntest > 3/36 Test #3: isbntest . Passed0.01 sec > Start 4: lccntest > 4/36 Test #4: lccntest . Passed0.00 sec > Start 5: lcctest > 5/36 Test #5: lcctest .. Passed0.01 sec > Start 6: formattest > 6/36 Test #6: formattest ... Passed0.01 sec > Start 7: fieldtest > 7/36 Test #7: fieldtest Passed0.01 sec > Start 8: imagetest > 8/36 Test #8: imagetest Passed0.02 sec > Start 9: imagejobtest > 9/36 Test #9: imagejobtest . Passed0.03 sec > Start 10: iso6937test > 10/36 Test #10: iso6937test .. Passed0.00 sec > Start 11: iso5426test > 11/36 Test #11: iso5426test .. Passed0.01 sec > Start 12: collectiontest > 12/36 Test #12: collectiontest ... Passed0.61 sec > Start 13: comparisontest > 13/36 Test #13: comparisontest ...***Failed0.02 sec > * Start testing of ComparisonTest * > Config: Using QtTest library 5.15.2, Qt 5.15.2 (x86_64-little_endian-lp64 > shared (dynamic) release build; by GCC 10.2.1 20201207), debian unknown > PASS : ComparisonTest::initTestCase() > PASS : ComparisonTest::testNumber(null) > PASS : ComparisonTest::testNumber(< 0) > PASS : ComparisonTest::testNumber(> 0) > PASS : ComparisonTest::testNumber(=1 1) > PASS : ComparisonTest::testNumber(< 1) > PASS : ComparisonTest::testNumber(> 1) > PASS : ComparisonTest::testNumber(> -1) > PASS : ComparisonTest::testNumber(< -1) > PASS : ComparisonTest::testNumber(> 10) > PASS : ComparisonTest::testNumber(< 10) > PASS : ComparisonTest::testNumber(multiple1) > PASS : ComparisonTest::testNumber(multiple2) > PASS : ComparisonTest::testNumber(multiple3) > PASS : ComparisonTest::testNumber(multiple4) > PASS : ComparisonTest::testNumber(float1) > PASS : ComparisonTest::testNumber(float2) > PASS : ComparisonTest::testNumber(float3) > PASS : ComparisonTest::testNumber(float4) > PASS : ComparisonTest::testLCC(null) > PASS : ComparisonTest::testLCC(null1) > PASS : ComparisonTest::testLCC(null2) > PASS : ComparisonTest::testLCC(test1) > PASS : ComparisonTest::testLCC(test2) > PASS : ComparisonTest::testLCC(test3) > PASS : ComparisonTest::testDate(null) > PASS : ComparisonTest::testDate(null1) > PASS : ComparisonTest::testDate(null2) > PASS : ComparisonTest::testDate(test1) > PASS : ComparisonTest::testDate(test2) > PASS : ComparisonTest::testDate(test3) > PASS : ComparisonTest::testDate(test5) > PASS : ComparisonTest::testDate(words) > FAIL! : ComparisonTest::testDate(words) Compared values are not the same >Actual (comp.compare(string1, string2)): -1 >Expected (res) : 0 >Loc: [/<>/src/tests/comparisontest.cpp(105)] > PASS : ComparisonTest::testTitle(null) > PASS : ComparisonTest::testTitle(null1) > PASS : ComparisonTest::testTitle(null2) > PASS : ComparisonTest::testTitle(test3) > PASS : ComparisonTest::testTitle(test4) > PASS : ComparisonTest::testTitle(test5) > PASS : ComparisonTest::testTitle(test6) > PASS : ComparisonTest::testTitle(test7) > PASS : ComparisonTest::testString(null) > PASS : ComparisonTest::testString(null1) > PASS : ComparisonTest::testString(null2) > PASS : ComparisonTest::testString(test1) > PASS : ComparisonTest::testString(test2) > PASS : ComparisonTest::testBool(null) > PASS : ComparisonTest::testBool(null1) > PASS : ComparisonTest::testBool(null2) > PASS : ComparisonTest::testBool(truetrue) > PASS : ComparisonTest::testBool(truefalse) > PASS : ComparisonTest::testBool(falsetrue) > PASS : ComparisonTest::testChoiceField() > PASS : ComparisonTest::cleanupTestCase() > Totals: 54 passed, 1 failed, 0 skipped, 0 blacklisted, 3ms > * Fini
Bug#980694: sfepy: FTBFS: Signal: Aborted (6)
Source: sfepy Version: 2019.4-2.1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20210120 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[3]: Entering directory '/<>/doc' > PYTHONPATH=.. sphinx-build -b html -d _build/doctrees . _build/html > Running Sphinx v3.4.3 > making output directory... done > building [mo]: targets for 0 po files that are out of date > building [html]: targets for 230 source files that are out of date > updating environment: [new config] 232 added, 0 changed, 0 removed > reading sources... [ 0%] archived_news > reading sources... [ 0%] archived_support > reading sources... [ 1%] developer_guide > reading sources... [ 1%] development > reading sources... [ 2%] downloads > reading sources... [ 2%] ebcs_implementation > reading sources... [ 3%] examples > reading sources... [ 3%] index > reading sources... [ 3%] installation > reading sources... [ 4%] introduction > reading sources... [ 4%] license > reading sources... [ 5%] linear_combination_bc > reading sources... [ 5%] manpages > reading sources... [ 6%] mat_optim > reading sources... [ 6%] mat_optim/homogenization_opt_src > reading sources... [ 6%] mat_optim/linear_elasticity_opt_src > reading sources... [ 7%] mat_optim/material_opt_src > reading sources... [ 7%] news > reading sources... [ 8%] preprocessing > reading sources... [ 8%] primer > reading sources... [ 9%] problem_desc_file_long > reading sources... [ 9%] release_notes > reading sources... [ 9%] release_tasks > reading sources... [ 10%] solver_table > reading sources... [ 10%] solving_pdes_by_fem > reading sources... [ 11%] splinebox > reading sources... [ 11%] src/build_helpers > reading sources... [ 12%] src/extractor > reading sources... [ 12%] src/homogen > reading sources... [ 12%] src/phonon > A process has executed an operation involving a call > to the fork() system call to create a child process. > > As a result, the libfabric EFA provider is operating in > a condition that could result in memory corruption or > other system errors. > > For the libfabric EFA provider to work safely when fork() > is called, you will need to set the following environment > variable: > RDMAV_FORK_SAFE > > However, setting this environment variable can result in > signficant performance impact to your application due to > increased cost of memory registration. > > You may want to check with your application vendor to see > if an application-level alternative (of not using fork) > exists. > > Your job will now abort. > [ip-172-31-13-40:07422] *** Process received signal *** > [ip-172-31-13-40:07422] Signal: Aborted (6) > [ip-172-31-13-40:07422] Signal code: (-6) > [ip-172-31-13-40:07422] [ 0] > /lib/x86_64-linux-gnu/libpthread.so.0(+0x14140)[0x7fc5caa9e140] > [ip-172-31-13-40:07422] [ 1] > /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x141)[0x7fc5ca763ce1] > [ip-172-31-13-40:07422] [ 2] > /lib/x86_64-linux-gnu/libc.so.6(abort+0x123)[0x7fc5ca74d537] > [ip-172-31-13-40:07422] [ 3] > /usr/lib/x86_64-linux-gnu/libfabric.so.1(+0x7c14e)[0x7fc5b930314e] > [ip-172-31-13-40:07422] [ 4] > /lib/x86_64-linux-gnu/libc.so.6(+0x85228)[0x7fc5ca7ad228] > [ip-172-31-13-40:07422] [ 5] > /lib/x86_64-linux-gnu/libc.so.6(__libc_fork+0x20)[0x7fc5ca7f3490] > [ip-172-31-13-40:07422] [ 6] /usr/bin/python3[0x65306b] > [ip-172-31-13-40:07422] [ 7] /usr/bin/python3[0x53f65a] > [ip-172-31-13-40:07422] [ 8] > /usr/bin/python3(_PyObject_MakeTpCall+0x39b)[0x51db7b] > [ip-172-31-13-40:07422] [ 9] > /usr/bin/python3(_PyEval_EvalFrameDefault+0x5b10)[0x5177f0] > [ip-172-31-13-40:07422] [10] /usr/bin/python3[0x511237] > [ip-172-31-13-40:07422] [11] > /usr/bin/python3(_PyFunction_Vectorcall+0x361)[0x529051] > [ip-172-31-13-40:07422] [12] > /usr/bin/python3(_PyEval_EvalFrameDefault+0x701)[0x5123e1] > [ip-172-31-13-40:07422] [13] /usr/bin/python3[0x511237] > [ip-172-31-13-40:07422] [14] > /usr/bin/python3(_PyFunction_Vectorcall+0x361)[0x529051] > [ip-172-31-13-40:07422] [15] /usr/bin/python3[0x537a8e] > [ip-172-31-13-40:07422] [16] /usr/bin/python3[0x51e0bf] > [ip-172-31-13-40:07422] [17] /usr/bin/python3(PyObject_Call+0x129)[0x53c679] > [ip-172-31-13-40:07422] [18] > /usr/bin/python3(_PyEval_EvalFrameDefault+0x23ef)[0x5140cf] > [ip-172-31-13-40:07422] [19] /usr/bin/python3[0x511237] > [ip-172-31-13-40:07422] [20] > /usr/bin/python3(_PyFunction_Vectorcall+0x361)[0x529051] > [ip-172-31-13-40:07422] [21] /usr/bin/python3(PyObject_Call+0xc1)[0x53c611] > [ip-172-31-13-40:07422] [22] > /usr/bin/python3(_PyEval_EvalFrameDefault+0x23ef)[0x5
Bug#980693: felix-latin: FTBFS: latex error
Source: felix-latin
Version: 2.0-11.1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210120 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[2]: Entering directory '/<>/TeX'
> xelatex felix34.tex
> This is XeTeX, Version 3.14159265-2.6-0.92 (TeX Live 2020/Debian)
> (preloaded format=xelatex)
> restricted \write18 enabled.
> entering extended mode
> (./felix34.tex
> LaTeX2e <2020-10-01> patch level 4
> L3 programming layer <2021-01-09> xparse <2020-03-03>
> (/usr/share/texlive/texmf-dist/tex/latex/base/article.cls
> Document Class: article 2020/04/10 v1.4m Standard LaTeX document class
> (/usr/share/texlive/texmf-dist/tex/latex/base/size12.clo))
> (/usr/share/texlive/texmf-dist/tex/latex/fontspec/fontspec.sty
> (/usr/share/texlive/texmf-dist/tex/latex/l3packages/xparse/xparse.sty
> (/usr/share/texlive/texmf-dist/tex/latex/l3kernel/expl3.sty
> (/usr/share/texlive/texmf-dist/tex/latex/l3backend/l3backend-xetex.def
> (|extractbb --version))
> Runaway argument?
> \q_stop <\__int_eval:w \c_zero_int \__int_eval_end: \exp_after:wN \use_ii:nnn
> \
> ETC.
> ! File ended while scanning use of \__sys_tmp:w.
>
> \par
> l.148 { \sys_load_backend:n { } }
>
> ?
> ! Emergency stop.
>
> \par
> l.148 { \sys_load_backend:n { } }
>
> No pages of output.
> Transcript written on felix34.log.
> make[2]: *** [Makefile:3: tout] Error 1
The full build log is available from:
http://qa-logs.debian.net/2021/01/20/felix-latin_2.0-11.1_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with me
so that we can identify if something relevant changed in the meantime.
About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
Bug#980691: gnome-software: FTBFS: dh_auto_configure: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc --localstatedir
Source: gnome-software Version: 3.38.0-3 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20210120 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_auto_configure -- -Dgnome_desktop=true -Dodrs=true -Dostree=false > -Dpackagekit=true -Dpackagekit_autoremove=true -Drpm_ostree=false > -Dubuntu_reviews=false -Dfwupd=false -Dflatpak=false -Dgudev=false > -Dmalcontent=false -Dvalgrind=false -Dflatpak=true -Dmalcontent=true > -Dgudev=true -Dfwupd=true -Dsnap=true -Dvalgrind=true > cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. > --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc > --localstatedir=/var --libdir=lib/x86_64-linux-gnu -Dgnome_desktop=true > -Dodrs=true -Dostree=false -Dpackagekit=true -Dpackagekit_autoremove=true > -Drpm_ostree=false -Dubuntu_reviews=false -Dfwupd=false -Dflatpak=false > -Dgudev=false -Dmalcontent=false -Dvalgrind=false -Dflatpak=true > -Dmalcontent=true -Dgudev=true -Dfwupd=true -Dsnap=true -Dvalgrind=true > The Meson build system > Version: 0.56.2 > Source dir: /<> > Build dir: /<>/obj-x86_64-linux-gnu > Build type: native build > WARNING: Unknown options: "ostree, ubuntu_reviews" > The value of new options can be set with: > meson setup --reconfigure -Dnew_option=new_value ... > Project name: gnome-software > Project version: 3.38.0 > Using 'CFLAGS' from environment with value: '-g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security' > Using 'LDFLAGS' from environment with value: '-Wl,-z,relro -Wl,-z,now -Wl,-O1 > -Wl,--as-needed' > Using 'CPPFLAGS' from environment with value: '-Wdate-time > -D_FORTIFY_SOURCE=2' > C compiler for the host machine: cc (gcc 10.2.1 "cc (Debian 10.2.1-6) 10.2.1 > 20210110") > C linker for the host machine: cc ld.bfd 2.35.1 > Using 'CFLAGS' from environment with value: '-g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security' > Using 'LDFLAGS' from environment with value: '-Wl,-z,relro -Wl,-z,now -Wl,-O1 > -Wl,--as-needed' > Using 'CPPFLAGS' from environment with value: '-Wdate-time > -D_FORTIFY_SOURCE=2' > Host machine cpu family: x86_64 > Host machine cpu: x86_64 > Compiler for C supports arguments -fstack-protector-strong: YES > Compiler for C supports arguments -Waggregate-return: YES > Compiler for C supports arguments -Warray-bounds: YES > Compiler for C supports arguments -Wcast-align: YES > Compiler for C supports arguments -Wclobbered: YES > Compiler for C supports arguments -Wdeclaration-after-statement: YES > Compiler for C supports arguments -Wempty-body: YES > Compiler for C supports arguments -Wextra: YES > ../meson.build:73: WARNING: Consider using the built-in warning_level option > instead of using "-Wextra". > Compiler for C supports arguments -Wformat=2: YES > Compiler for C supports arguments -Wformat-nonliteral: YES > Compiler for C supports arguments -Wformat-security: YES > Compiler for C supports arguments -Wformat-signedness: YES > Compiler for C supports arguments -Wignored-qualifiers: YES > Compiler for C supports arguments -Wimplicit-function-declaration: YES > Compiler for C supports arguments -Werror=implicit-function-declaration: YES > Compiler for C supports arguments -Winit-self: YES > Compiler for C supports arguments -Winline: YES > Compiler for C supports arguments -Wmissing-declarations: YES > Compiler for C supports arguments -Wmissing-format-attribute: YES > Compiler for C supports arguments -Wmissing-include-dirs: YES > Compiler for C supports arguments -Wmissing-noreturn: YES > Compiler for C supports arguments -Wmissing-parameter-type: YES > Compiler for C supports arguments -Wmissing-prototypes: YES > Compiler for C supports arguments -Wnested-externs: YES > Compiler for C supports arguments -Werror=nested-externs: YES > Compiler for C supports arguments -Wno-discarded-qualifiers: YES > Compiler for C supports arguments -Wno-missing-field-initializers: YES > Compiler for C supports arguments -Wno-strict-aliasing: YES > Compiler for C supports arguments -Wno-suggest-attribute=format: YES > Compiler for C supports arguments -Wno-unused-parameter: YES > Compiler for C supports arguments -Wold-style-definition: YES > Compiler for C supports arguments -Woverride-init: YES > Compiler for C supports arguments -Wpacked: YES > Compiler for C supports arguments -Wpointer-arith: YES > Compiler for C supports arguments -Wredundant-decls: YES > Compiler for C supports arguments -Wreturn-type: YE
Bug#980688: seaborn: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13
Source: seaborn Version: 0.10.1-2 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20210120 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > xvfb-run --auto-servernum --server-num=20 dh_auto_test override_dh_auto_test > I: pybuild base:232: cd /<>/.pybuild/cpython3_3.9_seaborn/build; > python3.9 -m pytest > = test session starts > == > platform linux -- Python 3.9.1+, pytest-6.0.2, py-1.10.0, pluggy-0.13.0 > rootdir: /<>, configfile: pytest.ini > collected 591 items > > seaborn/tests/test_algorithms.py ss [ > 3%] > seaborn/tests/test_axisgrid.py . [ > 9%] > .[ > 18%] > seaborn/tests/test_categorical.py .. [ > 24%] > [ > 36%] > [ > 40%] > seaborn/tests/test_distributions.py s.ss..ss.. [ > 43%] > seaborn/tests/test_matrix.py ... [ > 50%] > ss...[ > 57%] > seaborn/tests/test_miscplot.py .s[ > 57%] > seaborn/tests/test_palettes.py [ > 63%] > seaborn/tests/test_rcmod.py ...s.s [ > 67%] > seaborn/tests/test_regression.py ss.ss.. [ > 74%] > .s.. [ > 76%] > seaborn/tests/test_relational.py ... [ > 82%] > [ > 92%] > seaborn/tests/test_utils.py F.ss [ > 99%] > s > [100%] > > === FAILURES > === > test_locator_to_legend_entries > > > def test_locator_to_legend_entries(): > > locator = mpl.ticker.MaxNLocator(nbins=3) > limits = (0.09, 0.4) > levels, str_levels = utils.locator_to_legend_entries( > locator, limits, float > ) > assert str_levels == ["0.00", "0.15", "0.30", "0.45"] > > limits = (0.8, 0.9) > levels, str_levels = utils.locator_to_legend_entries( > locator, limits, float > ) > assert str_levels == ["0.80", "0.84", "0.88", "0.92"] > > limits = (1, 6) > levels, str_levels = utils.locator_to_legend_entries(locator, limits, > int) > assert str_levels == ["0", "2", "4", "6"] > > locator = mpl.ticker.LogLocator(numticks=3) > limits = (5, 1425) > levels, str_levels = utils.locator_to_legend_entries(locator, limits, > int) > if LooseVersion(mpl.__version__) >= "3.1": > > assert str_levels == ['0', '1', '100', '1', '1e+06'] > E AssertionError: assert ['0', '1', '1... '1', ...] == ['0', > '1', '1...000', '1e+06'] > E At index 2 diff: '10' != '100' > E Left contains 2 more items, first extra item: '1' > E Use -v to get the full diff > > seaborn/tests/test_utils.py:395: AssertionError > === warnings summary > === > .pybuild/cpython3_3.9_seaborn/build/seaborn/tests/test_axisgrid.py::TestFacetGrid::test_set_ticklabels > > /<>/.pybuild/cpython3_3.9_seaborn/build/seaborn/axisgrid.py:936: > UserWarning: FixedFormatter should only be used together with FixedLocator > ax.set_yticklabels(labels, **kwargs) > > .pybuild/cpython3_3.9_seaborn/build/seaborn/tests/test_axisgrid.py::TestFacetGrid::test_set_ticklabels > > /<>/.pybuild/cpython3_3.9_seaborn/build/seaborn/axisgrid.py:924: > UserWarning: FixedFormatter should only be used together with FixedLocator > ax.set_xticklabels(curr_labels, **kwargs) > > .pybuild/cpython3_3.9_seaborn/build/seaborn/tests/test_axisgrid.py::TestFacetGrid::test_set_ticklabels > > /
Bug#980686: ldc: FTBFS: dh_auto_configure: error: cd bootstrap-stage2 && cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var -D
Source: ldc Version: 1:1.24.0-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20210120 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[4]: Entering directory '/<>/bootstrap-stage1' > [ 93%] Linking C shared library ../lib/libphobos2-ldc-shared.so > cd /<>/bootstrap-stage1/runtime && /usr/bin/cmake -E > cmake_link_script CMakeFiles/phobos2-ldc-shared.dir/link.txt --verbose=1 > /usr/bin/cc -fPIC -g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > -D_FORTIFY_SOURCE=2 -Wdate-time -D_FORTIFY_SOURCE=2 -DHAVE_UNISTD_H > -Wl,-z,relro -shared -Wl,-soname,libphobos2-ldc-shared.so.94 -o > ../lib/libphobos2-ldc-shared.so.2.0.94 objects/etc/c/curl.o > objects/etc/c/odbc/sql.o objects/etc/c/odbc/sqlext.o > objects/etc/c/odbc/sqltypes.o objects/etc/c/odbc/sqlucode.o > objects/etc/c/sqlite3.o objects/etc/c/zlib.o > objects/std/algorithm/comparison.o objects/std/algorithm/internal.o > objects/std/algorithm/iteration.o objects/std/algorithm/mutation.o > objects/std/algorithm/package.o objects/std/algorithm/searching.o > objects/std/algorithm/setops.o objects/std/algorithm/sorting.o > objects/std/array.o objects/std/ascii.o objects/std/base64.o > objects/std/bigint.o objects/std/bitmanip.o objects/std/compiler.o > objects/std/complex.o objects/std/concurrency.o objects/std/container/array.o > objects/std/container/binaryheap.o objects/std/container/dlist.o > objects/std/container/package.o objects/std/container/rbtree.o > objects/std/container/slist.o objects/std/container/util.o objects/std/conv.o > objects/std/csv.o objects/std/datetime/date.o objects/std/datetime/interval.o > objects/std/datetime/package.o objects/std/datetime/stopwatch.o > objects/std/datetime/systime.o objects/std/datetime/timezone.o > objects/std/demangle.o objects/std/digest/crc.o objects/std/digest/digest.o > objects/std/digest/hmac.o objects/std/digest/md.o > objects/std/digest/murmurhash.o objects/std/digest/package.o > objects/std/digest/ripemd.o objects/std/digest/sha.o objects/std/encoding.o > objects/std/exception.o > objects/std/experimental/allocator/building_blocks/affix_allocator.o > objects/std/experimental/allocator/building_blocks/aligned_block_list.o > objects/std/experimental/allocator/building_blocks/allocator_list.o > objects/std/experimental/allocator/building_blocks/ascending_page_allocator.o > objects/std/experimental/allocator/building_blocks/bitmapped_block.o > objects/std/experimental/allocator/building_blocks/bucketizer.o > objects/std/experimental/allocator/building_blocks/fallback_allocator.o > objects/std/experimental/allocator/building_blocks/free_list.o > objects/std/experimental/allocator/building_blocks/free_tree.o > objects/std/experimental/allocator/building_blocks/kernighan_ritchie.o > objects/std/experimental/allocator/building_blocks/null_allocator.o > objects/std/experimental/allocator/building_blocks/package.o > objects/std/experimental/allocator/building_blocks/quantizer.o > objects/std/experimental/allocator/building_blocks/region.o > objects/std/experimental/allocator/building_blocks/scoped_allocator.o > objects/std/experimental/allocator/building_blocks/segregator.o > objects/std/experimental/allocator/building_blocks/stats_collector.o > objects/std/experimental/allocator/common.o > objects/std/experimental/allocator/gc_allocator.o > objects/std/experimental/allocator/mallocator.o > objects/std/experimental/allocator/mmap_allocator.o > objects/std/experimental/allocator/package.o > objects/std/experimental/allocator/showcase.o > objects/std/experimental/allocator/typed.o > objects/std/experimental/checkedint.o objects/std/experimental/logger/core.o > objects/std/experimental/logger/filelogger.o > objects/std/experimental/logger/multilogger.o > objects/std/experimental/logger/nulllogger.o > objects/std/experimental/logger/package.o objects/std/experimental/typecons.o > objects/std/file.o objects/std/format.o objects/std/functional.o > objects/std/getopt.o objects/std/internal/attributes.o > objects/std/internal/cstring.o objects/std/internal/digest/sha_SSSE3.o > objects/std/internal/math/biguintarm.o > objects/std/internal/math/biguintcore.o > objects/std/internal/math/biguintnoasm.o > objects/std/internal/math/biguintx86.o > objects/std/internal/math/errorfunction.o > objects/std/internal/math/gammafunction.o objects/std/internal/memory.o > objects/std/internal/scopebuffer.o objects/std/internal/test/dummyrange.o > objects/std/internal/test/range.o objects/std/internal/test/uda.o > objects/std/internal/unicode_comp.o objects
Bug#980687: checkstyle: FTBFS: Failed to execute goal org.antlr:antlr4-maven-plugin:4.7.2:antlr4
Source: checkstyle Version: 8.34-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20210120 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_auto_build > /usr/lib/jvm/default-java/bin/java -noverify -cp > /usr/share/maven/boot/plexus-classworlds-2.x.jar > -Dmaven.home=/usr/share/maven > -Dmaven.multiModuleProjectDirectory=/<> > -Dclassworlds.conf=/etc/maven/m2-debian.conf > -Dproperties.file.manual=/<>/debian/maven.properties > org.codehaus.plexus.classworlds.launcher.Launcher > -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian > -Dmaven.repo.local=/<>/debian/maven-repo --batch-mode package > javadoc:jar javadoc:aggregate -DskipTests -Dnotimestamp=true -Dlocale=en_US > [INFO] Scanning for projects... > [WARNING] The POM for > org.apache.maven.plugins:maven-checkstyle-plugin:jar:3.1.1 is missing, no > dependency information available > [WARNING] Failed to retrieve plugin descriptor for > org.apache.maven.plugins:maven-checkstyle-plugin:3.1.1: Plugin > org.apache.maven.plugins:maven-checkstyle-plugin:3.1.1 or one of its > dependencies could not be resolved: Cannot access nexus-codehaus-snapshot > (https://oss.sonatype.org/content/repositories/codehaus-snapshots/) in > offline mode and the artifact > org.apache.maven.plugins:maven-checkstyle-plugin:jar:3.1.1 has not been > downloaded from it before. > [WARNING] The POM for org.apache.maven.plugins:maven-install-plugin:jar:2.4 > is missing, no dependency information available > [WARNING] Failed to retrieve plugin descriptor for > org.apache.maven.plugins:maven-install-plugin:2.4: Plugin > org.apache.maven.plugins:maven-install-plugin:2.4 or one of its dependencies > could not be resolved: Cannot access nexus-codehaus-snapshot > (https://oss.sonatype.org/content/repositories/codehaus-snapshots/) in > offline mode and the artifact > org.apache.maven.plugins:maven-install-plugin:jar:2.4 has not been downloaded > from it before. > [WARNING] The POM for org.apache.maven.plugins:maven-deploy-plugin:jar:2.7 is > missing, no dependency information available > [WARNING] Failed to retrieve plugin descriptor for > org.apache.maven.plugins:maven-deploy-plugin:2.7: Plugin > org.apache.maven.plugins:maven-deploy-plugin:2.7 or one of its dependencies > could not be resolved: Cannot access nexus-codehaus-snapshot > (https://oss.sonatype.org/content/repositories/codehaus-snapshots/) in > offline mode and the artifact > org.apache.maven.plugins:maven-deploy-plugin:jar:2.7 has not been downloaded > from it before. > [WARNING] The POM for > org.apache.maven.plugins:maven-assembly-plugin:jar:3.3.0 is missing, no > dependency information available > [WARNING] Failed to retrieve plugin descriptor for > org.apache.maven.plugins:maven-assembly-plugin:3.3.0: Plugin > org.apache.maven.plugins:maven-assembly-plugin:3.3.0 or one of its > dependencies could not be resolved: Cannot access nexus-codehaus-snapshot > (https://oss.sonatype.org/content/repositories/codehaus-snapshots/) in > offline mode and the artifact > org.apache.maven.plugins:maven-assembly-plugin:jar:3.3.0 has not been > downloaded from it before. > [WARNING] The POM for > org.apache.maven.plugins:maven-dependency-plugin:jar:3.1.2 is missing, no > dependency information available > [WARNING] Failed to retrieve plugin descriptor for > org.apache.maven.plugins:maven-dependency-plugin:3.1.2: Plugin > org.apache.maven.plugins:maven-dependency-plugin:3.1.2 or one of its > dependencies could not be resolved: Cannot access nexus-codehaus-snapshot > (https://oss.sonatype.org/content/repositories/codehaus-snapshots/) in > offline mode and the artifact > org.apache.maven.plugins:maven-dependency-plugin:jar:3.1.2 has not been > downloaded from it before. > [WARNING] The POM for org.apache.maven.plugins:maven-release-plugin:jar:2.1 > is missing, no dependency information available > [WARNING] Failed to retrieve plugin descriptor for > org.apache.maven.plugins:maven-release-plugin:2.1: Plugin > org.apache.maven.plugins:maven-release-plugin:2.1 or one of its dependencies > could not be resolved: Cannot access nexus-codehaus-snapshot > (https://oss.sonatype.org/content/repositories/codehaus-snapshots/) in > offline mode and the artifact > org.apache.maven.plugins:maven-release-plugin:jar:2.1 has not been downloaded > from it before. > [WARNING] The POM for org.codehaus.mojo:sonar-maven-plugin:jar:3.7.0.1746 is > missing, no dependency information available > [WARNING] Failed to retrieve plugin descriptor for > org.codehaus.mojo
Bug#980685: seqan: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j4 test ARGS\+=-j4 returned exit code 2
Source: seqan Version: 1.4.2+dfsg-4 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20210120 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[2]: Entering directory '/<>/obj-x86_64-linux-gnu' > Running tests... > /usr/bin/ctest --force-new-ctest-process -j4 > Test project /<>/obj-x86_64-linux-gnu > Start 1: test_demo_align_align > Start 2: test_demo_align_compute_alignment_stats > Start 3: test_demo_align_gaps_example > Start 4: test_demo_align_global_alignment_banded > 1/93 Test #1: test_demo_align_align > .. Passed0.05 sec > Start 5: test_demo_align_global_alignment_unbanded > 2/93 Test #2: test_demo_align_compute_alignment_stats > Passed0.05 sec > Start 6: test_demo_align_integrate_align > 3/93 Test #4: test_demo_align_global_alignment_banded > Passed0.05 sec > Start 7: test_demo_bam_io_bam_stream > 4/93 Test #3: test_demo_align_gaps_example > ... Passed0.05 sec > Start 8: test_demo_find_finder_index > 5/93 Test #5: test_demo_align_global_alignment_unbanded > .. Passed0.05 sec > Start 9: test_demo_find_finder_online > 6/93 Test #6: test_demo_align_integrate_align > Passed0.05 sec > Start 10: test_demo_graph_graph_algo_dijkstra > 7/93 Test #7: test_demo_bam_io_bam_stream > ***Failed0.05 sec > Loading files "/<>/core/demos/bam_io/bam_stream.cpp.stdout", > "None". > Running /<>/obj-x86_64-linux-gnu/bin/demo_bam_io_bam_stream. > ERROR: Return code of > /<>/obj-x86_64-linux-gnu/bin/demo_bam_io_bam_stream was 1. > > Start 11: test_demo_graph_algorithms_all_pairs_shortest_path > 8/93 Test #8: test_demo_find_finder_index > Passed0.05 sec > Start 12: test_demo_graph_algorithms_bellman_ford_algorithm > 9/93 Test #9: test_demo_find_finder_online > ... Passed0.05 sec > Start 13: test_demo_graph_algorithms_breadth_first_search > 10/93 Test #10: test_demo_graph_graph_algo_dijkstra > Passed0.05 sec > Start 14: test_demo_graph_algorithms_dag_shortest_path > 11/93 Test #11: test_demo_graph_algorithms_all_pairs_shortest_path > . Passed0.05 sec > Start 15: test_demo_graph_algorithms_depth_first_search > 12/93 Test #12: test_demo_graph_algorithms_bellman_ford_algorithm > .. Passed0.05 sec > Start 16: test_demo_graph_algorithms_dijkstra > 13/93 Test #13: test_demo_graph_algorithms_breadth_first_search > Passed0.05 sec > Start 17: test_demo_graph_algorithms_floyd_warshall_algorithm > 14/93 Test #14: test_demo_graph_algorithms_dag_shortest_path > ... Passed0.05 sec > Start 18: test_demo_graph_algorithms_ford_fulkerson_algorithm > 15/93 Test #15: test_demo_graph_algorithms_depth_first_search > .. Passed0.05 sec > Start 19: test_demo_graph_algorithms_kruskals_algorithm > 16/93 Test #16: test_demo_graph_algorithms_dijkstra > Passed0.05 sec > Start 20: test_demo_graph_algorithms_prims_algorithm > 17/93 Test #17: test_demo_graph_algorithms_floyd_warshall_algorithm > Passed0.05 sec > Start 21: test_demo_graph_algorithms_strongly_connected_components > 18/93 Test #18: test_demo_graph_algorithms_ford_fulkerson_algorithm > Passed0.05 sec > Start 22: test_demo_graph_algorithms_topological_sort > 19/93 Test #19: test_demo_graph_algorithms_kruskals_algorithm > .. Passed0.05 sec > Start 23: test_demo_graph_algorithms_transitive_closure > 20/93 Test #20: test_demo_graph_algorithms_prims_algorithm > . Passed0.05 sec > Start 24: test_demo_index_index_begin_atEnd_representative > 21/93 Test #21: test_demo_graph_algorithms_strongly_connected_components > ... Passed0.05 sec > Start 25: test_demo_index_index_counting > 22/93 Test #22: test_demo_graph_algorithms_topological_sort > Passed0.05 sec > Start 26: test_demo_index_index_finder > 23/93 Test #23: test_demo_graph_algorithms_transitive_closure > ..
Bug#980684: gnome-firmware: FTBFS: dh_auto_configure: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc --localstatedir
Source: gnome-firmware Version: 3.36.0-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20210120 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > dpkg-buildpackage > - > > Command: dpkg-buildpackage -us -uc -sa -rfakeroot > dpkg-buildpackage: info: source package gnome-firmware > dpkg-buildpackage: info: source version 3.36.0-1 > dpkg-buildpackage: info: source distribution unstable > dpkg-buildpackage: info: source changed by Laurent Bigonville > > dpkg-source --before-build . > dpkg-buildpackage: info: host architecture amd64 > debian/rules clean > dh clean --with gnome >dh_gnome_clean >dh_clean > dpkg-source -b . > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-source: info: building gnome-firmware using existing > ./gnome-firmware_3.36.0.orig.tar.xz > dpkg-source: info: building gnome-firmware in > gnome-firmware_3.36.0-1.debian.tar.xz > dpkg-source: info: building gnome-firmware in gnome-firmware_3.36.0-1.dsc > debian/rules binary > dh binary --with gnome >dh_update_autotools_config >dh_autoreconf >dh_auto_configure > cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. > --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc > --localstatedir=/var --libdir=lib/x86_64-linux-gnu > The Meson build system > Version: 0.56.2 > Source dir: /<> > Build dir: /<>/obj-x86_64-linux-gnu > Build type: native build > Project name: gnome-firmware > Project version: 3.36.0 > Using 'CFLAGS' from environment with value: '-g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security' > Using 'LDFLAGS' from environment with value: '-Wl,-z,relro' > Using 'CPPFLAGS' from environment with value: '-Wdate-time > -D_FORTIFY_SOURCE=2' > C compiler for the host machine: cc (gcc 10.2.1 "cc (Debian 10.2.1-6) 10.2.1 > 20210110") > C linker for the host machine: cc ld.bfd 2.35.1 > Using 'CFLAGS' from environment with value: '-g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security' > Using 'LDFLAGS' from environment with value: '-Wl,-z,relro' > Using 'CPPFLAGS' from environment with value: '-Wdate-time > -D_FORTIFY_SOURCE=2' > Host machine cpu family: x86_64 > Host machine cpu: x86_64 > Compiler for C supports arguments -Waggregate-return: YES > Compiler for C supports arguments -Warray-bounds: YES > Compiler for C supports arguments -Wcast-align: YES > Compiler for C supports arguments -Wclobbered: YES > Compiler for C supports arguments -Wdeclaration-after-statement: YES > Compiler for C supports arguments -Wempty-body: YES > Compiler for C supports arguments -Wextra: YES > ../meson.build:60: WARNING: Consider using the built-in warning_level option > instead of using "-Wextra". > Compiler for C supports arguments -Wformat=2: YES > Compiler for C supports arguments -Wformat-security: YES > Compiler for C supports arguments -Wformat-signedness: YES > Compiler for C supports arguments -Wignored-qualifiers: YES > Compiler for C supports arguments -Wimplicit-function-declaration: YES > Compiler for C supports arguments -Winit-self: YES > Compiler for C supports arguments -Winline: YES > Compiler for C supports arguments -Wmissing-declarations: YES > Compiler for C supports arguments -Wmissing-format-attribute: YES > Compiler for C supports arguments -Wmissing-include-dirs: YES > Compiler for C supports arguments -Wmissing-noreturn: YES > Compiler for C supports arguments -Wmissing-parameter-type: YES > Compiler for C supports arguments -Wmissing-prototypes: YES > Compiler for C supports arguments -Wnested-externs: YES > Compiler for C supports arguments -Wno-discarded-qualifiers: YES > Compiler for C supports arguments -Wno-missing-field-initializers: YES > Compiler for C supports arguments -Wno-strict-aliasing: YES > Compiler for C supports arguments -Wno-suggest-attribute=format: YES > Compiler for C supports arguments -Wno-unused-parameter: YES > Compiler for C supports arguments -Wno-cast-function-type: YES > Compiler for C supports arguments -Wold-style-definition: YES > Compiler for C supports arguments -Wno-format-nonliteral: YES > Compiler for C supports arguments -Woverride-init: YES > Compiler for C supports arguments -Wpacked: YES > Compiler for C supports arguments -Wpointer-arith: YES > Compiler for C supports arguments -Wredundant-decls: YES > Compiler for C supports arguments -Wreturn-type: YES > Compiler for C supports arguments -Wshadow: YES > Compiler for C supports arguments -Wsig
Bug#980682: liblist-objects-withutils-perl: FTBFS: dh_auto_test: error: make -j1 test TEST_VERBOSE=1 returned exit code 2
Source: liblist-objects-withutils-perl Version: 2.028003-1.1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20210120 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > PERL_DL_NONLAZY=1 "/usr/bin/perl" "-MExtUtils::Command::MM" "-MTest::Harness" > "-e" "undef *Test::Harness::Switches; test_harness(1, 'blib/lib', > 'blib/arch')" t/*.t t/00_load/*.t t/01_array/*.t t/02_hash/*.t > t/03_junctions/*.t t/04_immutable/*.t t/05_typed/*.t t/06_immutable_typed/*.t > t/07_json/*.t t/08_zpl/*.t t/09_autobox_array/*.t t/09_autobox_hash/*.t > # > # Versions for all modules listed in MYMETA.json (including optional ones): > # > # === Configure Requires === > # > # Module Want Have > # --- > # ExtUtils::MakeMaker any 7.44 > # > # === Build Requires === > # > # Module Want Have > # --- > # ExtUtils::MakeMaker any 7.44 > # > # === Test Requires === > # > # Module Want Have > # --- > # ExtUtils::MakeMaker any 7.44 > # File::Spec any 3.78 > # Test::More 0.88 1.302175 > # > # === Test Recommends === > # > # ModuleWant Have > # - > # CPAN::Meta2.120900 2.150010 > # JSON::PP any 4.04 > # Test::Without::Module any 0.20 > # > # === Runtime Requires === > # > # ModuleWant Have > # - > # Carp any 1.50 > # Class::Method::Modifiers any 2.13 > # Exporter any 5.74 > # List::Util1.33 1.55 > # List::UtilsBy 0.09 0.11 > # Module::Runtime 0.0130.016 > # Role::Tiny 1.003 2.002003 > # Scalar::Util any 1.55 > # Type::Tie0.0040.014 > # autoboxany v3.0.1 > # overload any 1.31 > # parent any0.238 > # strictures 2 2.06 > # > # === Runtime Recommends === > # > # Module Want Have > # - - > # List::UtilsBy::XS 0.03 missing > # Type::Tiny0.022 1.012000 > # > t/00-report-prereqs.t ... > 1..1 > ok 1 > ok > t/00_load/all.t . > ok 1 - array ok > ok 2 - immarray ok > ok 3 - array_of ok > ok 4 - immarray_of ok > ok 5 - hash ok > ok 6 - immhash ok > ok 7 - hash_of ok > ok 8 - immhash_of ok > ok 9 - autobox ok > 1..9 > ok > t/00_load/all_typetinyish.t . > ok 1 - array ok > ok 2 - immarray ok > ok 3 - array_of ok > ok 4 - immarray_of ok > ok 5 - hash ok > ok 6 - immhash ok > ok 7 - hash_of ok > ok 8 - immhash_of ok > ok 9 - autobox ok > 1..9 > ok > t/00_load/autobox.t . > ok 1 - autobox import ok > ok 2 - -autobox import ok > 1..2 > ok > t/00_load/autobox_subclass.t > ok 1 - autoboxed array ok > ok 2 - autoboxed hash ok > 1..2 > ok > t/00_load/badopts.t . > ok 1 - bad import croaks ok > ok 2 - bad function croaks ok > 1..2 > ok > List::Objects::WithUtils::Role::Array::WithJunctions is not a Role::Tiny at > /<>/blib/lib/List/Objects/WithUtils/Array.pm line 6. > Compilation failed in require at > /usr/lib/x86_64-linux-gnu/perl-base/parent.pm line 16. > BEGIN failed--compilation aborted at > /<>/blib/lib/List/Objects/WithUtils/Array/Junction.pm line 8. > Compilation failed in require at > /<>/blib/lib/List/Objects/WithUtils/Role/Array/WithJunctions.pm > line 5. > BEGIN failed--compilation aborted at > /<>/blib/lib/List/Objects/WithUtils/Role/Array/WithJunctions.pm > line 5. > Compilation failed in require at /usr/share/perl5/Role/Tiny.pm line 51. > Compilation failed in require at (eval 21) line 1. > BEGIN failed--compilation aborted at (eval 21) line 1. > at t/00_load/bare.t line 4. > List::Objects::WithUtils::Role::Array::WithJunctions is not a Role::Tiny at > /<>/blib/lib/List/Objects/WithUtils/Array/Immutable/Typed.pm > line 6. > Compilation failed in require at (eval 57) line 1. > BEGIN failed--compilation aborted at (eval 57) line 1. > at t/00_load/ba
Bug#980683: plasma-discover: FTBFS: dh_install: error: missing files, aborting
Source: plasma-discover Version: 5.20.5-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20210120 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[2]: Entering directory '/<>/obj-x86_64-linux-gnu' > make[2]: Nothing to be done for 'preinstall'. > make[2]: Leaving directory '/<>/obj-x86_64-linux-gnu' > Install the project... > /usr/bin/cmake -P cmake_install.cmake > -- Install configuration: "Debian" > -- Installing: > /<>/debian/tmp/usr/share/qlogging-categories5/discover.categories > -- Installing: /<>/debian/tmp/usr/share/locale > -- Installing: /<>/debian/tmp/usr/share/locale/es > -- Installing: /<>/debian/tmp/usr/share/locale/es/LC_MESSAGES > -- Installing: > /<>/debian/tmp/usr/share/locale/es/LC_MESSAGES/libdiscover.mo > -- Installing: > /<>/debian/tmp/usr/share/locale/es/LC_MESSAGES/plasma-discover.mo > -- Installing: > /<>/debian/tmp/usr/share/locale/es/LC_MESSAGES/plasma-discover-notifier.mo > -- Installing: /<>/debian/tmp/usr/share/locale/bs > -- Installing: /<>/debian/tmp/usr/share/locale/bs/LC_MESSAGES > -- Installing: > /<>/debian/tmp/usr/share/locale/bs/LC_MESSAGES/libdiscover.mo > -- Installing: > /<>/debian/tmp/usr/share/locale/bs/LC_MESSAGES/plasma-discover.mo > -- Installing: /<>/debian/tmp/usr/share/locale/de > -- Installing: /<>/debian/tmp/usr/share/locale/de/LC_MESSAGES > -- Installing: > /<>/debian/tmp/usr/share/locale/de/LC_MESSAGES/libdiscover.mo > -- Installing: > /<>/debian/tmp/usr/share/locale/de/LC_MESSAGES/plasma-discover.mo > -- Installing: > /<>/debian/tmp/usr/share/locale/de/LC_MESSAGES/plasma-discover-notifier.mo > -- Installing: /<>/debian/tmp/usr/share/locale/ca@valencia > -- Installing: > /<>/debian/tmp/usr/share/locale/ca@valencia/LC_MESSAGES > -- Installing: > /<>/debian/tmp/usr/share/locale/ca@valencia/LC_MESSAGES/libdiscover.mo > -- Installing: > /<>/debian/tmp/usr/share/locale/ca@valencia/LC_MESSAGES/plasma-discover.mo > -- Installing: > /<>/debian/tmp/usr/share/locale/ca@valencia/LC_MESSAGES/plasma-discover-notifier.mo > -- Installing: /<>/debian/tmp/usr/share/locale/uk > -- Installing: /<>/debian/tmp/usr/share/locale/uk/LC_MESSAGES > -- Installing: > /<>/debian/tmp/usr/share/locale/uk/LC_MESSAGES/libdiscover.mo > -- Installing: > /<>/debian/tmp/usr/share/locale/uk/LC_MESSAGES/plasma-discover.mo > -- Installing: > /<>/debian/tmp/usr/share/locale/uk/LC_MESSAGES/plasma-discover-notifier.mo > -- Installing: /<>/debian/tmp/usr/share/locale/lt > -- Installing: /<>/debian/tmp/usr/share/locale/lt/LC_MESSAGES > -- Installing: > /<>/debian/tmp/usr/share/locale/lt/LC_MESSAGES/libdiscover.mo > -- Installing: > /<>/debian/tmp/usr/share/locale/lt/LC_MESSAGES/plasma-discover.mo > -- Installing: > /<>/debian/tmp/usr/share/locale/lt/LC_MESSAGES/plasma-discover-notifier.mo > -- Installing: /<>/debian/tmp/usr/share/locale/zh_CN > -- Installing: /<>/debian/tmp/usr/share/locale/zh_CN/LC_MESSAGES > -- Installing: > /<>/debian/tmp/usr/share/locale/zh_CN/LC_MESSAGES/libdiscover.mo > -- Installing: > /<>/debian/tmp/usr/share/locale/zh_CN/LC_MESSAGES/plasma-discover.mo > -- Installing: > /<>/debian/tmp/usr/share/locale/zh_CN/LC_MESSAGES/plasma-discover-notifier.mo > -- Installing: /<>/debian/tmp/usr/share/locale/mr > -- Installing: /<>/debian/tmp/usr/share/locale/mr/LC_MESSAGES > -- Installing: > /<>/debian/tmp/usr/share/locale/mr/LC_MESSAGES/libdiscover.mo > -- Installing: > /<>/debian/tmp/usr/share/locale/mr/LC_MESSAGES/plasma-discover.mo > -- Installing: /<>/debian/tmp/usr/share/locale/vi > -- Installing: /<>/debian/tmp/usr/share/locale/vi/LC_MESSAGES > -- Installing: > /<>/debian/tmp/usr/share/locale/vi/LC_MESSAGES/libdiscover.mo > -- Installing: > /<>/debian/tmp/usr/share/locale/vi/LC_MESSAGES/plasma-discover.mo > -- Installing: /<>/debian/tmp/usr/share/locale/eu > -- Installing: /<>/debian/tmp/usr/share/locale/eu/LC_MESSAGES > -- Installing: > /<>/debian/tmp/usr/share/locale/eu/LC_MESSAGES/libdiscover.mo > -- Installing: > /<>/debian/tmp/usr/share/locale/eu/LC_MESSAGES/plasma-discover.mo > -- Installing: > /<>/debian/tmp/usr/share/locale/eu/LC_MESSAGES/plasma-discover-notifier.mo > -- Installing: /<>/debian/tmp/usr/share/locale/it > -- Installing: /<>/debian/tmp/usr/share/locale/it/LC_MESSAGES > -- Installing: > /<>/debian/tmp/usr/shar
Bug#980671: bmtk: FTBFS: Signal: Aborted (6)
Source: bmtk Version: 0.0+git20201018.018da0a+ds-2 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20210120 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_auto_build > I: pybuild base:232: /usr/bin/python3 setup.py build > running build > running build_py > creating /<>/.pybuild/cpython3_3.9/build/bmtk > copying bmtk/__init__.py -> /<>/.pybuild/cpython3_3.9/build/bmtk > creating /<>/.pybuild/cpython3_3.9/build/bmtk/utils > copying bmtk/utils/sim_setup.py -> > /<>/.pybuild/cpython3_3.9/build/bmtk/utils > copying bmtk/utils/__init__.py -> > /<>/.pybuild/cpython3_3.9/build/bmtk/utils > copying bmtk/utils/hdf5_helper.py -> > /<>/.pybuild/cpython3_3.9/build/bmtk/utils > copying bmtk/utils/property_schema.py -> > /<>/.pybuild/cpython3_3.9/build/bmtk/utils > creating /<>/.pybuild/cpython3_3.9/build/bmtk/simulator > copying bmtk/simulator/__init__.py -> > /<>/.pybuild/cpython3_3.9/build/bmtk/simulator > creating /<>/.pybuild/cpython3_3.9/build/bmtk/tests > copying bmtk/tests/__init__.py -> > /<>/.pybuild/cpython3_3.9/build/bmtk/tests > creating /<>/.pybuild/cpython3_3.9/build/bmtk/analyzer > copying bmtk/analyzer/__init__.py -> > /<>/.pybuild/cpython3_3.9/build/bmtk/analyzer > copying bmtk/analyzer/io_tools.py -> > /<>/.pybuild/cpython3_3.9/build/bmtk/analyzer > copying bmtk/analyzer/spikes_loader.py -> > /<>/.pybuild/cpython3_3.9/build/bmtk/analyzer > copying bmtk/analyzer/firing_rates.py -> > /<>/.pybuild/cpython3_3.9/build/bmtk/analyzer > copying bmtk/analyzer/compartment.py -> > /<>/.pybuild/cpython3_3.9/build/bmtk/analyzer > copying bmtk/analyzer/spike_trains.py -> > /<>/.pybuild/cpython3_3.9/build/bmtk/analyzer > copying bmtk/analyzer/spikes_analyzer.py -> > /<>/.pybuild/cpython3_3.9/build/bmtk/analyzer > copying bmtk/analyzer/utils.py -> > /<>/.pybuild/cpython3_3.9/build/bmtk/analyzer > copying bmtk/analyzer/cell_vars.py -> > /<>/.pybuild/cpython3_3.9/build/bmtk/analyzer > creating /<>/.pybuild/cpython3_3.9/build/bmtk/builder > copying bmtk/builder/node_pool.py -> > /<>/.pybuild/cpython3_3.9/build/bmtk/builder > copying bmtk/builder/__init__.py -> > /<>/.pybuild/cpython3_3.9/build/bmtk/builder > copying bmtk/builder/node.py -> > /<>/.pybuild/cpython3_3.9/build/bmtk/builder > copying bmtk/builder/iterator.py -> > /<>/.pybuild/cpython3_3.9/build/bmtk/builder > copying bmtk/builder/network.py -> > /<>/.pybuild/cpython3_3.9/build/bmtk/builder > copying bmtk/builder/node_set.py -> > /<>/.pybuild/cpython3_3.9/build/bmtk/builder > copying bmtk/builder/connector.py -> > /<>/.pybuild/cpython3_3.9/build/bmtk/builder > copying bmtk/builder/edge.py -> > /<>/.pybuild/cpython3_3.9/build/bmtk/builder > copying bmtk/builder/id_generator.py -> > /<>/.pybuild/cpython3_3.9/build/bmtk/builder > copying bmtk/builder/connection_map.py -> > /<>/.pybuild/cpython3_3.9/build/bmtk/builder > copying bmtk/builder/functor_cache.py -> > /<>/.pybuild/cpython3_3.9/build/bmtk/builder > creating /<>/.pybuild/cpython3_3.9/build/bmtk/utils/converters > copying bmtk/utils/converters/__init__.py -> > /<>/.pybuild/cpython3_3.9/build/bmtk/utils/converters > copying bmtk/utils/converters/hoc_converter.py -> > /<>/.pybuild/cpython3_3.9/build/bmtk/utils/converters > creating /<>/.pybuild/cpython3_3.9/build/bmtk/utils/sonata > copying bmtk/utils/sonata/population.py -> > /<>/.pybuild/cpython3_3.9/build/bmtk/utils/sonata > copying bmtk/utils/sonata/__init__.py -> > /<>/.pybuild/cpython3_3.9/build/bmtk/utils/sonata > copying bmtk/utils/sonata/node.py -> > /<>/.pybuild/cpython3_3.9/build/bmtk/utils/sonata > copying bmtk/utils/sonata/file.py -> > /<>/.pybuild/cpython3_3.9/build/bmtk/utils/sonata > copying bmtk/utils/sonata/types_table.py -> > /<>/.pybuild/cpython3_3.9/build/bmtk/utils/sonata > copying bmtk/utils/sonata/edge.py -> > /<>/.pybuild/cpython3_3.9/build/bmtk/utils/sonata > copying bmtk/utils/sonata/group.py -> > /<>/.pybuild/cpython3_3.9/build/bmtk/utils/sonata > copying bmtk/utils/sonata/utils.py -> > /<>/.pybuild/cpython3_3.9/build/bmtk/utils/sonata > copying bmtk/utils/sonata/column_property.py -> > /<>/.pybuild/cpython3_3.9/build/bmtk/utils/sonata > copying bmtk/utils/sonata/file_root.py ->
