Control: tag -1 -moreinfo
Control: tag -1 +upstream
This came up on #debian-devel and jrtc27 (James Clarke) spotted the underlying
cause - from "man getaddrinfo":
| If hints.ai_flags includes the AI_ADDRCONFIG flag, then IPv4 addresses
| are returned in the list pointed to by res only if the local system has
| at least one IPv4 address configured, and IPv6 addresses are returned
| only if the local system has at least one IPv6 address configured. The
| loopback address is not considered for this case as valid as a config‐
| ured address.
The last sentence about loopback isn't in POSIX, but is in RFC3493. And
this is the problem here - inside the chroot, pbuilder has removed all but
loopback, so getaddrinfo() won't return an IPv4 address as there's no IPv4
address configured (not considering loopback). By similar logic, it won't
return an IPv6 address either.
Practically, you wouldn't actually use Xapian's remote backend on a box
with only loopback - you'd have to run the server on the same box, which
makes little sense. But this setup is likely to be seen in testsuites for
both xapian-core, and for things which build on it and use the remote
backend, and disabling networking except localhost is sane for
autobuilders, so I think this is worthwhile addressing in xapian-core.
Cheers,
Olly
