Your message dated Tue, 1 Nov 2016 16:47:51 +0100
with message-id <20161101154751.noqk4wdf4dzma...@xanadu.blop.info>
and subject line Re: Bug#841597: blockdiag: FTBFS: E: Build killed with signal
TERM after 150 minutes of inactivity
has caused the Debian Bug report #841597,
regarding blockdiag: FTBFS: E: Build killed with signal TERM after 150 minutes
of inactivity
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.)
--
841597: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841597
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: blockdiag
Version: 1.5.3+dfsg-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161021 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
> ---[ stderr ] ---
> WARNING: unknown image type: http://localhost:8000/circle.svg
> WARNING: unknown image type: http://localhost:8000/circle.eps
>
>
> --------------------- >> end captured stdout << ----------------------
>
> Ran 710 tests in 2.530s
>
> FAILED (SKIP=351, failures=1)
> E: pybuild pybuild:276: test: plugin distutils failed with: exit code=1: cd
> /<<BUILDDIR>>/blockdiag-1.5.3+dfsg/.pybuild/pythonX.Y_2.7/build; python2.7 -m
> nose
> dh_auto_test: pybuild --test --test-nose -i python{version} -p 2.7 returned
> exit code 13
> debian/rules:13: recipe for target 'build' failed
> make: *** [build] Error 25
> dpkg-buildpackage: error: debian/rules build gave error exit status 2
> E: Build killed with signal TERM after 150 minutes of inactivity
If the failure looks somehow time/timezone related:
Note that this rebuild was performed without the 'tzdata' package
installed in the chroot. tzdata used be (transitively) part of
build-essential, but it no longer is. If this package requires it to
build, it should be added to build-depends. For the release team's
opinion on this, see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836940#185
If the failure looks LSB-related:
similarly to tzdata, lsb-base is not installed in the build chroot.
The full build log is available from:
http://aws-logs.debian.net/2016/10/21/blockdiag_1.5.3+dfsg-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 ---
Hi,
On 01/11/16 at 08:23 +0900, Kouhei Maeda wrote:
> Thanks your report.
> But in my environment that I made with pbuilder and cowbuilder, the
> problem does not reappear.
> Please tell me your environmental how to make because I want to test
> it in the same environment.
I've tried the build again, and it doesn't fail anymore. Comparing
build-dependencies, this could have been caused by a bug in
imagemagick or libpng16 (as both were updated).
I'm closing the bug,
Lucas
--- End Message ---
