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

Rafael Laboissiere rafael at debian.org
Mon Feb 4 17:09:30 UTC 2008

* Steve Langasek <vorlon at debian.org> [2008-02-03 16:32]:

> To the best of my knowledge, none of these configurations achieve that goal.
> While there's lore among Debian developers to the effect that
> "Conflicts/Replaces" will trigger the package manager to pull in the new
> package automatically as a replacement for the obsolete package, I have
> never seen this happen in practice with any of the frontends.

Thanks for the explanation.

> The only two configurations that I know to achieve this purpose are:
> - create a dummy package under the old package name, which depends on the
>   new package name
> - keep the old package name for the new version of the software

The second option is not acceptable for us.

Thanks for the suggestion, Steve.  The remaining of my reply below is
addressed to the DOG:

What should you do know?  It is clear from the discussion in this bug report
that the current Conflicts/Replaces/Provides setting is not appropriate.
However, if we generate dummy octave2.9* packages then we will have to
reintroduced the infamous epoch in the version number, which we were trying
to avoid.

I do not think we have a choice here.  If nobody objects, I will do the
necessary changes in SVN.

More information about the Pkg-octave-devel mailing list