[Pkg-octave-devel] Packaging Octave 3.8

[Sébastien Villemot]

Le jeudi 02 janvier 2014 à 21:39 +0100, Rafael Laboissiere a écrit :
> * Sébastien Villemot <sebastien at debian.org> [2014-01-02 20:04]:
> >
> > I was actually wondering if adding a "Breaks: liboctave1" would not do 
> > the job. I am still unsure. I guess it depends on whether non-Forge 
> > packages depending on liboctave1 still work or not after the upgrade to 
> > Octave 3.8.
> 
> I took a quick look at the non-forge packages that depend on liboctave1, 
> which are:
> 
>    octave-vlfeat
>    sdpam
>    octave-psychtoolbox-3
>    octave-plplot
>    octave-pfstools
>    octave-nlopt
>    libsbml5-octave
>    octave-gdf
>    octave-lhapdf
>    octave-gmt
>    octave-biosig
>    octave-sundials
> 
> They contain either *.mex or *.oct files and they all seem to depend on 
> the octave interpreter for working.
> 
> We could test them and check whether they still work with octave 3.8.0 
> installed, provided that liboctave1 is not removed.  However, it will be 
> perhaps simpler to plan a transition and get all those packages rebuilt 
> against liboctave2.

Of course these packages will need to be rebuilt against liboctave2,
otherwise octave 3.8 will not migrate to testing.

But this was not my point. I am thinking about partial upgrades, i.e. a
situation where the user upgrades octave but not some package depending
on it (and that package will therefore still be using liboctave1). And,
if partial upgrades do not work, then it is our duty to avoid them by
adding the corresponding Breaks.

-- 
 .''`.    Sébastien Villemot
: :' :    Debian Developer
`. `'     http://www.dynare.org/sebastien
  `-      GPG Key: 4096R/381A7594


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part
URL: <http://lists.alioth.debian.org/pipermail/pkg-octave-devel/attachments/20140102/6e3d38d7/attachment.sig>