notfound 430422 4.1.0-1~flub1
found 430422 4.0.6-2.3
thanks

On Thu, Oct 04, 2007 at 11:55:28AM +0200, Philipp Kern wrote:
> Hi Floris,
> 
> On Sun, Jun 24, 2007 at 01:19:10PM +0100, Floris Bruynooghe wrote:
> > Attached is the .diff.gz against the upstream omniORB-4.1 tarball that
> > does the required work.  It fixes almost all of omniorb4's outstanding
> > bugs too as added bonus and should only need minor changes for adoption
> > in Debian itself.
> 
> are omniorb 4.1 and omniorbpy 3.0 fully compatible to 4.0 and 2.X? I.e.
> do we have to expect that an upgrade breaks existing applications?

Floris is currently working on packaging omniorb 4.1 (see [1]).
If I recall correctly, omniorb 4.0 is *not* compatible with Python 2.5,
so in order to be able to provide python 2.5 modules for omniorb we need
to move forward to omniorb 4.1.

But you're right, we'll need to check if it's possible to upgrade
without breaking existing applications. If it's not we'll probably have
to package this in a separate source package.

Thomas

[1] http://alioth.debian.org/projects/pkg-corba



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to