On Tue, 2010-05-25 at 10:34 +0200, Michael Banck wrote: > Hi, > > On Tue, May 25, 2010 at 09:17:35AM +0100, Mark Ellis wrote: > > On Mon, 2010-05-24 at 22:08 +0200, Michael Banck wrote: > > > tags 562159 -patch > > > thanks > > > > > > Hi, > > > > > > On Mon, May 24, 2010 at 03:46:26PM +0100, Mark Ellis wrote: > > > > This is caused by a change in swig from 1.3.37. The attached patch fixes > > > > this at source level, unlike the other patches mentioned. Please apply > > > > this, python-opensync is completely useless without it. > > > > > > That patch is for 0.22, unstable has 0.39 and it does not seem to apply > > > to that version. > > > > > > > > > Michael > > > > Sorry, did I attach it to the wrong section ? Yes, the patch is for > > 0.22, and needs to be applied to squeeze/testing. > > Ah, ok. I am afraid 0.22 will be removed from testing soonish, though. > It is basically unmaintained upstream for years now and maintaining it > over the squeeze lifetime seems unrealistic. >
Ouch, this is very very very bad news. I know 0.22 is basically unmaintained, but from my experience with 0.39, this will mean that syncing with synce (Windows Mobile) will be impossible in testing. Apart from the general problems with the python wrapper, 0.39 fails with plugins that don't require a configuration, and there is a bizarre g_slice error that I have yet to identify. > > The python wrapper of 0.39 in unstable is a completely different story, > > and I don't believe has any chance of working properly at the moment. > > Yeah, possibly. > > > Michael
signature.asc
Description: This is a digitally signed message part
