On Sun, Jan 29, 2017 at 06:00:06PM -0400, David Bremner wrote: > Daniel Schepler <dschep...@gmail.com> writes: > > > Source: xapian-core > > Version: 1.4.3-1 > > Severity: normal > > I'm not the xapian maintainer, but I consider this not a bug. Using > localhost networking for testing is common, and not forbidden by Debian > policy afaik.
Policy's wording isn't entirely clear here - from ยง4.9: | For packages in the main archive, no required targets may attempt | network access. My reading (and I assume what is intended) is that this is not meant to include localhost, but localhost is the loopback *network* interface, so I can see how people could interpret it to exclude that too. But I think having localhost available is valuable, and if the latter interpretation was being argued for, I think policy needs clarifying. As David points out, having localhost available allows testsuites to test network functionality. If we can't run such tests we could miss Debian-specific patches introducing regressions which the testsuite would have caught if we'd been able to run it. But pbuilder with USENETWORK=no should actually still provide lo. It didn't originally but that was reported and addressed: https://bugs.debian.org/753944 Daniel: What version of pbuilder are you using? If it's more than a year old, then upgrading will probably fix this. If not, then either that fix has regressed in pbuilder regression, or else something more complex is going on. Cheers, Olly
