11:25 a.m.
Hello everybody,
So after many months I was excited to try syncevolution with caldav and
carddav support today.
I executed my configuration commands as earlier posted on this mailing-list.
Please see the bellow pastebin URL that contains the details (versions,
configuration, and syncevolution commands)
http://paste.debian.net/124460/
The only n900 how-to I could find was:
http://talk.maemo.org/showthread.php?t=40278
Could somebody have a look at the pastebin and can tell me what I am
doing wrong? and what I should do to make the N900 calender and contacts
use caldav and carddav by default!
Thanks in advance,
Kind regards,
Jelle de Jong
11:52 a.m.
On Fr, 2011-07-29 at 11:25 +0200, Jelle de Jong wrote:
So after many months I was excited to try syncevolution with caldav
and
carddav support today.
I executed my configuration commands as earlier posted on this mailing-list.
Those are obsolete and no longer work in 1.1.99.5. Please follow the
WebDAV instructions in the README:
http://syncevolution.org/documentation/syncevolution-usage
If DAViCal has a URL for your user ("principal"), then you can use that
as common syncURL for both CalDAV and CardDAV. I think it supports that.
Please see the bellow pastebin URL that contains the details
(versions,
configuration, and syncevolution commands)
http://paste.debian.net/124460/
----------------------------------------------
Doing a slow synchronization may lead to duplicated items or
lost data when the server merges items incorrectly. Choosing
a different synchronization mode may be the better alternative.
Restart synchronization of affected source(s) with one of the
following sync modes to recover from this problem:
slow, refresh-from-server, refresh-from-client
Analyzing the current state:
syncevolution --status davical-caldav addressbook calendar
Running with one of the three modes:
syncevolution --sync [slow|refresh-from-server|refresh-from-client] davical-caldav
addressbook calendar
-----------------------------------------------
This is something that'll show up even with the current instructions.
It's intentional, you need to make a choice as explained above.
Note the warning in the README:
Warning: in local sync, the sync config side acts as server.
Therefore the from-server variants (one-way-from-server,
refresh-from-server) transfer data from the sync config into the
target config. The from-client variants transfer in the other
direction, even if the target config happens to access data on a
remote server.
If you want to avoid dealing with this, configure the target-config with
"preventSlowSync=0".
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
12:14 p.m.
Dear Patrick,
On 29-07-11 11:52, Patrick Ohly wrote:
Those are obsolete and no longer work in 1.1.99.5. Please follow the
WebDAV instructions in the README:
http://syncevolution.org/documentation/syncevolution-usage
If DAViCal has a URL for your user ("principal"), then you can use that
as common syncURL for both CalDAV and CardDAV. I think it supports that.
#CardDAV
https://secure.powercraft.nl/davical/caldav.php/delta/cardav/
username=delta
password=Gaod0lae
#CalDAV
https://secure.powercraft.nl/davical/caldav.php/gamma/home/
username=gamma
password=roch8Jey
Could you please create an example configuration based on the above
credentials. I can't make head or tails out of the syncevolution-usage
documentation without a working example, i'm sorry..
Thanks in advance,
Kind regards,
Jelle de Jong
12:24 p.m.
On Fr, 2011-07-29 at 12:14 +0200, Jelle de Jong wrote:
Dear Patrick,
On 29-07-11 11:52, Patrick Ohly wrote:
> Those are obsolete and no longer work in 1.1.99.5. Please follow the
> WebDAV instructions in the README:
> http://syncevolution.org/documentation/syncevolution-usage
>
> If DAViCal has a URL for your user ("principal"), then you can use that
> as common syncURL for both CalDAV and CardDAV. I think it supports that.
#CardDAV
https://secure.powercraft.nl/davical/caldav.php/delta/cardav/
username=delta
password=Gaod0lae
#CalDAV
https://secure.powercraft.nl/davical/caldav.php/gamma/home/
username=gamma
password=roch8Jey
Could you please create an example configuration based on the above
credentials. I can't make head or tails out of the syncevolution-usage
documentation without a working example, i'm sorry..
Can you point to specific aspects that you don't understand and which
need to be explained better?
Anyway, here's the WebDAV example adapted to separate URL and
credentials for CalDAV and CardDAV. Instead of configuring "addressbook"
and "calendar", separate configs are used with one source in each.
syncURL is given explicitly.
# configure target config for CardDAV
syncevolution --configure \
--template webdav \
syncURL=https://secure.powercraft.nl/davical/caldav.php/delta/cardav/ \
username=delta \
password=Gaod0lae \
target-config@carddav \
addressbook
# configure sync config for CardDAV
syncevolution --configure \
--template SyncEvolution_Client \
syncURL=local://@carddav \
username= \
password= \
carddav \
addressbook
# initial slow sync for CardDAV
syncevolution --sync slow carddav
# incremental sync for CardDAV
syncevolution carddav
# same for CalDAV
syncevolution --configure \
--template webdav \
syncURL=https://secure.powercraft.nl/davical/caldav.php/gamma/home/ \
username=gamma \
password=roch8Jey \
target-config@caldav \
calendar
syncevolution --configure \
--template SyncEvolution_Client \
syncURL=local://@caldav \
username= \
password= \
caldav \
calendar
syncevolution --sync slow caldav
syncevolution caldav
12:38 p.m.
On 29-07-11 12:24, Patrick Ohly wrote:
Can you point to specific aspects that you don't understand and
which
need to be explained better?
Anyway, here's the WebDAV example adapted to separate URL and
credentials for CalDAV and CardDAV. Instead of configuring "addressbook"
and "calendar", separate configs are used with one source in each.
syncURL is given explicitly.
Thank you! I could not figure out where to place the syncURL as it is
not mentioned in the documentation, but it seems critical to provide an
URL to the servers. Also the target-config@ is a bit fuzzie, but
examples really help a lot!
I created the configuration, but I am hitting an HTTPS problem:
http://paste.debian.net/124471/
I am using cacert certificates, the N900 browser works fine with them
but it seems neon libs are giving some issues. Any idea how to tell neon
to trust the cacert authority?
http://www.cacert.org/index.php?id=3
http://www.cacert.org/certs/root.crt
Thanks in advance,
Kind regards,
Jelle de Jong
12:47 p.m.
On Fr, 2011-07-29 at 12:38 +0200, Jelle de Jong wrote:
I created the configuration, but I am hitting an HTTPS problem:
http://paste.debian.net/124471/
I am using cacert certificates, the N900 browser works fine with them
but it seems neon libs are giving some issues. Any idea how to tell neon
to trust the cacert authority?
This came up on the list before, see Ove's emails.
The result was that it cannot be done with the current code. You'll have
to disable SSL checking.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
2:51 p.m.
Dear Patrick.
I was able to do an initial caldav sync! Yeah!, but the carddav fails
please see the pastebin: http://paste.debian.net/124487/
Am I doing something wrong?
Thanks in advance,
Kind regards,
Jelle de Jong
5:39 p.m.
On 29-07-11 14:51, Jelle de Jong wrote:
I was able to do an initial caldav sync! Yeah!, but the carddav
fails
please see the pastebin: http://paste.debian.net/124487/
Am I doing something wrong?
During more testing I figured out syncevolution is capable of deleting
the complete addressbook resources from the davical server when
something goes "wrong" with the syncs.
http://paste.debian.net/124505/
I guess the [INFO @carddav] @carddav/addressbook: deleting <> removes
the complete addressbook....
Kind regards,
Jelle de Jong
8:34 p.m.
On Fr, 2011-07-29 at 17:39 +0200, Jelle de Jong wrote:
On 29-07-11 14:51, Jelle de Jong wrote:
> I was able to do an initial caldav sync! Yeah!, but the carddav fails
> please see the pastebin: http://paste.debian.net/124487/
>
> Am I doing something wrong?
During more testing I figured out syncevolution is capable of deleting
the complete addressbook resources from the davical server when
something goes "wrong" with the syncs.
Well, you grant it read/write access, so yes, it certainly is capable to
wreck havoc. It shouldn't of course :-/
http://paste.debian.net/124505/
I guess the [INFO @carddav] @carddav/addressbook: deleting <> removes
the complete addressbook....
This could be a follow-up error from the previous ETag error.
Can you send me all your carddav logs, both for the sync and target
config, and for all sessions? I'd like to have a look to figure out how
it could have gone wrong like that.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
1:58 p.m.
On Fr, 2011-07-29 at 20:34 +0200, Patrick Ohly wrote:
On Fr, 2011-07-29 at 17:39 +0200, Jelle de Jong wrote:
> On 29-07-11 14:51, Jelle de Jong wrote:
> > I was able to do an initial caldav sync! Yeah!, but the carddav fails
> > please see the pastebin: http://paste.debian.net/124487/
> >
> > Am I doing something wrong?
>
> During more testing I figured out syncevolution is capable of deleting
> the complete addressbook resources from the davical server when
> something goes "wrong" with the syncs.
Well, you grant it read/write access, so yes, it certainly is capable to
wreck havoc. It shouldn't of course :-/
> http://paste.debian.net/124505/
>
> I guess the [INFO @carddav] @carddav/addressbook: deleting <> removes
> the complete addressbook....
This could be a follow-up error from the previous ETag error.
Can you send me all your carddav logs, both for the sync and target
config, and for all sessions? I'd like to have a look to figure out how
it could have gone wrong like that.
Jelle sent some logs, but Intel's mail system filtered them out before
delivering the email.
In the meantime I installed DAViCal 0.9.9.4, the current version from
mcmillan.net.nz. Both CalDAV and CardDAV worked fine in my tests.
Jelle, which version of DAViCal are you running?
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
2:14 p.m.
On 01-08-11 13:58, Patrick Ohly wrote:
In the meantime I installed DAViCal 0.9.9.4, the current version
from
mcmillan.net.nz. Both CalDAV and CardDAV worked fine in my tests.
Jelle, which version of DAViCal are you running?
0.9.9-0 from Ubuntu 10.04.3 LTS Server (sorry legacy system, will be
migrated to Debian GNU/Linux)
PS. the new logs are coming soon.
Kind regards,
Jelle de Jong
8:22 p.m.
On Fr, 2011-07-29 at 14:51 +0200, Jelle de Jong wrote:
Dear Patrick.
I was able to do an initial caldav sync! Yeah!, but the carddav fails
please see the pastebin: http://paste.debian.net/124487/
Am I doing something wrong?
No, your commands are fine.
[INFO @carddav] @carddav/addressbook: started
[INFO @carddav] @carddav/addressbook: adding <???>
[ERROR @carddav] @carddav/addressbook: could not retrieve ETag
[INFO @carddav] @carddav/addressbook: received 1/3
[INFO @carddav] @carddav/addressbook: adding "Jelle de Jong"
[ERROR @carddav] @carddav/addressbook: could not retrieve ETag
[INFO @carddav] @carddav/addressbook: received 2/3
[INFO @carddav] @carddav/addressbook: adding "Marchel S."
[ERROR @carddav] @carddav/addressbook: could not retrieve ETag
[INFO @carddav] @carddav/addressbook: received 3/3
[INFO] @default/addressbook: first time sync done unsuccessfully
[ERROR] @default/addressbook: fatal error (remote, status 500)
[...]
Synchronization failed, see
/home/user/.cache/syncevolution/target_+config(a)carddav-2011-07-29-14-39-a/syncevolution-log.html
for details.
I need this log file to say more. You can send it to me privately.
Basically the error about ETag says that the CardDAV server is not
behaving as it is expected to. At this point we have to assume that
SyncEvolution<->DAViCal CardDAV are not compatible.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
1:27 p.m.
On 07/29/2011 12:38 PM, Jelle de Jong wrote:
I am using cacert certificates, the N900 browser works fine with
them
but it seems neon libs are giving some issues. Any idea how to tell neon
to trust the cacert authority?
You should probably just add the "SSLVerifyServer=0" option when
configuring the DAV backends. SyncEvolution's WebDAV backend currently
has no way to tell neon where the CA certificates are (so neon will
probably just look in /etc/ssl/certs, which, of course, is unused and
empty on Maemo).
I also think you could have made your life a lot easier if you had just
used the syncevolution-frontend to configure your DAV sync...
2:44 p.m.
On 29-07-11 13:27, Ove Kåven wrote:
You should probably just add the "SSLVerifyServer=0" option
when
configuring the DAV backends. SyncEvolution's WebDAV backend currently
has no way to tell neon where the CA certificates are (so neon will
probably just look in /etc/ssl/certs, which, of course, is unused and
empty on Maemo).
Many thanks! That saved a lot of searching!
I also think you could have made your life a lot easier if you had
just
used the syncevolution-frontend to configure your DAV sync...
/me is checking out syncevolution-frontend.
Kind regards,
Jelle de Jong
3456
days inactive
3459
days old
syncevolution@synevolution.org
13 comments
3 participants
participants (3)
-
Jelle de Jong -
Ove Kåven -
Patrick Ohly