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

["Debian Bug Tracking System" <owner@bugs.debian.org>]

Your message dated Mon, 15 Aug 2022 13:31:41 +0200
with message-id <YvoundoFXwk7NNMl@ramacher.at>
and subject line Re: Bug#1015270: transition: nodejs
has caused the Debian Bug report #1015270,
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.)


-- 
1015270: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015270
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

--- Begin Message ---

• To: Debian Bug Tracking System <submit@bugs.debian.org>
• Subject: transition: nodejs
• From: Jérémy Lal <kapouer@melix.org>
• Date: Mon, 18 Jul 2022 19:07:15 +0200
• Message-id: <165816403571.115698.6090826517240982634.reportbug@localhost.localdomain>

Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: transition

Hi,

nodejs 18.6.0 will soon be the active version of nodejs:
https://nodejs.org/en/about/releases/

I rebuilt and checked all reverse-build-deps of libnode-dev/nodejs,
and dealt with most of the regressions, or opened bugs proposing a solution.

Thanks,
Jérémy


Ben file:

title = "nodejs";
is_affected = .depends ~ /\b(libnode93)\b/ | .depends ~ /\b(libnode108)\b/;
is_good = .depends ~ /\b(libnode108)\b/;
is_bad = .depends ~ /\b(libnode93)\b/;

--- End Message ---

--- Begin Message ---

• To: Jérémy Lal <kapouer@melix.org>, 1015270-done@bugs.debian.org
• Subject: Re: Bug#1015270: transition: nodejs
• From: Sebastian Ramacher <sramacher@debian.org>
• Date: Mon, 15 Aug 2022 13:31:41 +0200
• Message-id: <YvoundoFXwk7NNMl@ramacher.at>
• In-reply-to: <CAJxTCxz8nONBCfC7bQx9pL2ZPq4Tzii-sNNVj_gp6H84MSrewg@mail.gmail.com>
• References: <165816403571.115698.6090826517240982634.reportbug@localhost.localdomain> <CAM8zJQt0xUfMN4HQgBQZdcoZuvbGqrSmqvP0ZDf_zR5dLoHCaw@mail.gmail.com> <e64809a9-f978-2bc9-2e9c-373ae15ab58b@debian.org> <CAJxTCxxOqQgp=wARA+K30oYwdOQ9VOK7dwcUi25L_Jv7zLg-ug@mail.gmail.com> <3a972ed4-cb40-4018-2923-56ab7a0fb226@debian.org> <165816403571.115698.6090826517240982634.reportbug@localhost.localdomain> <CAJxTCxz8nONBCfC7bQx9pL2ZPq4Tzii-sNNVj_gp6H84MSrewg@mail.gmail.com>

On 2022-07-30 15:56:07, Jérémy Lal wrote:
> Le sam. 30 juil. 2022 à 15:42, Paul Gevers <elbrus@debian.org> a écrit :
> 
> > Hi Jérémy,
> >
> > On 29-07-2022 22:47, Jérémy Lal wrote:
> > >     All seems to be well on its way, with the exception of the
> > autopkgtest
> > >     failure of node-babel7 on ppc64el. Did you already have a look at
> > that?
> > >
> > >     I can file the bug against node-babel7 if you want.
> > >
> > >
> > > v8 clearly crashes on ppc64el here while executing tsc, so it's not a
> > > node-babel7 bug.
> >
> > If I understand you correctly, v8 is some internal thing of nodejs and
> > the issue needs to be fixed there.
> 
> 
> That's right.
> 
> 
> > Did you already report the issue
> > upstream? Do you need help from the ppc64el porters? Will you handle this?
> >
> 
> Not yet but yes, I'm currently working on it - good news is that it
> reproduces on plummer.d.o.

The issues were fixed and nodejs migrated.

Cheers
-- 
Sebastian Ramacher

--- End Message ---