Bug#695770: Shouldn't builds just be reattempted for python-2.6?
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 again, but a try on murphy was successful. Either there is something wrong with biber, or python 2.6 is doing something strange. This should really be fixed. Note that biber is an amd64 kernel with i386 userland, murphy is a i386 kernel. Kurt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#695770: Shouldn't builds just be reattempted for python-2.6?
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. But I may be mistaken Yep. It already looked reproducible and the build for i386 again didn't work. Also I don't know why you're copying hurd-i386, because that one doesn't look transient at all. For mips, it seems the build failed because the testsuite was started, which normally doesn't happen on mips. This is caused by this test on_buildd := $(shell [ -f /CurrentlyBuilding -o $$LOGNAME = buildd ] echo yes) On corelli2, LOGNAME is 'buildd2', and so (as can be seen in the build log) the testsuite was started. So for the mips build, a new attempt might solve the problem. I guess a new attempt on sparc could also be tried, but I don't have any idea what's going wrong there. 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? Cheers, Ivo -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#695770: Shouldn't builds just be reattempted for python-2.6?
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 build for i386 again didn't work. Also I don't know why you're copying hurd-i386, because that one doesn't look transient at all. Kind regards Philipp Kern signature.asc Description: Digital signature
Bug#695770: Shouldn't builds just be reattempted for python-2.6?
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
