Hi,
On Wed, 11 Dec 2013 14:07:14 +0100 Nicolas Boulenguez
wrote:
> Some (admittedly faulty) build tools produce messages on stderr instead of
> stdout.
I don't think it can be called faulty to produce messages on stderr. I'd not
want, for example a progress meter on stdout because that would me
On Sun, Feb 15, 2015 at 10:30:11AM +0100, Johannes Schauer wrote:
> > I'm CCing the sbuild maintainers because it probably needs to be fixed there
> > first.
> Should instead this bug not be reassigned to sbuild?
> This bug even has a patch - fixing it should be trivial.
Yeah, fix it in mainline s
Hi,
On Fri, 11 Jul 2014 12:56:57 -0400 Felipe Sateler wrote:
> I just spent some time wondering about this due to a build failure in
> ardour3. This is a big time waster for everyone involved.
during the last three months I uploaded botch with different changes to somehow
not cause timeouts on a
Package: buildd.debian.org
Followup-For: Bug #731940
Hi,
Nicolas Boulenguez wrote:
> Some (admittedly faulty) build tools produce messages on stderr
> instead of stdout. However, sbuild only considers stdout to detect
> timeout and kill inactive builds.
I just spent some time wondering about thi
Package: buildd.debian.org
Severity: wishlist
Tags: patch
Hello.
Some (admittedly faulty) build tools produce messages on stderr
instead of stdout. However, sbuild only considers stdout to detect
timeout and kill inactive builds.
This results in hard to diagnose failures, as the log (rightfully)
5 matches
Mail list logo