> > I could not reproduce this issue. How did you get the source for node > (GitHub clone and if so which branch/tag did you checkout, source tarball, > other)? Also, which OS did you use to run node? >
I cloned the github repo, checked out the v0.10.33-release branch, did `./configure --debug --without-snapshot` and `make`. I'm running on 64-bit Ubuntu 12.04.5. I just tried my repro steps and I can repro this but it apparently also depends on the contents of the package.json in the current directory -- if I run the same "npm install archiver connect" command from the original directory it fails as described; if I run it from an empty directory (or rm ./package.json) it completes successfully. I have to run somewhere right now but I will boil this down to a minimal repro case that's actually self-contained and get back to you later tonight. I also tried rebuilding after reconfigure with `./configure --debug` (no --without-snapshot) and a clean build, to see if the --without-snapshot flag makes a difference (my experience is I need that flag to be able to use the heap profiler which I like to be able to use, and I assume that the official nodejs.org binaries are built that way). It doesn't seem to make a difference. thanks Matt -- Job board: http://jobs.nodejs.org/ New group rules: https://gist.github.com/othiym23/9886289#file-moderation-policy-md Old group rules: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to nodejs+unsubscr...@googlegroups.com. To post to this group, send email to nodejs@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/nodejs/609aa8b1-a15b-41d4-8577-52fdf1833659%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
