Your message dated Sun, 27 Sep 2020 21:29:58 +0100 with message-id <20200927202958.gb114...@espresso.pseudorandom.co.uk> and subject line Re: Bug#971156: libsoup2.4: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 MESON_TESTTHREADS=4 ninja test returned exit code 1 has caused the Debian Bug report #971156, regarding libsoup2.4: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 MESON_TESTTHREADS=4 ninja 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.) -- 971156: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971156 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Source: libsoup2.4 Version: 2.70.0-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200926 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > 26/41 ssl-test FAIL 0.12s (killed by signal 5 > SIGTRAP) The full build log is available from: http://qa-logs.debian.net/2020/09/26/libsoup2.4_2.70.0-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! 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 ---Version: 2.71.1-1 On Sun, 27 Sep 2020 at 20:54:35 +0200, Lucas Nussbaum wrote: > Relevant part (hopefully): > > 26/41 ssl-test FAIL 0.12s (killed by signal 5 > > SIGTRAP) This is basically the same bug as #970935 and is fixed in the version I uploaded to unstable earlier today (plus a few earlier versions in experimental). smcv
--- End Message ---
