Hi,
libuv upstream here. This is (most likely) due to the test suite. Given
libuv is a i/o library it does some i/o with the outside world in a few
tests. What is the policy for these kind of packages?
Debian could have a patch skipping those tests, but I doubt we'd apply
them upstream.
Regards,
On Thu, 07 Jul 2016 11:26:55 +0200 Chris Lamb <la...@debian.org> wrote:
Source: libuv
Version: 0.10.36-3
Severity: serious
Justification: Policy 4.9
User: la...@debian.org
Usertags: network-access
Dear Maintainer,
Whilst libuv 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 23b3236fe5a9.50304 > google-public-dns-a.google.com.9999:
Flags [S], seq 3514717835, win 29200, options [mss 1460,sackOK,TS val 66263071 ecr
0,nop,wscale 7], length 0
00:00:00.303691 IP 23b3236fe5a9.40816 > 1.2.3.4.9123: Flags [S], seq
251433203, win 29200, options [mss 1460,sackOK,TS val 66263146 ecr 0,nop,wscale
7], length 0
[..]
The full build log (including tcpdump output) is attached.
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
--
Saúl Ibarra Corretgé
http://bettercallsaghul.com
_______________________________________________
Pkg-javascript-devel mailing list
Pkg-javascript-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
