Your message dated Tue, 8 Jan 2013 09:04:30 +0100
with message-id <[email protected]>
and subject line Re: Shouldn't builds just be reattempted for python-2.6?
has caused the Debian Bug report #695770,
regarding python2.6 2.6.8-1: FTBFS on i386 mips sparc
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
695770: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=695770
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
package: src:python2.6
severity: serious
Hi,
It seems python2.6 2.6.8-1 fails to build on some archs:
https://buildd.debian.org/status/package.php?p=python2.6
This also prevents the fix for #639405 from reaching unstable (and testing).
Cheers,
Ivo
--- End Message ---
--- Begin Message ---
Hi,
On Tue, Jan 01, 2013 at 09:07:50PM +0100, Ivo De Decker wrote:
> 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.
It did. But the test in python-2.6 is still broken.
> I guess a new attempt on sparc could also be tried, but I don't have any idea
> what's going wrong there.
It also did.
> 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.
As the build failure are gone (for now), I'm closing this bug.
Cheers,
Ivo
--- End Message ---
