[DRE-maint] Bug#498700: Missing upgrade path from libdb4.2-ruby1.8 to libdb-ruby1.8

Adeodato Simó dato at net.com.org.es
Sun Sep 28 12:43:30 UTC 2008

* Frans Pop [Fri, 12 Sep 2008 13:19:58 +0200]:

> Package: libdb-ruby1.8
> Version: 0.6.5-1
> Severity: serious
> Justification: Causes unclean upgrades

> I have dhelp installed on a Lenny system, which depends on
> libdb4.2-ruby1.8. After upgrading the system at some point I was left
> with libdb4.2-ruby1.8 still installed as "obsolete package".

> At first I thought this was some temporary inconsistency in testing, but
> I now find that libdb4.2-ruby1.8 has been renamed to libdb-ruby1.8,
> which provides the old package.

> However, it seems that no upgrade path is provided to ensure that users
> that already had the old package installed will get the new package.
> Only if libdb-ruby1.8 is selected manually will the old package get
> replaced.

> IMO this is a serious issue as libdb4.2-ruby1.8 is also present in
> unstable and the missing upgrade path will therefore also affect Etch to
> Lenny upgrades.

Isn't this a bug of our upgrading tools, that should prefer to install a
new, non-obsolete package A that Provides: B, rather than keeping a
no-longer-present-in-the-lists B installed?

Adeodato Simó                                     dato at net.com.org.es
Debian Developer                                  adeodato at debian.org
There is no man so good who, were he to submit all his thoughts to the
laws, would not deserve hanging ten times in his life.
                -- Michel de Montaigne

More information about the Pkg-ruby-extras-maintainers mailing list