[Pkg-octave-devel] Bug#520220: octave3.0: This release candidate snapshot should not enter testing

[Thomas Weber]

On Thu, Mar 19, 2009 at 12:30:05PM +0100, Rafael Laboissiere wrote:
> * Thomas Weber <thomas.weber.mail at gmail.com> [2009-03-18 23:05]:
> 
> > On Wed, Mar 18, 2009 at 09:30:59AM +0100, Rafael Laboissiere wrote:
> > > Package: octave3.0
> > > Version: 1:3.0.4~rc5-2
> > > Severity: serious
> > > 
> > > This version of the octave3.0 package is based on a release candidate
> > > snapshot for the upcoming 3.0.4 version.  The upstream authors have told 
> > > us [1] that release candidates should not be distributed as Debian packages.
> > > 
> > > Let us keep this version in unstable for now.
> > 
> > Any plan how we should continue with this? We can't let any binary
> > octave-forge package into testing like that. The current octave3.0
> > packages in unstable and testing are ABI-incompatible.
> 
> My feeling is that 1:3.0.4~rc5-2 is of release quality. The only know
> regression from 3.0.3 is fixed by a patch in Debian.  I am waiting to see
> what Jaroslav Hajek  has to say about this.  In the meanwhile, I filed this
> bug report to avoid going against the upstream wishes as regards the version
> of the package in testing.
> 
> That said, I think we could upload the octave-forge packages to unstable,
> building them against 3.0.4~rc5.  Otherwise, if you do not feel confident
> about this, we could wait for Octave 3.2, but I think the released is not
> yet scheduled.

Hmm, maybe I'm wrong about that, but:
If we build octave-forge packages against current unstable (3.0.4RC) and
they enter testing with 3.0.1, the packages with .oct files will break,
won't they?

	Thomas