Source: python-pysnmp4 Version: 4.3.2-1 Severity: serious Justification: Policy 4.9 User: la...@debian.org Usertags: network-access
Dear Maintainer, Whilst python-pysnmp4 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 f388474420e8.56001 > dnscache.uct.ac.za.domain: 22176+ A? docs.python.org. (33) 00:00:00.000047 IP f388474420e8.56001 > dnscache.uct.ac.za.domain: 58704+ AAAA? docs.python.org. (33) 00:00:00.298323 IP dnscache.uct.ac.za.domain > f388474420e8.56001: 22176 3/4/4 CNAME python.map.fastly.net., CNAME prod.python.map.fastlylb.net., A 151.101.16.223 (259) 00:00:00.298485 IP dnscache.uct.ac.za.domain > f388474420e8.56001: 58704 2/1/0 CNAME python.map.fastly.net., CNAME prod.python.map.fastlylb.net. (178) 00:00:00.298847 IP f388474420e8.56028 > 151.101.16.223.https: Flags [S], seq 3625504385, win 29200, options [mss 1460,sackOK,TS val 109282155 ecr 0,nop,wscale 7], length 0 00:00:00.448736 IP 151.101.16.223.https > f388474420e8.56028: Flags [S.], seq 1889438288, ack 3625504386, win 28560, options [mss 1440,sackOK,TS val 1698798700 ecr 109282155,nop,wscale 9], 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-pysnmp4.4.3.2-1.unstable.amd64.log.txt.gz
Description: Binary data