Le ven. 29 mai 2020 à 23:08, Nilesh Patra <npatra...@gmail.com> a écrit :
> Hi Jérémy > > On Fri, 29 May 2020, 23:47 Jérémy Lal, <kapo...@melix.org> wrote: > >> >> >> Le lun. 25 mai 2020 à 12:10, Jonas Smedegaard <jo...@jones.dk> a écrit : >> >>> 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. >>> >>> >>> > - armhf, i386: dh_dwz fails because it exhausts memory. >>> > Somewhat fixed by ignoring those failures. *Is there a better option >>> ?* >>> >>> Maybe this (used e.g. in modero package) helps: >>> >>> # reduce debugging information on 32bit archs >>> # to avoid some FTBFS (memory axhaustion of build environment?) >>> ifeq ($(DEB_HOST_ARCH_BITS),32) >>> export DEB_CXXFLAGS_MAINT_APPEND = -g1 >>> endif >>> >>> >> Good idea ! I'm going to try that now. >> >> >> >>> > - 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. >>> >>> Might be helped from above as well. >>> >>> Might also help to disable parallel builds for that architecture. >>> >> >> Yes, indeed, going to do that too, if that's not already the case. >> > > With the latest upload to experimental > Looks like you managed to fix all(most of) the stuff. Yay! :-) > Is this ready now to migrate? > Let's see how it goes...
-- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
