Update of opensync

[Guido Diepen]

Hi everybody,

don't know how closely you are following the opensync development, but I saw
that very recently the OpenSync folks have released a new version of the
unstable 0.3x branch, namely 0.39!!

In the release notes http://www.opensync.org/wiki/opensync-0.39-notes it is
stated that now there should be a stable API. Unfortunately I don't know yet
whether the python plugin stuff is already working at the moment.... ;)

Kind regards,

Guido Diepen

[Dr J A Gow]

Post by Guido Diepen
Hi everybody,
don't know how closely you are following the opensync development, but I saw
that very recently the OpenSync folks have released a new version of the
unstable 0.3x branch, namely 0.39!!
In the release notes http://www.opensync.org/wiki/opensync-0.39-notes it is
stated that now there should be a stable API. Unfortunately I don't know yet
whether the python plugin stuff is already working at the moment.... ;)

Still can't get Opensync's python-module to build - this is what's holding
up my fixes to the sync-engine opensync0.4x support.

John.

[Mark Ellis]

Post by Dr J A Gow

Post by Guido Diepen
Hi everybody,
don't know how closely you are following the opensync development, but I saw
that very recently the OpenSync folks have released a new version of the
unstable 0.3x branch, namely 0.39!!
In the release notes http://www.opensync.org/wiki/opensync-0.39-notes it is
stated that now there should be a stable API. Unfortunately I don't know yet
whether the python plugin stuff is already working at the moment.... ;)

Still can't get Opensync's python-module to build - this is what's holding
up my fixes to the sync-engine opensync0.4x support.
John.

John, you had any luck with this ? I've just started to take a look at
it, and they seem to have changed a few things don't they ...

Mark

[Dr J A Gow]

Post by Mark Ellis
John, you had any luck with this ? I've just started to take a look at
it, and they seem to have changed a few things don't they ...
Mark

Just checked it again: I _still_ can't get Opensync SVN python-module to
build.

John.

[Mark Ellis]

Post by Dr J A Gow

Post by Mark Ellis
John, you had any luck with this ? I've just started to take a look at
it, and they seem to have changed a few things don't they ...
Mark

Just checked it again: I _still_ can't get Opensync SVN python-module to
build.
John.

Well, I've had a good old hack at this, I can get it into a buildable
state, but I'm in no doubt that it won't actually work. It seems to have
python objects as userdata coming out of nowhere by functions that have
been removed from the public api !!!

Just out of interest, has anyone asked the opensync guys if they are
going to maintain this ?

Mark

[Mark Ellis]

Post by Mark Ellis

Post by Dr J A Gow

Post by Mark Ellis
John, you had any luck with this ? I've just started to take a look at
it, and they seem to have changed a few things don't they ...
Mark

Just checked it again: I _still_ can't get Opensync SVN python-module to
build.
John.

Well, I've had a good old hack at this, I can get it into a buildable
state, but I'm in no doubt that it won't actually work. It seems to have
python objects as userdata coming out of nowhere by functions that have
been removed from the public api !!!
Just out of interest, has anyone asked the opensync guys if they are
going to maintain this ?

Ok, had a revelation.

Attached is a patch to the 0.36 python plugin (the last release) which I
hope will make it work for 0.39, and presumably trunk. It may not apply
completely cleanly to trunk, but I can't seem to check that out at the
moment.

I can't test it properly myself at the moment, but am reasonably
confident, and thought I'd throw it out there for you guys to play
with !

Mark

[Dr J A Gow]

Post by Mark Ellis

Post by Mark Ellis

Post by Dr J A Gow

Post by Mark Ellis
John, you had any luck with this ? I've just started to take a look at
it, and they seem to have changed a few things don't they ...
Mark

Just checked it again: I _still_ can't get Opensync SVN python-module to
build.
John.

Well, I've had a good old hack at this, I can get it into a buildable
state, but I'm in no doubt that it won't actually work. It seems to have
python objects as userdata coming out of nowhere by functions that have
been removed from the public api !!!
Just out of interest, has anyone asked the opensync guys if they are
going to maintain this ?

Ok, had a revelation.
Attached is a patch to the 0.36 python plugin (the last release) which I
hope will make it work for 0.39, and presumably trunk. It may not apply
completely cleanly to trunk, but I can't seem to check that out at the
moment.
I can't test it properly myself at the moment, but am reasonably
confident, and thought I'd throw it out there for you guys to play
with !

Thanks for this Mark. I was trying to avoid getting to embroiled in
Opensync innards so this is much appreciated. I will test as soon as I
can, probably will fix it up for trunk as I am running Opensync trunk at
the moment. Fingers crossed! If it works I will prioritize the Opensync
0.4x fixes in sync-engine.

John.

[Mark Ellis]

Post by Dr J A Gow

Post by Mark Ellis

Post by Mark Ellis

Post by Dr J A Gow

Post by Mark Ellis
John, you had any luck with this ? I've just started to take a look at
it, and they seem to have changed a few things don't they ...
Mark

Just checked it again: I _still_ can't get Opensync SVN python-module to
build.
John.

Well, I've had a good old hack at this, I can get it into a buildable
state, but I'm in no doubt that it won't actually work. It seems to have
python objects as userdata coming out of nowhere by functions that have
been removed from the public api !!!
Just out of interest, has anyone asked the opensync guys if they are
going to maintain this ?

