Bug#251458: [Pkg-firebird-general] Re: Bug#251458: firebird: remote vulnerability

[Grzegorz B. Prokopski]

On Wed, 2004-07-28 at 11:24, Daniel Urban wrote:
> > 
> > 
> > > If this would happen I am not so sure about the usefulness of the
> > > firebird2 naming.
> > 
> > Maybe we can rename it to firebird later, but I am not sure what 
> > reflections a rename will have right now, before sarge release.
> > 
> I'm for renaming firebird2 to firebird.
> Could we do it now? Greg? Would be a problem with it now?

Yes, it would be.  But really, there's no point doing that.
Having it as a separate package gives us more flexibility:

* we would be able to push old fb into Sarge (i.e. with *big* security
warning and access allowed only from localhost, etc.) if we didn't
have fb2 in time (mind you, fb2 debs are NOT in testing yet and they
haven't had really wide testing as they only just hit unstable).

* we can still have old firebird packages around (i.e. in an unofficial
repository) and they would NOT be:
 - mistaken with firebird2 packages
 - auto-upgraded on standard system upgrade and overriden with 1.5.x
   version (otherwise you would need to keep them "on hold" which
   would make the automatic updates from unofficial repository
   impossible)

This is a common practice that you add a release number to the package
name when you want to keep the old version around for users that might
need it.  Just see the output of 'apt-cache search tk8'.

Cheers,

				GBP
-- 
Grzegorz B. Prokopski      <gadek@debian.org>
Debian GNU/Linux           http://www.debian.org
SableVM - LGPL'ed Java VM  http://www.sablevm.org
Why SableVM ?!?            http://devel.sablevm.org/wiki/Features