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

[Frans Pop]

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.

The same issue may also affect libdb-ruby1.9.

-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.27-rc5 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash