Source: python-future Version: 0.15.2-2 Severity: serious Justification: Policy 4.9 User: la...@debian.org Usertags: network-access
Dear Maintainer,
Whilst python-future 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 a0060c47b606.46455 > dnscache.uct.ac.za.domain: 65445+ A?
docs.python.org. (33)
00:00:00.000045 IP a0060c47b606.46455 > dnscache.uct.ac.za.domain: 40305+
AAAA? docs.python.org. (33)
00:00:00.321499 IP dnscache.uct.ac.za.domain > a0060c47b606.46455: 65445
3/4/4 CNAME python.map.fastly.net., CNAME prod.python.map.fastlylb.net., A
151.101.16.223 (259)
00:00:00.327415 IP dnscache.uct.ac.za.domain > a0060c47b606.46455: 40305
2/1/0 CNAME python.map.fastly.net., CNAME prod.python.map.fastlylb.net. (178)
00:00:00.327659 IP a0060c47b606.56548 > 151.101.16.223.http: Flags [S], seq
3114845646, win 29200, options [mss 1460,sackOK,TS val 107973771 ecr
0,nop,wscale 7], length 0
00:00:00.341151 IP 151.101.16.223.http > a0060c47b606.56548: Flags [S.], seq
1857195259, ack 3114845647, win 5792, options [mss 1460,sackOK,TS val 719202749
ecr 107973771,nop,wscale 1], length 0
[..]
This appears to be caused by (at least) Sphinx's intersphinx mapping extension.
Please see #830186 for more information, including suggestions on how to fix it.
The full build log (including tcpdump output) is attached.
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
python-future.0.15.2-2.unstable.amd64.log.txt.gz
Description: Binary data
