Package: liblapack3
Version: 3.12.1-6
Severity: important
Tags: d-i
X-Debbugs-Cc: debian-amd64@lists.debian.org, basos.g@gmx.net, debian-boot@lists.debian.org
User: debian-amd64@lists.debian.org
Usertags: amd64
User: debian-boot@lists.debian.org
Usertags: amd64

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
After dist upgrading from bullseye to trixie, and trying to run the minidlad
daemon, it failed with error

/usr/sbin/minidlnad: error while loading shared libraries: liblapack.so.3:
cannot open shared object file: No such file or directory

   * What exactly did you do (or not do) that was effective (or
     ineffective)?
This seems to be related to https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=1117208

From the above bug I could fix this with

root@dogcat:~# update-alternatives --query liblapack.so.3-x86_64-linux-gnu
update-alternatives: warning: alternative /usr/lib/x86_64-linux-
gnu/atlas/liblapack.so.3 (part of link group liblapack.so.3-x86_64-linux-gnu)
doesn't exist; removing from list of alternatives
Name: liblapack.so.3-x86_64-linux-gnu
Link: /usr/lib/x86_64-linux-gnu/liblapack.so.3
Status: auto
Best: /usr/lib/x86_64-linux-gnu/lapack/liblapack.so.3
Value: /usr/lib/x86_64-linux-gnu/atlas/liblapack.so.3

Alternative: /usr/lib/x86_64-linux-gnu/lapack/liblapack.so.3
Priority: 10


 update-alternatives --set liblapack.so.3-x86_64-linux-gnu
/usr/lib/x86_64-linux-gnu/lapack/liblapack.so.3
update-alternatives: warning: alternative /usr/lib/x86_64-linux-
gnu/atlas/liblapack.so.3 (part of link group liblapack.so.3-x86_64-linux-gnu)
doesn't exist; removing from list of alternatives
update-alternatives: warning: /etc/alternatives/liblapack.so.3-x86_64-linux-gnu
is dangling; it will be updated with best choice
update-alternatives: using /usr/lib/x86_64-linux-gnu/lapack/liblapack.so.3 to
provide /usr/lib/x86_64-linux-gnu/liblapack.so.3 (liblapack.so.3-x86_64-linux-
gnu) in manual mode


*** End of the template - remove these template lines ***

Note, the same happened for

libblas3
   Installed: 3.12.1-6

with a similar fix.

Le samedi 06 décembre 2025 à 21:35 +0200, basos9 a écrit :

I suppose you mean from bookworm to trixie? Because skipping one
release during the upgrade process is unsupported.

This seems to be the same bug as #117208, i.e. atlas alternative not
correctly removed after its deinstallation.

The prerm script of atlas in bookworm in obviously correct, so this
must be an edge case of the upgrade process.

Unless there is a way to reproduce it, I don’t see anything actionable
here.

The rest is not interesting - cross-release dist-upgrades
are not supported.  Release notes for trixie says you should
upgrade to latest bookworm before upgrading to trixie.

This bug report can be closed.

For the reported, I suggest a clean install of trixie to
an empty partition.

Thanks,

/mjt

Sorry, it was a typo mistake of mine.

I dist upgraded from the latest oldstable to stable which in this time
is, 12 to 13 (bookworm to trixie).

Nevertheless, this system was installed with debian 10 in the first place.

I could not either reproduce it in a docker environment from a fresh 12
to 13. So it might be a left over file in /etc/alertnatives that was not
cleared and caused the issue.

You can leave this as as a reference for any other person that might
have this issue.

Thank you