Hi, On Thu, 07 Jul 2016 16:38:15 +0200 Chris Lamb <la...@debian.org> wrote: > Source: nodejs > Version: 4.4.7~dfsg-2 > Severity: serious > Justification: Policy 4.9 > User: la...@debian.org > Usertags: network-access > > Dear Maintainer, > > Whilst nodejs builds successfully on unstable/amd64, according to > Debian Policy 4.9 packages may not attempt network access during > a build. > > 00:00:00.000000 IP 60e0bdbdf45e.48831 > dnscache.uct.ac.za.domain: 36996+ > A? localhost. (27) > 00:00:00.005147 IP dnscache.uct.ac.za.domain > 60e0bdbdf45e.48831: 36996* > 1/1/1 A 127.0.0.1 (85) > 00:00:49.376504 IP 60e0bdbdf45e.34203 > dnscache.uct.ac.za.domain: 46038+ > AAAA? www.google.com. (32) > 00:00:49.376504 IP 60e0bdbdf45e.59241 > dnscache.uct.ac.za.domain: 21036+ > A? www.google.com. (32) > > [..] > > The full build log (including tcpdump output) is attached.
Is this a regression in 4.4.7, or is 4.3.1 also affected? This is blocking testing migration, which is preventing the mips64el binaries from entering testing. Cheers, Emilio
