On 24/09/15 14:58, Jérémy Lal wrote: > 2015-09-24 14:53 GMT+02:00 Jérémy Lal <kapo...@melix.org > <mailto:kapo...@melix.org>>: > > 2015-09-24 14:42 GMT+02:00 Daniel Pocock <dan...@pocock.pro > <mailto:dan...@pocock.pro>>: > > > > This is failing because node-nan 2.x is now in unstable > > I've filed a bug upstream requesting support for node-nan 2.x > > > This is the right thing to do. > > > Maybe both old and new versions of node-nan will be needed in > stretch? > > > This isn't ! The idea is to move forward to nodejs 4 / nan 2. > Maintaining legacy modules is more time-consuming than porting them > to nan 2.x - a task that i can do but that is best done by upstream. > > Since the two files built using node-gyp and node-nan have been taken > from node-ws, and since node-ws has already been ported to node-nan 2, > i suggest to be patient... > > > An even better solution is to package > https://github.com/websockets/bufferutil > and > https://github.com/websockets/utf-8-validate > and depend on them. > This will benefit node-ws and node-websocket >
I only uploaded node-websocket because it is used by the latest JsSIP code https://github.com/versatica/JsSIP/blob/master/package.json I'm also trying to upload JSCommunicator, JsSIP and the rest of the dependency hierarchy (see my other recent node-* uploads) to jessie-backports where node-nan 2 is not present and the build failure doesn't occur. Can anybody from the JsSIP team comment on this? How do you feel about having node-nan 2.x in the dependency hierarchy? Will you continue using node-websocket or would you possibly use node-ws[1] instead? Using node-ws instead of node-websocket will reduce the number of packages we have to keep track of in Debian. Regards, Daniel 1. https://github.com/websockets/ws
