Bug#678848: liblapack3: octave has upgrade problems: liblapack.so.3gf: cannot open shared object file: No such file or directory

[Sébastien Villemot]

reassign 678848 dpkg
merge 671711 678848
affects 678848 liblapack3 libblas3 octave
thanks

Andreas Beckmann <debian at abeckmann.de> writes:

> Package: liblapack3
> Version: 3.4.1-3
> Severity: serious

> while doing piuparts tests distupgrading from squeeze to sid I noticed a
> cooperation problem between octave and liblapack3:
>
> [...]
>   Preparing to replace liblapack3gf 3.3.1-1 (using .../liblapack3gf_3.4.1-3_amd64.deb) ...
>   Unpacking replacement liblapack3gf ...
>   Preparing to replace libblas3gf 1.2.20110419-2 (using .../libblas3gf_1.2.20110419-3_amd64.deb) ...
>   Unpacking replacement libblas3gf ...
>   Selecting previously unselected package libblas3.
>   Unpacking libblas3 (from .../libblas3_1.2.20110419-3_amd64.deb) ...
>   update-alternatives: warning: alternative /usr/lib/libblas/libblas.so.3gf (part of link group libblas.so.3gf) doesn't exist. Removing from list of alternatives.
>   update-alternatives: warning: /etc/alternatives/libblas.so.3gf is dangling, it will be updated with best choice.
>   Selecting previously unselected package liblapack3.
>   Unpacking liblapack3 (from .../liblapack3_3.4.1-3_amd64.deb) ...
>   update-alternatives: warning: alternative /usr/lib/lapack/liblapack.so.3gf (part of link group liblapack.so.3gf) doesn't exist. Removing from list of alternatives.
>   update-alternatives: warning: /etc/alternatives/liblapack.so.3gf is dangling, it will be updated with best choice.
>   Preparing to replace octave-io 1.0.18-2 (using .../octave-io_1.0.19-1_amd64.deb) ...
>   Unpacking replacement octave-io ...
>   Processing triggers for octave ...
>   octave: error while loading shared libraries: liblapack.so.3gf: cannot open shared object file: No such file or directory
>   dpkg: error processing octave (--unpack):
>    subprocess installed post-installation script returned error exit status 127
>   Errors were encountered while processing:
>    octave

The problem is that the octave trigger is run before liblapack3 (a
dependency of octave) is configured.

This is a dpkg bug, I’m therefore reassigning and merging accordingly.

Hopefully the impact of this bug seems limited (at least in the octave
case), because dpkg retries the trigger a second time after having
configured liblapack3 (and that second time is successful).

Thanks,

-- 
Sébastien Villemot
Researcher in Economics & Debian Maintainer
http://www.dynare.org/sebastien
Phone: +33-1-40-77-84-04 - GPG Key: 4096R/381A7594
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 835 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/debian-science-maintainers/attachments/20120625/ed2d0ce0/attachment.pgp>