[Fwd: [Bug 584997] Re: TypeError in python wrapper, caused by swig change]

Discussion:

Mark Ellis

2011-01-25 12:53:03 UTC

I'm sure there are people out there using this. If so please feedback to
this bug, or it gets scrapped.

-------- Forwarded Message --------

Subject: [Bug 584997] Re: TypeError in python wrapper, caused by swig
change
Date: Tue, 25 Jan 2011 10:03:09 +0100
Any testers of the lucid-proposed package? As this has been in -proposed
for nearly half a year, I'll remove the proposed package soon if there
is no feedback. Thank you!
--
You received this bug notification because you are a direct subscriber
of the bug.
https://bugs.launchpad.net/bugs/584997
TypeError in python wrapper, caused by swig change
New
Fix Released
Fix Committed
SWIG 1.3.37 introduced, rightly or wrongly, some changes in the way
python is handled. This causes a crippling TypeError in python-
opensync built with later versions of swig, such as the package in
10.04 lucid. The following patch will fix this problem, it will work
ok with any version but is only required in builds on lucid. Please
apply, python-opensync is crippled without this.
---
Description: Fix for change in SWIG after 1.3.36
Upstream 0.2x branch is essentially unmaintained.
Forwarded: no
Last-Update: 2010-05-24
diff -Nurp opensync-0.22.orig/wrapper/opensync.i opensync-0.22/wrapper/opensync.i
--- opensync-0.22.orig/wrapper/opensync.i 2007-03-27 12:49:09.000000000 +0100
+++ opensync-0.22/wrapper/opensync.i 2010-05-21 18:36:46.857447188 +0100
@@ -82,7 +82,7 @@ typedef struct {} OSyncHashTable;
%extend OSyncChange {
OSyncChange(PyObject *obj=NULL) {
OSyncChange *change = NULL;
- if (obj)
+ if ((obj) && (obj != Py_None))
change = (OSyncChange *)PyCObject_AsVoidPtr(obj);
else
change = osync_change_new();
https://bugs.launchpad.net/opensync/+bug/584997/+subscribe

Tejas Guruswamy

2011-01-25 16:29:01 UTC

Permalink

Post by Mark Ellis
I'm sure there are people out there using this. If so please feedback to
this bug, or it gets scrapped.

Hi mark, I am almost sure I did encounter the problem and solved it with
the proposed patch, but not totally sure. How can I make sure of that? I
would not send garbage to the bug page.
And, should I post a feedback in the bug page even if I applied the
patch manually (i.e., I never enabled nor used -proposed) ?
Thanks
Andrea

We've been using this patch successfully in openSUSE for many months
now, will that help?

Regards,
Tejas

Post by Mark Ellis
-------- Forwarded Message --------

Mark Ellis

2011-01-25 20:20:59 UTC

Permalink

Post by Tejas Guruswamy

Post by Mark Ellis
I'm sure there are people out there using this. If so please feedback to
this bug, or it gets scrapped.

We've been using this patch successfully in openSUSE for many months
now, will that help?
Regards,
Tejas

Thanks, but they were basically looking for ubuntu lucid users to check
out the patched package i'd uploaded to -proposed to confirm it didn't
screw anything up.

Post by Tejas Guruswamy

Post by Mark Ellis
-------- Forwarded Message --------

------------------------------------------------------------------------------
Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
Finally, a world-class log management solution at an even better price-free!
Download using promo code Free_Logger_4_Dev2Dev. Offer expires
February 28th, so secure your free ArcSight Logger TODAY!
http://p.sf.net/sfu/arcsight-sfd2d
_______________________________________________
SynCE-Devel mailing list
https://lists.sourceforge.net/lists/listinfo/synce-devel

Andrea Vai

2011-01-25 16:21:37 UTC

Permalink

Post by Mark Ellis
I'm sure there are people out there using this. If so please feedback to
this bug, or it gets scrapped.

Post by Mark Ellis
-------- Forwarded Message --------