Re: Bug#95116: failed autobuild of python-numeric_17.1.2-4 (m68k): conflicting build-depends
Michael Schmitz writes:
> > How can I fix this in python-numeric? On a recent unstable system I
> > have both blas-dev and lapack-dev installed. Or do the build
> > dependencies of blas-dev and lapack-dev, and apt doesn't detect this?
>
> Sorry if I wasn't perfectly clear about the details:
>
> The dependencies of blas-dev (-> blas1) and lapack-dev (-> lapack) did
> conflict for me. apt refused to install either blas-dev or lapack-dev.
>
> > > Unpacking lapack (from .../lapack_2.0.1-2.1_m68k.deb) ...
> > > Unpacking lapack-dev (from .../lapack-dev_2.0.1-2.1_m68k.deb) ...
>
> That's the lapack versions, I have no idea what blas versions were
> current at that time. I can have another try at installing both blas1 and
> lapack (current versions) to see if that changed.
$ dpkg -l blas1 lapack blas-dev lapack-dev apt
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Name Version Description
+++-==============-==============-============================================
ii blas1 1.0-6 A set of building blocks for performing vect
ii lapack 3.0-5.1 a comprehensive set of linear algebra routin
ii blas-dev 1.0-6 A set of building blocks for performing vect
ii lapack-dev 3.0-5.1 a comprehensive set of linear algebra routin
ii apt 0.5.3 Advanced front-end for dpkg
that's installed together on my system. So I assume I can close the
report, because it's resolved in the most recent version.
Reply to: