Discussion:
RAPIError when creating partnership
Iain Buchanan
2010-10-08 01:29:54 UTC
Permalink
Hi again,

I've been working through some build problems, and I've now managed to
rebuild all synce and libopensync packages cleanly. These are the
version I'm using:

[IP-] [ ] app-pda/dynamite-0.1.1:0
[I-O] [ ] app-pda/libopensync-0.22:0
[IP-] [ ] app-pda/libopensync-plugin-evolution2-0.22:0
[IP-] [ ] app-pda/libopensync-plugin-python-0.22:0
[IP-] [ ] app-pda/msynctool-0.22:0
[IP-] [ ] app-pda/orange-0.4:0
[I-O] [ ] app-pda/synce-hal-0.15:0
[I-O] [ ] app-pda/synce-librapi2-0.15:0
[IP-] [ ] app-pda/synce-librra-0.14:0
[IP-] [ ] app-pda/synce-librtfcomp-1.1:0
[I-O] [ ] app-pda/synce-libsynce-0.15:0
[I-O] [ ] app-pda/synce-sync-engine-0.15:0

now, when I try and create a partnership (all partnerships, msynctool
groups, and ~/.synce directory removed) I get this simple message:

$ create_partnership.py "Palm" "Contacts,Calendar"
Creating partnership...

error: failed to create partnership
error: org.freedesktop.DBus.Python.pyrapi2.RAPIError

I've attached the sync-engine.log if anyone is able to shed any light :)

many thanks,
--
Iain Buchanan <iaindb at netspace dot net dot au>

<SilverStr> media ethics is an oxymoron, much like Jumbo Shrimp and
Microsoft Works.
<MonkAway> not to mention NT Security
Iain Buchanan
2010-10-11 00:57:34 UTC
Permalink
Post by Iain Buchanan
$ create_partnership.py "Palm" "Contacts,Calendar"
Creating partnership...
error: failed to create partnership
error: org.freedesktop.DBus.Python.pyrapi2.RAPIError
I set up a new user account, and I don't get this error, nor the
E_IS_CAL error I posted earlier. Strange. Any thoughts apart from
blowing away my home directory?

thanks :)
--
Iain Buchanan <iaindb at netspace dot net dot au>

"On the Internet, no one knows you're using Windows NT"
(Submitted by Ramiro Estrugo, ***@fateware.com)
Iain Buchanan
2010-10-12 00:03:00 UTC
Permalink
It's aliii-i-i-i-ive!

So, the RAPI error went after I rebooted my device.

The E_IS_CAL error went when I changed my default cal in evolution to a
local one, not a caldav one.

Then I got the TypeError in opensync... for which I had to apply the
patch from Mark in May, now that's gone.

And THEN I could sync.

phew. Only lost a few contacts in the process. Now to see if Gentoo
wants to release a new (old) libopensync...
--
Iain Buchanan <iaindb at netspace dot net dot au>

Think lucky. If you fall in a pond, check your pockets for fish.
-- Darrell Royal
Loading...