I am not to worried about node-seq being removed from testing at the
moment, as there are many other dependencies requiring packaging for
browserify first.

It looks like it is is not a simple matter of updating the Depends:
field in debian/control.

Cloning the upstream repo, merging some fixes for the testsuite from a
fork, npm install'ing the dependencies gives me a passing test (Expresso
is required for the tests - I must file a bug about that).

npm update'ing the chainsaw dependency to 0.1.0 gives me the following
test failure when running "npm test":
   uncaught undefined: RangeError: Maximum call stack size exceeded
    at action (/home/ross/github/node-seq/index.js:76:11)
    at call (/home/ross/github/node-seq/index.js:236:17)
    at Array.forEach (native)
    at Object.parEach (/home/ross/github/node-seq/index.js:230:17)
    at EventEmitter.saw.next
    at Object.extend (/home/ross/github/node-seq/index.js:491:13)
    at EventEmitter.saw.next
    at EventEmitter.saw.jump
    at Function.cb (/home/ross/github/node-seq/index.js:39:21)
    at next (/home/ross/github/node-seq/index.js:266:26)

I will need to see what changed in chainsaw. But I will probably
concentrate on all the other browserify dependencies first.



Attachment: signature.asc
Description: OpenPGP digital signature

Pkg-javascript-devel mailing list

Reply via email to