Sylvestre Ledru <sylves...@debian.org> writes: > Are you sure it is not the bug #588175 ?
Although that bug (which I had missed, BTW; thanks for pointing it out) likely increased the impact of #577610, I would say that ATLAS's shlibs files still need to (re)allow alternative dependencies. The different libatlas3gf-* packages all (compatibly) define the same symbols, and libblas.so.3gf and liblapack.so.3gf can just as well come from libblas3gf and liblapack3gf respectively, so there is no need to insist on the specific ATLAS variant against which a package happens to have been built. To be sure, that will often be the generic libatlas3gf-base, but I still shouldn't need to install it when I already have libblas3gf, liblapack3gf, and libatlas3gf-amd64sse3. Thanks! -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?...@monk.mit.edu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
