On Sun, Jan 13, 2019 at 01:53:07PM +0100, Martin Pitt wrote:
> Hello Santiago,
>
> Santiago Vila [2019-01-13 13:37 +0100]:
> > > Indeed, this points out a broken build environment that doesn't have a
> > > loopback
> > > device. [...]
> >
> > No, not the case. This used to build ok in the past
Hello Santiago,
Santiago Vila [2019-01-13 13:37 +0100]:
> > Indeed, this points out a broken build environment that doesn't have a
> > loopback
> > device. [...]
>
> No, not the case. This used to build ok in the past in my autobuilders:
The loopback issue does not affect *your* builds. E. g.
On Sun, Jan 13, 2019 at 01:22:18PM +0100, Martin Pitt wrote:
> > I'm thus going to assume that the build environments that runs into
> > these problems uses network namespaces or similar and doesn't expose
> > anything but loopback to the build chroot.
>
> Indeed, this points out a broken build
Control: block -1 by bug 918892
Hello Santiago, Andreas,
Andreas Henriksson [2019-01-12 21:41 +0100]:
> > # FAIL: 31
>
> Lots of failing tests there
Right, but they have two different root causes. The first is bug 918892, a
recent regression in libssh 0.8.6, which causes all the
On Sat, Jan 12, 2019 at 09:41:49PM +0100, Andreas Henriksson wrote:
> It might be a good idea to first just test if all problems vanishes
> if builting in a less network restricted environment, [...]
I guess not, because I'm using plain sbuild on a stretch machine,
which AFAIK does not have (by
Hello,
On Sun, Jan 06, 2019 at 12:55:49AM +, Santiago Vila wrote:
> Package: src:cockpit
> Version: 184-1
> Severity: serious
> Tags: ftbfs
[...]
>
> Testsuite summary for Cockpit 184
>
Package: src:cockpit
Version: 184-1
Severity: serious
Tags: ftbfs
Dear maintainer:
I tried to build this package in buster but it failed:
[...]
debian/rules build-indep
dh build-indep
dh_update_autotools_config
7 matches
Mail list logo
