Source: docker-registry Version: 2.4.1~ds1-1 Severity: serious Justification: Policy 4.9 User: la...@debian.org Usertags: network-access
Dear Maintainer,
Whilst docker-registry 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 741721fa6fdd.45526 > dnscache.uct.ac.za.domain: 49467+
AAAA? shoudlntresolve.uct.ac.za. (43)
00:00:00.000204 IP 741721fa6fdd.38471 > dnscache.uct.ac.za.domain: 8701+ A?
shoudlntresolve.uct.ac.za. (43)
00:00:00.001139 IP dnscache.uct.ac.za.domain > 741721fa6fdd.45526: 49467
NXDomain* 0/1/0 (97)
00:00:00.001355 IP dnscache.uct.ac.za.domain > 741721fa6fdd.38471: 8701
NXDomain* 0/1/0 (97)
[..]
The full build log (including tcpdump output) is attached.
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
docker-registry.2.4.1~ds1-1.unstable.amd64.log.txt.gz
Description: Binary data
_______________________________________________ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
