On Thu, Oct 04, 2007 at 02:19:30PM +0200, Thomas Girard wrote:
> 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.

I know that, we use a backport of the *flub* packages internally
together with Python packages recompiled for python2.5.

> 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.

That was exactly my question.

Kind regards,
Philipp Kern
Debian Developer

Attachment: signature.asc
Description: Digital signature

Reply via email to