Bug#840756: node-lex-parser: FTBFS: Attempt to unlock ..., which hasn't been locked

2016-10-15 Thread Pirate Praveen
On Sun, 16 Oct 2016 00:20:31 -0400 u...@debian.org (Aaron M. Ucko) wrote: > Is there some reason node-lex-parser has an Architecture value of any > rather than all? Its contents all appear to be architecture-independent > at first glance. Because it was created by dh-make as npm2deb was crashing

Bug#840756: node-lex-parser: FTBFS: Attempt to unlock ..., which hasn't been locked

2016-10-15 Thread Aaron M. Ucko
Pirate Praveen writes: > jison is now in the archive and we don't need npm. Once jison clears > NEW, I'll upload a fixed version. Thanks. Alas, the new version is unbuildable on architectures that previously failed -- e.g., node-lex-parser build-depends on: -

Bug#840756: node-lex-parser: FTBFS: Attempt to unlock ..., which hasn't been locked

2016-10-15 Thread Pirate Praveen
Control: -1 tags pending On Friday 14 October 2016 07:29 PM, Aaron M. Ucko wrote: > Automatic builds of node-lex-parser all failed with either > > npm ERR! Error: Attempt to unlock jison@0.4.x, which hasn't been locked > npm ERR! at unlock (/usr/share/npm/lib/utils/locker.js:44:11) >

Bug#840756: node-lex-parser: FTBFS: Attempt to unlock ..., which hasn't been locked

2016-10-14 Thread Pirate Praveen
On വെള്ളി 14 ഒക്ടോബര്‍ 2016 07:29 വൈകു, Aaron M. Ucko wrote: > depending on the architecture. For whatever reason, the problem was with > jison@0.4.x on arm64, armhf, mips, powerpc, ppc64el, s390x, and the > non-release architecture kfreebsd-amd64, and test@* on i386, mips64el, > mipsel, and the

Bug#840756: node-lex-parser: FTBFS: Attempt to unlock ..., which hasn't been locked

2016-10-14 Thread Aaron M. Ucko
Source: node-lex-parser Version: 0.1.4-1 Severity: serious Justification: fails to build from source (but built successfully in the past) Automatic builds of node-lex-parser all failed with either npm ERR! Error: Attempt to unlock jison@0.4.x, which hasn't been locked npm ERR! at unlock