[Pkg-octave-devel] Bug#463039: why does octave3.0 provide: octave2.9?

[Thomas Weber]

Am Dienstag, den 05.02.2008, 13:50 +0100 schrieb Rafael Laboissiere:
> * Thomas Weber <thomas.weber.mail at gmail.com> [2008-02-05 13:00]:
> 
> > 
> > Am Dienstag, den 05.02.2008, 12:22 +0100 schrieb Rafael Laboissiere:
> > > * Thomas Weber <thomas.weber.mail at gmail.com> [2008-02-05 09:33]:
> > > 
> > > > I'm for the the dummy 2.9 package. It has the added advantage of getting
> > > > rid of the "octave" package in a sensible way (we simply don't build it
> > > > anymore). 
> > > 
> > > Okay, if there are no further objections, I will soon implement the dummy
> > > 2.9 packages.  This means that we will have to use the infamous epoch again.
> > 
> > Only for the octave2.9 packages, or do I misunderstand something?
> 
> I was thinking about having the octave3.0 source package produce the 2.9
> packages.  

This means an epoch in octave3.0's version number, but apart from that,
it's okay. There are lots of packages with epochs in Debian, so I guess
I should give up my resistance against one.

> The reason for that is that we are requiring the removal of 
> octave2.9 from Debian.  Perhaps we should release the new dummy octave2.9
> right now and ask for the removal only after the release of lenny.  This
> will ensure a better upgrade for the users of testing.

Thinking about it, this is the only way that makes sense, isn't it?
Otherwise, we would need a dummy octave2.9 source package. 

Okay, I guess we agree on this. octave3.0 will provide dummy octave2.9
packages. 

	Thomas