On Sa, 2010-10-30 at 23:01 +0100, Gordon Dickens wrote:
> Hello,
> 
> I just upgraded to Ubuntu 10.10 and to SyncEvolution 1.1 and I am 
> running into a problem.
> 
> As an FYI, I have been running SyncEvolution successfully for the past 
> couple of years starting with Ubuntu 8.04 without any problems.
> 
> I don't know if it was the Ubuntu upgrade or the SyncEvolution upgrade 
> that is causing the problem. I have a syncevolution server configuration 
> named "funambol" which is located at: ~/.config/syncevolution/funambol.  
> When I attempt to sync using the command "syncevolution funambol"  then 
> I get the following error message:
> 
> [ERROR] No configuration for server "funambol" found.
> [ERROR] cannot proceed without configuration
> 
> Also, when I run the command "syncevolution --print-servers" then my 
> funambol server is not listed.

That's a regression. You are using an old-style config, which was meant
to be usable, but some change broke that.

> However, I do indeed have the same funambol server configured that I 
> have always had at:~/.config/syncevolution/funambol.
> 
> I subsequently noticed that a new empty directory had appeared in my 
> funambol server's directory named "peers" at 
> ~/.config/syncevolution/funambol/peers. I found that if I delete the 
> "peers" directory then syncevolution finds my funambol server and 
> "syncevolution funambol" runs perfectly except it subsequently creates 
> the "peers" directory again each time that I run "syncevolution 
> funambol" so it will not run successfully thereafter without deleting 
> the "peers" directory again and again.  Weird...

If it is found, the config is no longer recognized. This was necessary
to distinguish between old-style peer config and new-style context
config. The "peers" directory shouldn't be created. That's the root
cause of the problem.

Here's how you can recover from this while I prepare an update:
      * remove the peers directory once more
      * run "syncevolution --migrate funambol"

This will renamed ".config/syncevolution/funambol" to
".config/syncevolution/funambol.old" (which can be removed later) and
the new-style config in ".config/syncevolution/default/peers/funambol".
Then just use it as before.

-- 
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]
http://lists.syncevolution.org/listinfo/syncevolution

Reply via email to