[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#872023: marked as done (transition: nodejs)

Your message dated Thu, 4 Jan 2018 12:12:36 +0100
with message-id <5ab98ff9-4e04-0de1-7b42-4e33b89d2f07@debian.org>
and subject line Re: Bug#849505: transition: nodejs
has caused the Debian Bug report #849505,
regarding transition: nodejs
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 owner@bugs.debian.org
immediately.)


-- 
849505: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849505
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: transition

Transition from nodejs 4 to nodejs 6, with module abi change from
version 46 to version 48.
All nodejs c++ addons (build-depending on nodejs-dev) must be rebuilt.

Also Julien Puydt rebuilt all node modules packages against nodejs 6
to check for failures and report them:
- node-chai #868319 fixed upstream
- node-argparse #868294 might be fixed upstream
- node-evp-bytestokey fails and is deprecated. #868298

Also i'm using nodejs 6 from experimental for some time now, and i don't
see breakage.

Ben file:

title = "nodejs";
is_affected = .build-depends ~ /nodejs-dev/;
is_good = .depends ~ /nodejs-abi-48/;
is_bad = .depends ~ /nodejs-abi-46/;


Regards,

Jérémy

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.11.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8), LANGUAGE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

--- End Message ---
--- Begin Message --- 
On 08/09/17 17:19, Emilio Pozuelo Monfort wrote:
> 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.

This transition got stuck for some time due to problems in nodejs itself (FTBFS
on mips(el), RC bug #878674). But since we're going to move to a newer version
(see transition bug #886294) I'm closing this one.

Cheers,
Emilio

--- End Message ---
Reply to: