[Pkg-corba-devel] New releases

[Thomas Girard]

> Hi

Hello Floris,

> I think the packages in the trunk are fine for release into unstable.

Last time I tried updating 4.1.2 to 4.1.3 I hit a bug because for some 
reason omniorb-nameserver and omniorb4-nameserver still include the 
startup script, causing naming server to be started twice.

Also, since renaming of omniorb4 to omniorb will not occur in 4.1.2-2 
but in 4.1.3-1, some Conflicts/Replace/Depends must be updated.

I'm working on this today, I will let you know about progress.

By the way, 4.1.4 was just released. I think we can push 4.1.3 anyway 
when it's ready; this will be the version for the omniorb4 -> omniorb 
naming transition.

> I'm not sure yet if it's still worth persuing a new omniORBpy in
> stable, no-one has complained about it and clearly I don't seem to
> have enough time to do this (I imagine there's more hoops to jump
> though and more policies to read up on).

Agreed.

Regards,

Thomas