https://bugs.meego.com/show_bug.cgi?id=22937
--- Comment #8 from pohly <patrick.ohly(a)intel.com> 2011-09-16 08:33:58 UTC ---
(In reply to comment #7)
> Alain, does that match your problem? Originally you gave a
command line which
> set the password in a normal config, but the real problem was in the HTTP
> server setup, right?
Actually, the problem was both in the backend password (see example with
--export), and also with the sync password (needed by the HTTP server).
Your explanation seems to match the case for the backend password, but maybe a
similar (but different) key mismatch is taken place for the sync password as
well?
The sync password uses keys in the lookup which do not depend on the config
name. Can you try 1.1.99.7 and report back with the exact steps if it still
fails?
> I'm confident that this is fixed in the 1.2 release branch
Where can I download the 1.2 branch?
http://downloads.syncevolution.org/syncevolution/sources/ doesn't seem to have
it...
The 1.1.99.x versions are the 1.2 pre-releases; 1.2 itself isn't released yet.
I just packaged the latest revision:
http://syncevolution.org/blogs/pohly/2011/syncevolution-11997-released
P.S. Something unrelated to sync evolution: your bugtracker makes it
inconvenient to answer a comment, as the most recent comments are near the
bottom, but the reply text area is near the top... it would be more convenient
if the reply area was near the bottom as well.
That's standard Bugzilla fare as far as I know. Either I am used to it or it
isn't a problem the way I use it, which is with the "[reply]" link inside
the
comment summary line.
--------
Product: SyncEvolution
Component: SyncEvolution
MeeGo Release: unspecified
Severity: normal
Priority: Medium
Keywords:
Status: RESOLVED
Who: patrick.ohly(a)intel.com
Assigned To: patrick.ohly(a)intel.com
Target Build: 1.2
Flags:
Changed:
--------
https://bugs.meego.com/show_bug.cgi?id=22937
--
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.