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

[Mike Miller <mtmiller@debian.org>]

On Fri, Feb 14, 2014 at 12:26:02 +0100, Rafael Laboissiere wrote:
> 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.

I started classifying already based on my previous mail, but I had
inadvertently rebuilt arch:all packages. I've now reinstalled most of
these from sid and I'll update the wiki to reflect these case (1)
packages.

I notice that the Breaks list includes octave-secs1d, which is arch:all
and doesn't look like it needs to be rebuilt. Was this a mistake?

-- 
mike