[buildd-tools-devel] Bug#710447: sbuild: Fails when it thinks it doesn't have enough disk space

[Kurt Roeckx]

On Thu, Dec 24, 2015 at 01:05:00AM +0100, Johannes Schauer wrote:
> Control: tag -1 + patch moreinfo
> 
> Hi,
> 
> On Thu, 30 May 2013 22:49:23 +0200 Kurt Roeckx <kurt at roeckx.be> wrote:
> > Package: sbuild
> > Version: 0.64.0-1+buildd20130522.0
> > Severity: important
> 
> what justifies Severity: important?

Because it marks packages as failed where nothing is wrong with
the package.

> > I got this in my log file:
> > Purging /A«BUILDDIRA»
> > Not cleaning session: cloned chroot in use
> > E: Disc space is probably not sufficient for building.
> > I: Source needs 2703644 KiB, while 4089748 KiB is free.)
> > 
> > And then it marked the package as failed.  It shouldn't have
> > failed that package.  At worst it should have been marked as
> > attempted.
> 
> Is sbuild still marking packages as failed in this case? The code in the
> function status_trigger() in bin/sbuild instead suggests that insufficient
> space is resulting in the status 'given-back'.
> 
> If you nevertheless want it to be set to 'attempted' instead, the fix is very
> simple:

Give back would be fine too.  It should just not mark it as
failed.


Kurt