<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Le lun. 25 mai 2020 à 11:34, Xavier <<a href="mailto:yadd@debian.org">yadd@debian.org</a>> a écrit :<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Le 25/05/2020 à 10:51, Jérémy Lal a écrit :<br>
> <br>
> <br>
> Le lun. 25 mai 2020 à 09:22, Nilesh Patra <<a href="mailto:npatra974@gmail.com" target="_blank">npatra974@gmail.com</a><br>
> <mailto:<a href="mailto:npatra974@gmail.com" target="_blank">npatra974@gmail.com</a>>> a écrit :<br>
> <br>
> Hi Jérémy<br>
> <br>
> On Sat, 7 Mar 2020, 14:34 Jérémy Lal, <<a href="mailto:kapouer@melix.org" target="_blank">kapouer@melix.org</a><br>
> <mailto:<a href="mailto:kapouer@melix.org" target="_blank">kapouer@melix.org</a>>> wrote:<br>
> <br>
> <br>
> <br>
> Le sam. 7 mars 2020 à 06:18, Nilesh Patra <<a href="mailto:npatra974@gmail.com" target="_blank">npatra974@gmail.com</a><br>
> <mailto:<a href="mailto:npatra974@gmail.com" target="_blank">npatra974@gmail.com</a>>> a écrit :<br>
> <br>
> <br>
> <br>
> I think we should start Node.js 12 migration (with<br>
> rollup, webpack,<br>
> gulp,...), this will also fix some RC/FTBFS bugs, should we?<br>
> I fixed a lot of failing autopkgtest errors (using [1]<br>
> list), most of<br>
> the remaining packages in this list will be fixed by<br>
> node-iconv rebuild.<br>
> <br>
> <br>
> Agreed. Node-nodedbi is removed from testing, officially<br>
> now. We can file a (RC) bug against Node-srs for it to _not_<br>
> migrate, same for Node-millstone.<br>
> Nodejs transition is also required for acorn transition,<br>
> from what I read on the mailing list.<br>
> <br>
> As it's been pending now, for a long time and there's not<br>
> much to be done except fixing these last 2-3 blockers, which<br>
> will be removed (from testing) anyway.<br>
> Would it be a good time to start the transition?<br>
> If yes, It would be great to start in other transitions, :)<br>
> <br>
> <br>
> <br>
> Right now node is waiting upon icu >= 64, which won't be in sid<br>
> before ~may.<br>
> <br>
> <br>
> This is probably the time now - may ends with the coming weekend.<br>
> Any updates if this is in sid or when this would get to sid if it<br>
> isn't already?<br>
> <br>
> <br>
> It's ready to be built, but not ready to go in testing:<br>
> <a href="https://buildd.debian.org/status/package.php?p=nodejs&suite=experimental" rel="noreferrer" target="_blank">https://buildd.debian.org/status/package.php?p=nodejs&suite=experimental</a><br>
> <br>
> - amd64 some tests won't pass because of network issues<br>
> I never figured why some build servers fail on this, and some not.<br>
> * If anyone knows an explanation, that'll help.*<br>
> - armhf, i386: dh_dwz fails because it exhausts memory.<br>
> Somewhat fixed by ignoring those failures. *Is there a better option ?*<br>
> - mips64el: tools/test.py no longer recognize the arch (it should get it<br>
> from<br>
> the one mapped in debian/rules). Easy to fix.<br>
> - mipsel: fails to build, OOM as some point.<br>
> That was on a 8GB memory machine, so i suppose it's bad luck, something<br>
> else was using memory maybe.<br>
> <br>
> Jérémy<br>
<br>
Hi,<br>
<br>
there is a new "needs-internet" restriction in autopkgtest, maybe this<br>
will fix one pb<br></blockquote><div><br></div><div>Indeed, but no: it happens during the build phase.</div><div>(that way we can get architecture-related test failures).<br></div><div><br></div><div>Also the tests are not requiring internet access, they only tcp/udp, ipv4/6 on localhost.</div><div><br></div><div><br></div><div><br></div><div> </div></div></div>