clone 678848 -1
reassign -1 libarpack2 3.1.1-2
retitle -1 libarpack2: please add Breaks: octave3.2
thanks
After digging a bit more into this octave upgrade problem, I found a
workaround: libarpack2 needs to add
Breaks: octave3.2
There is already a similar conflict in libblas3 (#677399).
Having the Breaks reorders the upgrade order so that octave3.2 is
removed in a few more cases (tested so far with octave-benchmark,
octave-vrml) before the libblas/liblapack links get broken and
octave3.2 cannot be triggered successfully any longer.
At the time when the trigger failed, octave3.2 was linked against both
libblas.so.3gf (directly) and against libblas.so.3 (via libarpack.so.2),
so libarpack2 seems to be the next promising candidate to add such a
conflict.
There should probably be a better way to properly describe this
conflict, but due to dpkg bug #678848 dpkg may do trigger-processing of
a package that has its dependencies currently not satisfied.
Anyway, the workaround I suggested here should circumvent these problems.
Andreas
--
To UNSUBSCRIBE, email to debian-dpkg-bugs-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
