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 (/usr/share/npm/lib/utils/locker.js:44:11)
  npm ERR!     at cb (/usr/share/npm/lib/cache/add-named.js:32:5)
  npm ERR!     at /usr/share/npm/lib/cache/add-named.js:41:20
  npm ERR!     at /usr/share/npm/lib/utils/locker.js:22:20
  npm ERR!     at /usr/share/npm/node_modules/inflight/inflight.js:22:7
  npm ERR!     at Array.forEach (native)
  npm ERR!     at res (/usr/share/npm/node_modules/inflight/inflight.js:21:9)
  npm ERR!     at /usr/lib/nodejs/once.js:17:15
  npm ERR!     at afterMkdir (/usr/share/npm/lib/cache/get-stat.js:53:14)
  npm ERR!     at /usr/lib/nodejs/mkdirp/index.js:34:29

or

  npm ERR! Error: Attempt to unlock test@*, which hasn't been locked
  npm ERR!     at unlock (/usr/share/npm/lib/utils/locker.js:44:11)
  [...]

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 non-release architecture kfreebsd-i386.

Could you please take a look?

Thanks!

FTR, I'm classifying this bug as a regression even though node-lex-parser
is new because I strongly suspect it would also affect binNMUs on amd64.

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

Reply via email to