Package: npm
Version: 0.2.19-1
Followup-For: Bug #622628
Unstable just got nodejs 0.6.2. Unfortunately, this breaks npm 0.2.19.
Hopefully we can bump up the priority of packaging the newer npm now?
cananian@skiffserv:~$ npm
node.js:201
throw e; // process.nextTick error, or 'error' event on first tick
^
Error: No such module
at Object.<anonymous> (/usr/share/npm/lib/utils/output.js:8:21)
at Module._compile (module.js:441:26)
at Object..js (module.js:459:10)
at Module.load (module.js:348:32)
at Function._load (module.js:308:12)
at Module.require (module.js:354:17)
at require (module.js:370:17)
at Object.<anonymous> (/usr/share/npm/lib/utils/log.js:21:14)
at Module._compile (module.js:441:26)
at Object..js (module.js:459:10)
cananian@skiffserv:~$
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 3.2.0-1-686-pae (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages npm depends on:
ii nodejs 0.6.11~dfsg1-2
ii nodejs-dev 0.6.11~dfsg1-2
npm recommends no packages.
npm suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
