[Pkg-octave-devel] [RFU] octave3.0 3.0.5-5

[Thomas Weber]

On Thu, May 21, 2009 at 10:43:25PM +0200, Rafael Laboissiere wrote:
> * Rafael Laboissiere <rafael at debian.org> [2009-05-21 11:45]:
> 
> > The octave3.0_3.0.5-4 has entered testing yesterday.  I will upload today
> > version 3.0.5-5 as in Git 274fe95.  This will close Bug#529049, which was
> > an ITP for the Octave-Forge pkg bugfix-3.0.5.
> 
> Actually, I postponed this upload because I just discovered a problem
> with the Debian packages.  Imagine a user who has installed older
> versions of the Octave Forge packages, for which the packages directory
> was not yet versioned (i.e. /usr/share/octave/packages/ instead of
> /usr/share/octave/packages/3.0/).  This worked fine for version of
> octave3.0 prior to 1:3.0.4~rc3-3. Now, if this user upgrades to octave
> 3.0.5, then all the Octave-Forge packages will become unavailable, even
> though apt-get will happily do the upgrade.
> 
> In order to help users to be aware of the problem, I added a Breaks field
> to debian/in/control (Git commit 648d10c).  I used "<<" relationships to
> the versions of the Octave-Forge packages that were built with version
> lesser than 0.6.4 of octave-pkg-dev.  I did some tests with apt-get and
> it seems to work.  I would though appreciate if someone could look at my
> changes before I upload 3.0.5-5.

Well, I took a look at your changes, but I don't have any unstable
chroot with a 3.0.4 version in it. I guess the easist way to mitigate
that risk is waiting a few days so most testing users will have 1:3.0.5-4
installed. Additionally, I think that most users will upgrade Octave and
octave-forge packages, not just Octave only.

	Thomas