Bug#695770: Shouldn't builds just be reattempted for python-2.6?

2013-01-08 Thread Kurt Roeckx
On Tue, Jan 08, 2013 at 09:04:30AM +0100, Ivo De Decker wrote: On i386, I tried the build several times with pbuilder, and it succeeds every time. This was on an amd64 kernel. Both buildd failures were on biber. Maybe it should be tried on another buildd? A wew try on biber failed

Bug#695770: Shouldn't builds just be reattempted for python-2.6?

2013-01-01 Thread Ivo De Decker
Hi, On Sun, Dec 30, 2012 at 09:15:41PM +0100, Philipp Kern wrote: On Sat, Dec 29, 2012 at 04:54:01PM +0100, Christian PERRIER wrote: Subject says it all. I'm tempted to think that at least the mips and i386 failures were just a transient failure and the builds should just be reattempted.

Bug#695770: Shouldn't builds just be reattempted for python-2.6?

2012-12-30 Thread Philipp Kern
On Sat, Dec 29, 2012 at 04:54:01PM +0100, Christian PERRIER wrote: Subject says it all. I'm tempted to think that at least the mips and i386 failures were just a transient failure and the builds should just be reattempted. But I may be mistaken Yep. It already looked reproducible and the

Bug#695770: Shouldn't builds just be reattempted for python-2.6?

2012-12-29 Thread Christian PERRIER
Subject says it all. I'm tempted to think that at least the mips and i386 failures were just a transient failure and the builds should just be reattempted. But I may be mistaken -- signature.asc Description: Digital signature