nodejs in groovy-proposed? (Re: +1 maintenance report)

Bryce Harrington bryce.harrington at
Tue Aug 11 21:13:40 UTC 2020

On Tue, Aug 11, 2020 at 01:02:27PM -0700, Steve Langasek wrote:
> On Tue, Aug 11, 2020 at 09:55:16AM -0700, Bryce Harrington wrote:
> > Could someone give a status update on the icu and json-c transitions?
> > I see they've been progressing daily, but curious since server team has
> > a few packages blocked from migrating.
> The big problem I see right now is nodejs, which seems to have made a
> complete mess of the autopkgtests of its revdeps.  I'd be interested to know
> if anyone is working on this and sees indications that it's tractable, or if
> we should just revert nodejs for now.

I worked on it quite a bit during my +1 maintenance shift a couple weeks
ago.  It has indeed been a huge mess, but it has definitely gotten a lot
better.  Looks to me like there's just three problems remaining for
nodejs itself:

a.  The main remaining issue is that for three of the packages there is a
bug on pcc64el with SHA1 encryption[1], which osomon has been working
on, and found to be due to a compiler optimization error.  He forwarded
it upstream[2] and yesterday upstream provided a patch to test[3].  So
this looks like it's on a path to be solved soon.

b.  Another three packages appear to be hitting timeouts on autopkgtests,
for arm64 only.  Their test histories look like they mostly fail with
scattered random passes.  Maybe a flaky test?  Maybe re-running it a few
times will resolve them?

c.  node-clean-css is the only other failure.  It occurs only on armhf
and only for a single test case.  It doesn't print any details about
what the test case was or how it failed.

In addition to nodejs itself, many node-* packages need rebuilt or
retriggered.  I did a bunch of these on my shift but we're getting
additional ones syncing from Debian.

So, nodejs feels reasonably close, and moving from nodejs 10 to 12 would
be a big improvement for users.



More information about the ubuntu-devel mailing list