Bug#430422: Changing omniorb4 source package name (was: Re: Bug#430422: omniorb4: Out of date / python2.5 transition)

2007-10-18 Thread Philipp Kern
On Thu, Oct 18, 2007 at 02:57:34PM +0200, Thomas Girard wrote: > Having thought about this again for a while, I'm no longer convinced we > should change the source package name. Indeed, the API was changed, but > we are not going to support both omniorb4.0 and omniorb4.1. > > omnievents, which bui

Bug#430422: Changing omniorb4 source package name (was: Re: Bug#430422: omniorb4: Out of date / python2.5 transition)

2007-10-18 Thread Thomas Girard
Hi all, > is the question if it's (intended to be) fully API compatible, then the > source package could just me updated. > > > The library packages do change name (from foo4 to foo4-1) due to the > > soname change, so anyone depending on it (i.e. omnievents) will be > > broken until they are reb

Bug#430422: omniorb4: Out of date / python2.5 transition

2007-10-04 Thread Philipp Kern
Hi Floris, on Thu, Oct 04, 2007 at 03:06:18PM +0100 you wrote: > I must admit I only use omniORB through omniORBpy, so don't really > know the anser. I had a look in the release notes and documentation > but didn't find anything explicitly, so I've asked this on the > omniorb-users lists. is the

Bug#430422: omniorb4: Out of date / python2.5 transition

2007-10-04 Thread Floris Bruynooghe
On 04/10/2007, Philipp Kern <[EMAIL PROTECTED]> wrote: > On Thu, Oct 04, 2007 at 02:19:30PM +0200, Thomas Girard wrote: > > 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

Bug#430422: omniorb4: Out of date / python2.5 transition

2007-10-04 Thread Philipp Kern
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

Bug#430422: omniorb4: Out of date / python2.5 transition

2007-10-04 Thread Thomas Girard
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 req

Bug#430422: omniorb4: Out of date / python2.5 transition

2007-10-04 Thread Philipp Kern
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

Bug#430422: omniorb4: Out of date / python2.5 transition

2007-06-25 Thread Floris Bruynooghe
Package: omniorb4 Version: 4.1.0-1~flub1 Severity: normal Tags: patch Hi As per http://lists.debian.org/debian-python/2007/06/msg9.html we should be preparing for the python2.5 transition. As it happens python-omniorb2 needs to be upgraded to omniORBpy-3.0 to work with python2.5 due to the f