[Pkg-octave-devel] Bug#735557: transition: octave3.8

[Rafael Laboissiere]

* Mike Miller <mtmiller at debian.org> [2014-02-13 17:16]:

> On Sun, Jan 19, 2014 at 10:58:34 +0100, Rafael Laboissiere wrote:
>> * Mike Miller <mtmiller at debian.org> [2014-01-18 23:52]:
>>>
>>> [snip]
>>>
>>> How about that wiki page to track the transition? Is there a 
>>> template we can reuse to start something?
>>
>> https://wiki.debian.org/Teams/DebianOctaveGroup/Octave3.6Transition
>
> Created new page for 3.8 transition (sorry for the delay):
>
> https://wiki.debian.org/Teams/DebianOctaveGroup/Octave3.8Transition

Thanks for this, Mike.

I think that we will face four different situations (at least) in this 
transition and that could be reflected somehow in the wiki page:

1) The package does not contain any .oct or .mex file and works with 3.8. 
Nothing to do here.

2) The package does not contain any .oct or .mex file but fails to work 
with 3.8.  A sourceful upload is required.

3) The package contains .oct and/or .mex files and compiles & runs 
correctly against 3.8.  A binNMU is required.

3) The package contains .oct and/or .mex files but fails to compile or 
run against 3.8.  A sourceful upload is required.

A good starting point for classifying the packages is the Breaks list of 
the octave package, as currently in Git.  Furthermore, we should include 
the non-Forge packages in the wiki page.

Rafael