[Pkg-octave-devel] Octave 3.4

Thomas Weber tweber at debian.org
Thu Feb 10 14:55:54 UTC 2011

On Wed, Feb 09, 2011 at 04:53:36PM -0600, Jordi Gutiérrez Hermoso wrote:
> On 9 February 2011 14:45, Thomas Weber <tweber at debian.org> wrote:
> > Okay, so here's a draft plan:
> > 1) I will upload octave-forge packages to be built against the current
> > 3.2 package.
> This upload is without making the move to git+upstream yet, right?

Yes. It's mostly meant to have the most recent stuff in unstable for
octave-forge while preparing the switch for Octave.

> > 2) We will switch the octave-forge packages over to
> > git-with-upstream source.
> Do you want to split them? 

Hm, yes. They are, after all, shipped in separate tarballs. I don't
think we should convert the upstream SVN into a git repository. 

> Should we agree on who does which packages?

I'm not at a point where I'm actually able to do much. This will
probably become worse from now on (I have my plate full with stuff in
real life right now).

> > 4) Switch to Octave 3.4. I haven't made up my mind about this yet,
> > that's why I've put it at the end.
> What about the soname and symbol versioning for the library? That's
> part of the big change for Octave itself, right?


> > - I want our patches to still appear at
> > http://patch-tracker.debian.org. I'm not sure what this means for
> > the workflow.
> Those are just read from the quilt patches from the uploaded package.
> Our VCS structure is irrelevant for those.

Yes, but it seems some DDs are using branches for each patch they add
and not a patch manage like quilt at all.


More information about the Pkg-octave-devel mailing list