Bug#709813: Please give back 0ad on amd64
Dear wanna-build team,
Please give back 0ad on amd64 on a buildd other than barber (i.e.
retry until some other buildd takes it). Currently, it FTBFS on barber
due to "Illegal instruction" when running its testsuite, and it's
proving to be problematic to trace the root cause of the issue. I
cannot reproduce the FTBFS locally with an up-to-date pbuilder, and
the build log doesn't seem to give any clues as to why barber is
bailing out on the testsuite (ansgar and others on #debian-devel noted
the presence of -msse, but that shouldn't be an issue on amd64). A bug
against 0ad has already been filed concerning this issue (#712956) and
I've filed a ticket with upstream [1] (which I'll pursue more
agressively when I have time), I don't think it's a regression, and
this is blocking the enet transition (#709813), so can you please give
back 0ad? Thanks!
gb 0ad_0.0.13-2+b1 . amd64
[1] http://trac.wildfiregames.com/ticket/1994
Reply to: