On Tue, 2014-10-07 at 09:28 -0700, Todd Wilson wrote: > On Mon, Oct 6, 2014 at 11:56 PM, Patrick Ohly <[email protected]> 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_...
Do you have an idea how it got there? I don't think previous SyncEvolution versions worked with such a config. > > 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, That would be good. A target-config@google log file at loglevel=4 would be useful. -- 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. _______________________________________________ SyncEvolution mailing list [email protected] https://lists.syncevolution.org/mailman/listinfo/syncevolution
