[Pkg-octave-devel] failed installing octave3.0 in chroot that had octave2.9

Ólafur Jens Sigurðsson ojsbug at gmail.com
Mon Feb 25 16:05:03 UTC 2008

On Mon, Feb 25, 2008 at 12:01:43PM +0100, Rafael Laboissiere wrote:
> * Ólafur Jens Sigurðsson <ojsbug at gmail.com> [2008-02-25 11:50]:
> > I was trying to install octave3.0 in a chroot environment that had
> > octave2.9 allready and it failed with
> > 
> > Unpacking octave3.0 (from .../octave3.0_1%3a3.0.0-4_i386.deb) ...
> > dpkg: error processing
> > /var/cache/apt/archives/octave3.0_1%3a3.0.0-4_i386.deb (--unpack):
> >  trying to overwrite /usr/share/enscript/hl/octave.st', which is also
> > in package octave2.9
> > dpkg-deb: subprocess paste killed by signal (Broken pipe)
> > Errors were encountered while processing:
> >  /var/cache/apt/archives/octave3.0_1%3a3.0.0-4_i386.deb
> >  E: Sub-process /usr/bin/dpkg returned an error code (1)
> > 
> > Is this reproducable with you guys or is this a one insidence only? :-)
> Perhaps we need some Conflicts fields in debian/control.  Which version of
> octave2.9 do you have in your chroot?

I have version 1:2.9.19-2 in my chroot.

This conflict is strange since my chroot is linked against the main
debian repository but at school I have another computer that is linked
to a repository here in Denmark and the octave3.0 packages have
different conflicts. I distinctly remember that octave3.0 at school
conflicted with octave2.9 but the one that my chroot is trying to pull
in does not contain that conflict only the following:

Conflicts: octave (<= 2.0.16-2)

Was the conflict to octave2.9 dropped by some reason recently?


More information about the Pkg-octave-devel mailing list