https://bugs.meego.com/show_bug.cgi?id=21251

jingke <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEEDINFO                    |ASSIGNED

--- Comment #22 from jingke <[email protected]> 2011-07-20 17:12:49 UTC ---
Hi Cheng,
Let's change the command. 

Make clean .config/ and .cache/syncevolution/ ; Create new config files:
$ syncevolution -c -l Google_Calendar -y username=<name> -y password=<pass>
target-config@google-calendar
$ syncevolution -c -l SyncEvolution_Client -y username= -y password= -y
syncURL=local://@google-calendar google-calendar calendar
[For proxy] if you need it, config in target-config@google-calendar

Then, do slow sync firstly:
syncevolution --sync slow google-calendar calendar

My current status is to meet an error for "Cannot parse ISC file":
[INFO] @default/addressbook: inactive
[INFO] @default/memo: inactive
[INFO] @default/todo: inactive
[INFO] @default/calendar: starting first time sync, two-way  ---> why
"two-way"??
[ERROR] error code from SyncEvolution fatal error (local, status 10500):
@default/calendar: opening calendar: Cannot open calendar: Cannot parse ISC
file '/home/meego/.local/share/evolution/calendar/system/calendar.ics'
[INFO] @default/calendar: first time sync done unsuccessfully
[ERROR] fatal error (local, status 10500)

Seems backend cannot parse BLANK calendar.ics?

--------
Product: OS Middleware
Component: SyncEvolution
MeeGo Release: 1.2
Severity: normal
Priority: Undecided
Keywords: 
Status: ASSIGNED
Who: [email protected]
Assigned To: [email protected]
Target Build: ---
Flags: 
Changed: Status
--------

https://bugs.meego.com/show_bug.cgi?id=21251


-- 
Configure bugmail: https://bugs.meego.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching someone on the CC list of the bug.
_______________________________________________
Syncevolution-issues mailing list
[email protected]
http://lists.syncevolution.org/listinfo/syncevolution-issues

Reply via email to