On Wed, Mar 01, 2017 at 03:33:55PM +0000, James Clarke wrote:
So the issue here is that, by default, pbuilder runs the build in a separate network namespace with only a loopback interface configured.
The loopback interface works, you can bind and connect as normal
(otherwise this would have been found a long time ago), but getaddrinfo
has a slightly interesting deviation from POSIX. POSIX states[1]:
It also fails on my system now since I switched from dnsmasq to systemd-resolved. That's really annoying.
On Sun, Apr 23, 2017 at 10:07:08PM +0200, Julian Andres Klode wrote:
On Wed, Mar 01, 2017 at 03:33:55PM +0000, James Clarke wrote:
So the issue here is that, by default, pbuilder runs the build in a separate network namespace with only a loopback interface configured.
The loopback interface works, you can bind and connect as normal (otherwise this would have been found a long time ago), but getaddrinfo has a slightly interesting deviation from POSIX. POSIX states[1]:
It also fails on my system now since I switched from dnsmasq to systemd-resolved. That's really annoying.
Just a quick note that it's probably the same thing that is tracked in glibc's #844420 (glibc FTBFS in pbuilder due a test failing to resolve localhost).
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 296 |
Nodes: | 16 (2 / 14) |
Uptime: | 57:42:52 |
Calls: | 6,652 |
Calls today: | 4 |
Files: | 12,200 |
Messages: | 5,331,029 |