On Fri, Sep 12, 2008 at 01:19:58PM +0200, Frans Pop wrote: > 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.
The obvious fix (dummy transitional packages) is in our SVN; it’a bit ugly, but seems to work. It certainly deserves a second pair of eyes, I might easily have missed something. Cheers, -- Michael Schutte <[EMAIL PROTECTED]>
signature.asc
Description: Digital signature