On Mon, Oct 6, 2014 at 11:56 PM, Patrick Ohly <patrick.ohly(a)intel.com> wrote:
> > Nevertheless, can you show the output of:
> >
> > syncevolution --print-config -q google
> > syncevolution --print-config -q target-config@google
>
> [I'm leaving off the blank options to save space and redacting a few
> id numbers; let me know if you need more]
>
> syncURL = local://@google
> username = goa:account_...
When I asked about "username=goa:..." in your "google" sync
config", I
meant the "google" config. You said that only
google/peers/target-config/config.ini has username=goa:... set, but then
why does it show up here?
Is it really unset in default/peers/google/config.ini?
Sorry, I was just looking in google/ and didn't think to look in default/:
$ cd ~/.config/syncevolution
$ find . -name config.ini -print | xargs grep goa
./default/peers/google/config.ini:username = goa:account_...
./google/peers/target-config/config.ini:username = goa:account_...
Anyway, removing it in the "google" config should allow you
to run syncs
again: syncevolution --configure username= google
Yes, authentication is successful now, but I'm still having some
problems with the sync. Perhaps we'll have to go into details off-list
about the contents of the events, but here is a selection of some of
the maybe relevant lines that were printed on a non-debug run:
[INFO @google] @google/calendar: starting first time sync from server
(peer is server)
[INFO @google] @google/calendar: deleting 1/1
[INFO] @default/calendar: starting first time sync, two-way (peer is client)
[INFO] @default/calendar: started
[INFO] @default/calendar: sent 99/656
[INFO @google] @google/calendar: started
[INFO @google] adding "....." [one of 98 such lines, interspersed with
two instances of:]
[ERROR @google] error code from SyncEvolution object not found
(remote, status 404): PUT: bad HTTP status: <status 1.1, code 404,
class 4, Not Found>
... and ending with:
[INFO @google] @google/calendar: received 98/755
[INFO] @default/calendar: first time sync done unsuccessfully
[INFO] @default/calendar: server database not found, check URI 'calendar'
[INFO] creating complete data backup after sync (enabled with dumpData
and needed for printChanges)
Synchronization failed, see
/home/twilson/.cache/syncevolution/google-2014-10-07-09-06/syncevolution-log.html
for details.
Changes applied during synchronization:
+---------------|-----------------------|-----------------------|-CON-+
| | @default | @google | FLI |
| Source | NEW | MOD | DEL | ERR | NEW | MOD | DEL | ERR | CTS |
+---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
| calendar | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
| refresh-from-local, 0 KB sent by client, 0 KB received |
| item(s) in database backup: 755 before sync, 755 after it |
| object not found (remote, status 404) |
+---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
| start Tue Oct 7 09:06:27 2014, duration 1:09min |
| object not found (remote, status 404) |
+---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
First ERROR encountered: error code from SyncEvolution object not
found (remote, status 404): PUT: bad HTTP status: <status 1.1, code
404, class 4, Not Found>
Data modified @default during synchronization:
*** @default/calendar ***
no changes
> I'm sending the output in a separate private email.
That confirms my theory and matches what I was able to reproduce myself
earlier.
Glad I was able to help.
--Todd