Le jeudi 16 janvier 2014 à 11:18 +0100, Thomas Weber a écrit : > On Fri, Jan 10, 2014 at 10:56:56AM +0100, Sébastien Villemot wrote: > > > Upgrade error from octave_3.6.4-4+b1 to octave_3.8.0-1, with > > > octave-control installed: > > > > > > (Reading database ... 427825 files and directories currently installed.) > > > Removing octave-control (2.6.1-1) ... > > > dpkg: liboctave1:amd64: dependency problems, but removing anyway as you requested: > > > octave depends on liboctave1 (= 3.6.4-4+b1). > > > > > > Removing liboctave1:amd64 (3.6.4-4+b1) ... > > > Processing triggers for octave (3.6.4-4+b1) ... > > > octave: error while loading shared libraries: liboctinterp.so.1: cannot open shared object file: No such file or directory > > > dpkg: error processing package octave (--remove): > > > subprocess installed post-installation script returned error exit status 127 > > > > This is a manifestation of #671711, which is unfortunately not yet > > fixed :( > > > > I guess we have no other choice than removing the breaks on liboctave1 > > and replacing it by a long list of package/versions that are broken with > > Octave 3.8. > > Is the problem just #671711? So, assuming dpkg would do the right thing, > we would get away with a simple Breaks:liboctave1? Yes, this is my understanding. The upgrade crash reported by Mike clearly comes from the fact that dpkg processes triggers while the dependencies of octave (here version 3.6.4-4+b1) are not satisfied (liboctave1 having already been removed). -- .''`. 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