[00:08] <barry> thomi: i'm back from dinner now
[00:09] <thomi> barry: so now the tests are failing in sbuild because they try and create a TCPServer, and that seems to fail in the chroot
[00:09] <barry> thomi: using pybuild?
[00:09] <thomi> I assume there's some restriction within an sbuild chroot about what network operations you're allowed to perform
[00:09] <thomi> barry: yes
[00:10] <thomi> it looked like it was unable to resolve 'localhost', so I'm retrying now with '127.0.0.1', but I suspect the real problem is a policy that prevents package builds from doing any network activity
[00:10] <thomi> (which sounds reasonable to me)
[00:10] <thomi> but I'm wondering if the best thing is to skip those tests during a package build, or if there's something better I can do
[00:10] <barry> thomi: so by default, pybuild sets http{,s}_proxy to 127.0.0.1:9 which is the discard port to prevent accidental attempts to download stuff from pypi.  usually that's fine, but if you do need to make localhost connections for tests, you want to override_dh_auto_test and unset those envars for the duration of the test
[00:11] <barry> https://wiki.debian.org/Python/LibraryStyleGuide
[00:11] <barry> (search for http_proxy)
[00:11] <thomi> ahhhh
[00:11] <thomi> awesome
[00:11] <barry> so something like this i think works:
[00:11] <barry> override_dh_auto_test:
[00:11] <barry>    http_proxy= https_proxy= dh_auto_test
[00:12] <thomi> cool, trying that now - thanks :D
[00:16] <barry> np!
[00:28] <thomi> barry: yaaay! A built binary package :)
[00:29] <barry> \o/
[00:29] <thomi> barry: I'll upload this to mentors, and maybe get you to +1 it?
[00:29] <thomi> barry: then perhaps you can upload it firect to Ubuntu to save us some time?
[00:29] <barry> :)
[00:29] <barry> thomi: send me an email so i don't forget and i'll take a look tomorrow
[00:30] <thomi> barry: will do, thanks
=== fginther` is now known as fginther