Your message dated Sat, 15 Oct 2016 17:28:01 +0000
with message-id <e1bvskb-0000nz...@franck.debian.org>
and subject line Bug#840756: fixed in node-lex-parser 0.1.4-2
has caused the Debian Bug report #840756,
regarding node-lex-parser: FTBFS: Attempt to unlock ..., which hasn't been 
locked
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.)


-- 
840756: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840756
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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

--- End Message ---
--- Begin Message ---
Source: node-lex-parser
Source-Version: 0.1.4-2

We believe that the bug you reported is fixed in the latest version of
node-lex-parser, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 840...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Pirate Praveen <prav...@debian.org> (supplier of updated node-lex-parser 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Sat, 15 Oct 2016 22:27:07 +0530
Source: node-lex-parser
Binary: node-lex-parser
Architecture: source amd64
Version: 0.1.4-2
Distribution: unstable
Urgency: medium
Maintainer: Pirate Praveen <prav...@debian.org>
Changed-By: Pirate Praveen <prav...@debian.org>
Description:
 node-lex-parser - parser for lexical grammars used by jison and jison-lex
Closes: 840756
Changes:
 node-lex-parser (0.1.4-2) unstable; urgency=medium
 .
   * Use system jison (Closes: #840756)
Checksums-Sha1:
 e9e8519fbe3a1c80f1e395f8fb1aef5bb6213acf 1925 node-lex-parser_0.1.4-2.dsc
 f777d6c065ed60b3024f2fca4be541c03944f92d 2260 
node-lex-parser_0.1.4-2.debian.tar.xz
 4393f85ac2428f76c641774bf641f3bfd13b9183 11646 
node-lex-parser_0.1.4-2_amd64.deb
Checksums-Sha256:
 bb468e7e13b63361cefbfb0fd959c95fc97287cad3dd7e608dc6b2e38ee50156 1925 
node-lex-parser_0.1.4-2.dsc
 1b9f175f54f707c2422f3d817b1527eecd02a999f4ab71222853264dfb50b86c 2260 
node-lex-parser_0.1.4-2.debian.tar.xz
 1e0446d6e89837b2014df035abf554d7525069d132edf535171544bb9753b485 11646 
node-lex-parser_0.1.4-2_amd64.deb
Files:
 2ea80f34642390e1e72e5c721ba387ec 1925 web optional node-lex-parser_0.1.4-2.dsc
 406b33c96b5cbe2b6cfd59cfcf8a46a3 2260 web optional 
node-lex-parser_0.1.4-2.debian.tar.xz
 622b8406436a77095ce068ea79e67174 11646 web optional 
node-lex-parser_0.1.4-2_amd64.deb

-----BEGIN PGP SIGNATURE-----

iQIcBAEBCAAGBQJYAmB5AAoJEM4fnGdFEsIqs1UP/0kzVI2Qjd2x0muM/HzQleWa
trD7d//Ga5fcBxMO3vN0jJedwdiupbHQ6CSBuZa03fi1RkiwatAPmrj7yIz+0n7L
BJ3us6Oo/b+KA8fdhVrccOEK+mssI12iZjdsmOxixK9BFd+cxmbkq6PPc/rPOL3o
uAy//tALIWMMCbtTUGi/D2vt/XSKlgTj9l6mnfJj0sKrKcgM5dusXTzuL/RfjFEO
Vxo47OeyKdHPoXzfDe9bTdsONE3cNwUYfWmh0c8/8mYdTi21kzmTtSFP3XyzWeaG
qgnmhguIHLgfQgA/j+AZZTaSlkLyu/UwTCH0b+8az9yO6lUywvPePzGTli0CVUP5
4i20tvDFwrKCvDXk2ryXVmUqRVpaonapaZQVQ1Rybd0tQGjgV+ZLi63Ma7ePGAiC
UO2hbZ48avsefwns7XXdC8fGFLFWi0ca/jrbf4mVd4iDjS+2CnV6gVNkRRW2cP/G
J/ADh3XLCfx+Nz99W3mpmsmRDHZUV7f/yx79+lST1SUuG5l69/j1BP5F7s5a/vM4
CZZGJaR9Mot8J0SHwN248Chuy2K/DGahUmqgpUZLEj03lWt+xAcVVysJkSp6y3Cn
2aGvC/o2HmYTixw2yTWM89kwVq/nubGuNy/REliXZmE5rOaHOLLoyjmB682BrgXI
aZiNqIeB3nx1FYrNuG7X
=D8Cg
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to