Bug#849505: transition: nodejs

[Emilio Pozuelo Monfort <pochu@debian.org>]

On 30/08/17 09:37, Jérémy Lal wrote:
> 
> 
> 2017-08-29 23:15 GMT+02:00 Sebastiaan Couwenberg <sebastic@xs4all.nl 
> <mailto:sebastic@xs4all.nl>>:
> 
>     On 06/25/2017 01:15 PM, Jonathan Wiltshire wrote:
>     > Now stretch is released we can deal with this.
>     >
>     > On Wed, Dec 28, 2016 at 12:49:33AM +0100, Jérémy Lal wrote:
>     >> Transition should have minimal impact on these addons.
>     >> Most other pure Node.js modules should be okay - they either
>     >> are already compatible with Node.js 6 or have upstream updates
>     >> providing that compatibility.
>     >
>     > This sounds rather, well, hopeful. Please stage the transition in
>     > experimental first, and test/fix reverse dependencies. Then come back and
>     > we'll schedule a time to do it in unstable.
>     >
>     > (Transitions should really be ready to go by the time they come to us;
>     > they should also be able to happen quickly, because a blocked transition
>     > holds up all sorts of other work.)
> 
>     Jérémy, the transition was started by the upload of nodejs to unstable,
>     but you've not replied to the above yet.
> 
>     Can you confirm that all reverse dependencies build successfully with
>     the new nodejs in unstable?
> 
>     If so, the binNMUs can be scheduled to move this transition along.
> 
>     I just uploaded a new upstream release of node-mapnik, that won't need
>     an NMU now, but the other rdeps still do.
> 
>     Kind Regards,
> 
> 
> All the reverse deps of nodejs-abi-xx should rebuild fine.

It's all done, except that node-websocket ships an arch:all package that depends
on nodejs-abi-48, and we can't binNMU arch:all packages... so that will need a
sourceful upload.

Cheers,
Emilio