Your message dated Sun, 17 Jun 2012 11:38:02 +0200
with message-id <87haua1dol....@brouzouf.villemot.name>
and subject line Re: Bug#605370: atlas: FTBFS on alpha, armel, ia64, mips,
powerpc and s390
has caused the Debian Bug report #605370,
regarding atlas: FTBFS on alpha, armel, ia64, mips, powerpc and s390
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 ow...@bugs.debian.org
immediately.)
--
605370: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=605370
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: atlas
Version: 3.8.3-29
Severity: serious
Tags: sid
Hello,
Your package fails to build on many architectures:
Please see https://buildd.debian.org/pkg.cgi?pkg=atlas
Best regards
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (700, 'unstable'), (600, 'testing'), (500, 'stable'), (1,
'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-5-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
--- End Message ---
--- Begin Message ---
Version: 3.8.4-7
Closing this bug, since version 3.8.4-7 compiled on all archs mentioned
in the original report.
For the records, here is my understanding of what happened:
- the original cause of the FTBFS which triggered this bug report was
external to the package (dependency or compiler issue) and it has
disappeared since
- however, in version 3.8.4-1, a new issue was introduced: the number of
threads was no longer forced to 2, and this led to failures on some
arches where autodetection of threads was not working; this change was
reverted in 3.8.4-7, hence the build success
- additionally, there are still random FTBFS due to the very nature of
upstream build system. These typically occur when the buildd is under
heavy load. This is documented upstream:
http://math-atlas.sourceforge.net/errata.html#tol
A build failing because of this known problem will have this message
near the end:
VARIATION EXCEEDS TOLERENCE, RERUN WITH HIGHER REPS.
A give back generally solves the problem. There seems to be no easy
solution to this issue, since fixing it would require thorough changes
in the build system.
--
Sébastien Villemot
Researcher in Economics & Debian Maintainer
http://www.dynare.org/sebastien
Phone: +33-1-40-77-84-04 - GPG Key: 4096R/381A7594
pgpRL69DLwubb.pgp
Description: PGP signature
--- End Message ---
