Hi,
Axel Beckert wrote:
> Ole Streicher wrote:
> > Am 14.10.2015 um 16:37 schrieb Axel Beckert:
> > > Yes, but not inside a clean chroot (pbuilder here). But I'm working on
> > > this.
> >
> > I used a clean chroot (pbuilder with cowbuild), and I didn't get any
> > unresolved deps (after a "cowbuilder --update").
>
> Hrm, interesting.
I finally found the culprit: My build space was too small. I captured
this while the test suite failed inside a "pbuilder login":
→ df -h /var/cache/pbuilder/build
Filesystem Type Size Used Avail Use% Mounted on
/dev/mapper/vgcc-pb ext4 6.8G 6.8G 0 100% /var/cache/pbuilder
There was no "no space left on device" in any of the build logs nor in
the output of the manually run test suite. I just became aware of it
bceause of other commands I entered after the test suite has been run.
It seems the LV was full only exactly at the point when the test suite
was run and I can imagine that maybe some internal, compiled
dependencies for the test suite weren't properly built due to this,
but it was only noticed when the tests itself failed.
With 1 GB more on that LV, the pdebuild-based build worked fine. Will
do the NMU soon.
Regards, Axel
--
,''`. | Axel Beckert <a...@debian.org>, http://people.debian.org/~abe/
: :' : | Debian Developer, ftp.ch.debian.org Admin
`. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5
`- | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
