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.)
--
841558: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841558
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

--- Begin Message ---

Source: node-tap
Version: 0.7.1-1.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):
> debian/rules build
> dh build
> dh_testdir
> dh_update_autotools_config
> dh_auto_configure
> debian/rules override_dh_auto_build
> make[1]: Entering directory '/<<PKGBUILDDIR>>'
> help2man -N -n "Test-Anything-Protocol module for Node.js" bin/tap.js -o
> "debian/tap.1"
> help2man: can't get `--help' info from bin/tap.js
> Try `--no-discard-stderr' if option outputs to stderr
> debian/rules:20: recipe for target 'debian/tap.1' failed
> make[1]: *** [debian/tap.1] Error 1
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/node-tap_0.7.1-1.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.