[Pkg-octave-devel] Packaging Octave 3.8

Sébastien Villemot sebastien at debian.org
Thu Jan 2 19:04:59 UTC 2014

Le jeudi 02 janvier 2014 à 17:44 +0100, Rafael Laboissiere a écrit :
> * Rafael Laboissiere <rafael at laboissiere.net> [2013-12-30 22:31]:
> >
> > All forge packages that contain *.oct files were built for api-v48+. 
> > Version 3.8* of the octave package will break them because it has 
> > api-49+.  Some kind of relationship (like Breaks, but I am not sure) 
> > should be added to the new octave package.
> I have done some experiments here and Breaks seem to be the appropriate 
> relationship.  However, I could not manage to get aptitude automatically 
> installing new versions (with the appropriate api directory) of the forge 
> packages when the octave package containing the Breaks relationship is 
> required for installation.
> If no better solution is proposed, I will commit a new debian/control 
> with the following:


Thanks for coming up with that list.

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.

 .''`.    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/24a4f2b3/attachment.sig>

More information about the Pkg-octave-devel mailing list