Ok, had a revelation.
Attached is a patch to the 0.36 python plugin (the last release) which I
hope will make it work for 0.39, and presumably trunk. It may not apply
completely cleanly to trunk, but I can't seem to check that out at the
moment.
I can't test it properly myself at the moment, but am reasonably
confident, and thought I'd throw it out there for you guys to play
with !

Thanks for this Mark. I was trying to avoid getting to embroiled in
Opensync innards so this is much appreciated. I will test as soon as I
can, probably will fix it up for trunk as I am running Opensync trunk at
the moment. Fingers crossed! If it works I will prioritize the Opensync
0.4x fixes in sync-engine.

Ditto on the innards :)

Managed to get trunk, and regenerated the patch to build against it. Not
much success with testing however, due to some apparently dodgy code in
the opensync python wrapper, with C style comments and other whatnot. I
know absolutely nothing about swig ...

Mark

[Dr J A Gow]

Post by Mark Ellis
Ditto on the innards :)
Managed to get trunk, and regenerated the patch to build against it. Not
much success with testing however, due to some apparently dodgy code in
the opensync python wrapper, with C style comments and other whatnot. I
know absolutely nothing about swig ...

Just went to sort out another machine with a fresh build of Opensync to
try this: would you believe it looks like Opensync have managed to break
the evo2 plugin in trunk! It just hangs (definitely the evo plugin is
the problem, file-sync works ok).

Anybody else seen this? If so I'll report it on the Opensync bugtracker.

John.

[Dr J A Gow]

Post by Dr J A Gow

Post by Mark Ellis
Ditto on the innards :)
Managed to get trunk, and regenerated the patch to build against it. Not
much success with testing however, due to some apparently dodgy code in
the opensync python wrapper, with C style comments and other whatnot. I
know absolutely nothing about swig ...

Just went to sort out another machine with a fresh build of Opensync to
try this: would you believe it looks like Opensync have managed to break
the evo2 plugin in trunk! It just hangs (definitely the evo plugin is
the problem, file-sync works ok).
Anybody else seen this? If so I'll report it on the Opensync bugtracker.

To add to my above, I really don't know what the Opensync people are
doing with their trunk at the moment - nothing seems to work properly.
Evo2, xslt-format, python-module either won't build or are broken at
run-time.

I can get 0.39 to build and run, but I am really not sure whether to
push forward with 0.39 to fix up the sync-engine conversions, or to just
wait until the opensync svn tree is a bit more stable before making the
changes. Chances are Opensync will change something and I will still be
chasing a moving target..... Grrrrr!

John.

[Mark Ellis]

Post by Dr J A Gow

Post by Dr J A Gow

Post by Mark Ellis
Ditto on the innards :)
Managed to get trunk, and regenerated the patch to build against it. Not
much success with testing however, due to some apparently dodgy code in
the opensync python wrapper, with C style comments and other whatnot. I
know absolutely nothing about swig ...

Just went to sort out another machine with a fresh build of Opensync to
try this: would you believe it looks like Opensync have managed to break
the evo2 plugin in trunk! It just hangs (definitely the evo plugin is
the problem, file-sync works ok).
Anybody else seen this? If so I'll report it on the Opensync bugtracker.

To add to my above, I really don't know what the Opensync people are
doing with their trunk at the moment - nothing seems to work properly.
Evo2, xslt-format, python-module either won't build or are broken at
run-time.
I can get 0.39 to build and run, but I am really not sure whether to
push forward with 0.39 to fix up the sync-engine conversions, or to just
wait until the opensync svn tree is a bit more stable before making the
changes. Chances are Opensync will change something and I will still be
chasing a moving target..... Grrrrr!
John.

Hmm, I've had another dabble too, and can see there are a number of
problems with the python bindings. I would say unless we want to help
out with opensync core, best to leave the whole thing until 0.40

Mark

[Dr J A Gow]

Post by Mark Ellis

Post by Dr J A Gow

Post by Dr J A Gow

Post by Mark Ellis
Ditto on the innards :)
Managed to get trunk, and regenerated the patch to build against it. Not
much success with testing however, due to some apparently dodgy code in
the opensync python wrapper, with C style comments and other whatnot. I
know absolutely nothing about swig ...

Just went to sort out another machine with a fresh build of Opensync to
try this: would you believe it looks like Opensync have managed to break
the evo2 plugin in trunk! It just hangs (definitely the evo plugin is
the problem, file-sync works ok).
Anybody else seen this? If so I'll report it on the Opensync bugtracker.

To add to my above, I really don't know what the Opensync people are
doing with their trunk at the moment - nothing seems to work properly.
Evo2, xslt-format, python-module either won't build or are broken at
run-time.
I can get 0.39 to build and run, but I am really not sure whether to
push forward with 0.39 to fix up the sync-engine conversions, or to just
wait until the opensync svn tree is a bit more stable before making the
changes. Chances are Opensync will change something and I will still be
chasing a moving target..... Grrrrr!
John.

Hmm, I've had another dabble too, and can see there are a number of
problems with the python bindings. I would say unless we want to help
out with opensync core, best to leave the whole thing until 0.40
Mark

Agreed. I'll keep watching the Opensync SVN for changes that may be
pertinent and start work once I can build the thing.

John.