Le lun. 8 juin 2020 à 11:13, Jonas Smedegaard <jo...@jones.dk> a écrit :
> Quoting Jonas Smedegaard (2020-05-25 12:09:53) > > Quoting Jérémy Lal (2020-05-25 10:51:32) > > > [nodejs 12 is] 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.* > > > > I suggest to ask on debian-devel@l.d.o > > > > Alternatively - if those tests are possible to identify and isolate - > > skip them during build and have them run at autobuildtest instead. > > Not sure if you're already made aware, but nodejs was mentioned today in > a perl bug where (as I understand it) the suspicion is that failures > connecting to localhost is related to systems having both ipv4 127.0.0.1 > and ipv6 ::1. > > See bug#962318. > That was an helpful hint. I made a bad fix for nodejs 12 to be able to build on conova at the moment, and upstream nodejs/libuv has respawned the discussion around this issue, as i figured out they were already well aware of it. On another front, i realized /usr/include/nodejs was bad because of two things: - upstream expects /usr/include/node, if any - upstream now has a "correct" set of headers to install there So, from now on nodejs 12 installs headers like that. But i didn't want to hinder the transition, so i left the old way in /usr/include/nodejs, and i'll change node-gyp to use /usr/include/node when all is in testing. 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
