[Pkg-corba-devel] omniorb4 package name change

[thomas.g.girard]

(Please discard the previous empty email)

Hello Floris,

On Tue, 3 Jun 2008 20:46:37 +0100, Floris Bruynooghe <floris.bruynooghe at gmail.com> wrote:
>> > Thought a bit more about this.  We could make an update to stable
>> > where we add a preinst and postinst script to save and restore the
>> > database, and then change the postrm script to not delete the
>> > databases unless they are purged.  If not we should mention this in
>> > the release notes.
> 
> So what would you think of this?  Would an update to stable be
> acceptable?  If not we might want to reconsider the current -2
> package. 

Hmmm... I don't think uploading something to stable is the right way to go. Whatever the
mistakes are in current stable packages, we need to handle them when updating. I'm sorry
I don't have a lot of time right now to have a look, but I will do ASAP.

>> I've compiled omniorb and tried to update from 4.1.2-1+b1 to 4.1.2-2
>> (using dpkg -i), and it failed:
> 
> I've tried to reproduce this but failed.  All upgrades I test work.  I
> have noticed a silly bug in the DB migration script though (not sure
> how that got in, I thought I tested everything properly), so not all
> was in vain! 

I'll give it another try. So, to recap, currently:
 * updating from 4.1.2-1+b1 to 4.1.2-2 works, but
 * upgrading from etch's 4.0.6-2.1 to 4.1.2-2 fails

Is that correct?

Thanks,
Thomas