Bug#853107: xapian-core: FTBFS under pbuilder with USENETWORK=no

Control: tag -1 + fixed-upstream patch On Mon, Mar 13, 2017 at 04:24:01PM +1300, Olly Betts wrote: > I think this is worthwhile addressing in xapian-core. I've pushed a fix for this upstream: https://trac.xapian.org/changeset/9ed4dec1cb51c241cf7eb0b927f0e3122c2676a2/git Once the release is out

Bug#853107: xapian-core: FTBFS under pbuilder with USENETWORK=no

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

Bug#853107: xapian-core: FTBFS under pbuilder with USENETWORK=no

On Thu, Feb 16, 2017 at 03:21:01PM -0800, Daniel Schepler wrote: > On Thu, Feb 16, 2017 at 1:37 PM, Olly Betts wrote: > > One thought - is /etc/gai.conf present in the chroot with any uncommented > > content? > > Nope, it's just the normal template /etc/gai.conf file with

Bug#853107: xapian-core: FTBFS under pbuilder with USENETWORK=no

On Thu, Feb 16, 2017 at 1:37 PM, Olly Betts wrote: > One thought - is /etc/gai.conf present in the chroot with any uncommented > content? Nope, it's just the normal template /etc/gai.conf file with everything commented. I think pbuilder does blank out /etc/resolv.conf in the

Bug#853107: xapian-core: FTBFS under pbuilder with USENETWORK=no

On Thu, Feb 16, 2017 at 09:19:35AM -0800, Daniel Schepler wrote: > > 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

Bug#853107: xapian-core: FTBFS under pbuilder with USENETWORK=no

On Sun, Jan 29, 2017 at 9:06 PM, Olly Betts wrote: > On Sun, Jan 29, 2017 at 06:00:06PM -0400, David Bremner wrote: >> Daniel Schepler writes: >> >> > Source: xapian-core >> > Version: 1.4.3-1 >> > Severity: normal >> >> I'm not the xapian maintainer, but I

Bug#853107: xapian-core: FTBFS under pbuilder with USENETWORK=no

On Tue, Jan 31, 2017 at 10:09:57PM +0100, Georg Faerber wrote: > > 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

Bug#853107: xapian-core: FTBFS under pbuilder with USENETWORK=no

Hi Olly, > 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. This is happening here [1] as well, which is a

Bug#853107: xapian-core: FTBFS under pbuilder with USENETWORK=no

On Sun, Jan 29, 2017 at 06:00:06PM -0400, David Bremner wrote: > Daniel Schepler 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,

Bug#853107: xapian-core: FTBFS under pbuilder with USENETWORK=no

Daniel Schepler 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. d

Bug#853107: xapian-core: FTBFS under pbuilder with USENETWORK=no

Source: xapian-core Version: 1.4.3-1 Severity: normal >From my pbuilder build log: ... Running test: qpmemoryleak1... EXCEPTION std::string Failed to get 'Listening...' from command '../bin/xapian-tcpsrv --one-shot --interface 127.0.0.1 --port 1239 -t30 --writable .chert/dbw' (output: