Control: reassign -1 dpkg
Control: forcemerge 678848 -1
Le mercredi 20 février 2013 à 22:02 +0100, Lucas Nussbaum a écrit :
> Package: octave-tsa
> Version: 4.2.4-1
> Severity: serious
> Justification: breaks upgrade from squeeze
> While testing upgrades from squeeze to wheezy, I ran into the following
> problem:
>
> Preparing to replace octave-tsa 4.0.1-2 (using .../octave-tsa_4.2.4-1_amd64.deb) ...
> Unpacking replacement octave-tsa ...
> Processing triggers for octave3.2 ...
> + [ triggered = configure ]
> + VERSION=3.2.4
> + PRIORITY=80
> + rebuild_pkg_database
> + octave-3.2.4 --silent --no-history --no-init-file --eval pkg ('rebuild');
> octave-3.2.4: error while loading shared libraries: liblapack.so.3gf: cannot open shared object file: N
> o such file or directory
> dpkg: error processing octave3.2 (--unpack):
> subprocess installed post-installation script returned error exit status 127
>
> A full log is attached.
>
> To reproduce:
> - install octave-tsa in a squeeze chroot
> - modify sources.list: point to wheezy
> - apt-get update
> - apt-get upgrade
> - apt-get dist-upgrade
>
> There are other packages affected by the same problem. Full list is:
> octave-data-smoothing octave-econometrics octave-optim octave-signal octave-tsa pfsglview pfstmo pfstools-dbg pfstools pfsview
This is a known dpkg bug. Merging accordingly.
--
.''`. Sébastien Villemot
: :' : Debian Developer
`. `' http://www.dynare.org/sebastien
`- GPG Key: 4096R/381A7594
Attachment:
signature.asc
Description: This is a digitally signed message part