Bug#581412: [libblas3gf] ImoprtError in Numpy when trying to execute mnemosyne

darkestkhan darkestkhan at gmail.com
Fri Jun 8 14:58:45 UTC 2012


> Le 08/06/2012 12:09, darkestkhan a écrit :
> >     from numpy.linalg import lapack_lite
> >  ImportError: libblas.so.3gf: cannot open shared object file: No such
> > file or directory
> I cannot reproduce your problem.
> sudo apt-get install -t unstable mnemosyne
>
> $ ls /usr/lib/libblas*
> /usr/lib/libblas.so.3  /usr/lib/libblas.so.3gf?
>
> Anyway this should fix your problem:
> $ sudo apt-get install libblas3 --reinstall
>
> Can you confirm?
>
> Thanks
> S

I tried that before looking for another bugfix/workaround - as it was
written in one of the previousresponses to this bugreport that
reinstalling helps.
I did run $ sudo aptitude reinstall libblas3 libblas3gf
but that didn't help and this is the reason why I tried making symlink
by hand (which actually solved the problem at least for me). I will check
the other day in QEMU if I can find a sure way to trigger the bug.
It is [not so] funny that yesterday mnemosyne was running properly, but
today I had this bug.

Luckily I still had logs from today morning upgrade:
Setting up libatlas3-base (3.8.4-5) ...
update-alternatives: using /usr/lib/atlas-base/atlas/libblas.so.3 to
provide /usr/lib/libblas.so.3 (libblas.so.3) in auto mode.
update-alternatives: warning: skip creation of /usr/lib/libblas.so.3gf
because associated file /usr/lib/atlas-base/libblas.so.3 (of link
group libblas.so.3) doesn't exist.
update-alternatives: using /usr/lib/atlas-base/atlas/liblapack.so.3 to
provide /usr/lib/liblapack.so.3 (liblapack.so.3) in auto mode.
Setting up libatlas3gf-base (3.8.4-5) ...

Maybe this will help.

Have a nice day,
darkestkhan





More information about the debian-science-maintainers mailing list