On Mon, 2010-11-01 at 16:03 +0100, Julien Cristau wrote:
On Mon, Nov 1, 2010 at 10:24:32 -0400, Adam C Powell IV wrote:
Hi Sylvestre,
Sorry, didn't see this note until now. You're probably right, that
should be the cause.
This confirms that a binNMU of scalapack should fix this
Hi Sylvestre,
Sorry, didn't see this note until now. You're probably right, that
should be the cause.
This confirms that a binNMU of scalapack should fix this bug (should
have subscribed to it). The maintainer hasn't replied, so can the
release team take care of this before squeeze? It's
On Mon, Nov 1, 2010 at 10:24:32 -0400, Adam C Powell IV wrote:
Hi Sylvestre,
Sorry, didn't see this note until now. You're probably right, that
should be the cause.
This confirms that a binNMU of scalapack should fix this bug (should
have subscribed to it). The maintainer hasn't
I wonder if it is not caused by:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=588175
scalapack-1.8.0/debian$ grep lapack-dev control
Build-Depends: mpi-default-dev, pvm-dev, blacs-pvm-dev, gfortran,
liblapack-dev, libblas-dev, debhelper (= 6), libblacs-mpi-dev
Sylvestre
--
To
4 matches
Mail list logo