Package: liblapack3 Version: 3.4.1-4 Severity: important I got warnings from dpkg when updating from 3.4.1-3 to 3.4.1-4 Dpkg version is 1.16.4.3 from wheezy (sid has more recent dpkg) Is this bug in lapack or in dpkg?
-- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (700, 'testing'), (600, 'unstable'), (500, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages liblapack3 depends on: ii debconf [debconf-2.0] 1.5.44 ii libblas3 [libblas.so.3] 1.2.20110419-3 ii libc6 2.13-33 ii libgcc1 1:4.7.1-2 ii libgfortran3 4.7.1-2 ii libquadmath0 4.7.1-2 liblapack3 recommends no packages. liblapack3 suggests no packages. -- no debconf information
... reparing to replace liblapack3 3.4.1-3 (using .../liblapack3_3.4.1-4_amd64.deb) ... update-alternatives: error: no alternatives for liblapack.so.3gf. dpkg: warning: subprocess old pre-removal script returned error exit status 2 dpkg - trying script from the new package instead ... dpkg: ... it looks like that went OK. Unpacking replacement liblapack3 ... Preparing to replace liblapack3gf 3.4.1-3 (using .../liblapack3gf_3.4.1-4_all.deb) ... update-alternatives: error: no alternatives for liblapack.so.3gf. dpkg: warning: subprocess old pre-removal script returned error exit status 2 dpkg - trying script from the new package instead ... dpkg: ... it looks like that went OK. Unpacking replacement liblapack3gf ... Processing triggers for man-db ... ... Setting up liblapack3 (3.4.1-4) ... update-alternatives: using /usr/lib/lapack/liblapack.so.3 to provide /usr/lib/liblapack.so.3 (liblapack.so.3) in auto mode. Setting up liblapack3gf (3.4.1-4) ...
