Jonas Smedegaard d...@jones.dk writes:
The package evidently builds fine now.
Yes, this failure mode is gone, thanks. It looks like the armel and
armhf builds are running into test suite timeouts, though:
On Mon, 5 Dec 2011 15:37:04 +0700, Jonas Smedegaard wrote:
On 11-12-05 at 09:24am, Jérémy Lal wrote:
This problem is caused by the fact you're building with latest
libv8-dev, but nodejs 0.4 wasn't.
I'll upload a nodejs 0.4 built against libv8 3.5 later today.
Hmm - I suspect this
On 05/12/2011 17:53, David Paleino wrote:
On Mon, 5 Dec 2011 15:37:04 +0700, Jonas Smedegaard wrote:
On 11-12-05 at 09:24am, Jérémy Lal wrote:
This problem is caused by the fact you're building with latest
libv8-dev, but nodejs 0.4 wasn't.
I'll upload a nodejs 0.4 built against libv8 3.5
Hi Aaron,
On 11-11-30 at 02:45pm, Aaron M. Ucko wrote:
The automated build of node-expat on i386 (the only platform besides
amd64 for which its build dependencies are available) failed with a
test suite error:
NODE_PATH=/.../node-expat-1.4.1/debian/node-node-expat//usr/lib/nodejs node
Jonas Smedegaard d...@jones.dk writes:
Not sure if the proper approach is to reasign or file another bug and
make one of them affect the other - and since I maintain both packages I
will simply spend my time on fixing the issue instead :-)
Commendably practical; thanks for the prompt fix.
5 matches
Mail list logo
