On Mon, May 25, 2020 at 10:51 am, Jérémy Lal <kapo...@melix.org>
wrote:
It's ready to be built, but not ready to go in testing:
https://buildd.debian.org/status/package.php?p=nodejs&suite=experimental
- amd64 some tests won't pass because of network issues
I never figured why some build servers fail on this, and some not.
If anyone knows an explanation, that'll help.
- armhf, i386: dh_dwz fails because it exhausts memory.
Somewhat fixed by ignoring those failures. Is there a better option
?
- mips64el: tools/test.py no longer recognize the arch (it should get
it from
the one mapped in debian/rules). Easy to fix.
- mipsel: fails to build, OOM as some point.
That was on a 8GB memory machine, so i suppose it's bad luck,
something
else was using memory maybe.
Can't these be fixed after it hits unstable, given that we really want
nodejs 12 in bullseye and we can't have nodejs 10 in bullseye?
The earlier it hits unstable, the more testing it can receive.
Jérémy
--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
