[Pkg-octave-devel] The future of Atlas

[lukshuntim at gmail.com]

On 06/16/2012 03:50 PM, Sébastien Villemot wrote:
> Thomas Weber <tweber at debian.org> writes:
> 
>> On Sun, Jun 10, 2012 at 10:28:15PM +0200, Sébastien Villemot wrote:
>>> I have been discussing this issue with Sylvestre Ledru, the maintainer
>>> of atlas. Even though he has not made a decision yet, he is now
>>> considering the possibility of removing atlas from the archive. I am
>>> going to help him maintain the package but I am not sure that we can
>>> solve the various issues. Especially there are FTBFS on several release
>>> architectures and upstream seems not willing to help.
>>
>> I've skimmed the SourceForge mailing list and I think the issue is more
>> along the lines of "he is way too busy for keeping ATLAS at least
>> somewhat buildable on what feels like 100+ architectures".
> 
> There is good news: I managed to fix the FTBFS of ATLAS. It is now
> almost in a releasable state.
> 
>>> All in all, it is becoming likely that we will have to change the
>>> Recommends field of octave from atlas to openblas. This may even have to
>>> be done for Wheezy.
>>
>> Hmm, I think Sylvestre should clarify that with the release team. I
>> don't think they will object (at least for Octave, it doesn't change
>> anything in the build), but I'd rather get their OK for that *now*. 
> 
> The Release Team is aware of some issues around BLAS/LAPACK. I hope they
> will accept the migration of the new set of packages (refblas,
> reflapack, atlas, openblas).

Would that mean libblas, liblapack, libblas-dev, liblapack-dev are now
all virtual packages? That would be great!

Regards,
ST
--