Your message dated Sun, 04 Sep 2016 00:53:45 +0200
with message-id <147294322588.953.869991314541340...@auryn.jones.dk>
and subject line Re: [Pkg-javascript-devel] Bug#719382: node-stringprep: FTBFS:
/bin/sh: 1: node-waf: not found
has caused the Debian Bug report #719382,
regarding node-stringprep: FTBFS: /bin/sh: 1: node-waf: not found
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.)
--
719382: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=719382
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-stringprep
Version: 0.1.5-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130811 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Maybe this is related to that as of node.js v0.8 node-waf was removed
and replaced with node-gyp (packaged independently).
Relevant part (hopefully):
> debian/rules build
> test -x debian/rules
> mkdir -p "."
>
> WARNING: copyright-check disabled - licensecheck (from devscripts package) is
> missing.
>
> touch debian/stamp-copyright-check
> touch debian/stamp-upstream-cruft
> NODE_PATH=/«PKGBUILDDIR»/debian/node-node-stringprep//usr/lib/nodejs node-waf
> configure
> /bin/sh: 1: node-waf: not found
> make: *** [configure/node-node-stringprep] Error 127
The full build log is available from:
http://aws-logs.debian.net/ftbfs-logs/2013/08/11/node-stringprep_0.1.5-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: 0.6.2-1
Quoting David Suárez (2013-08-11 13:54:01)
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
Thanks for reporting.
This was fixed with the release of node-stringprep 0.6.2-1.
- Jonas
--
* Jonas Smedegaard - idealist & Internet-arkitekt
* Tlf.: +45 40843136 Website: http://dr.jones.dk/
[x] quote me freely [ ] ask before reusing [ ] keep private
signature.asc
Description: signature
--- End Message ---
