[SyncEvolution] SyncEvolution 1.1.99.2 ready for testing
by Patrick Ohly
Hello!
I have uploaded binaries and source of 1.1.99.2, a pre-release of the
upcoming 1.2, to syncevolution.org. .debs are available in the
"unstable" repo, .rpms are in the usual location and the source is in
the new "experimental" sub-directory of the "source" download dir.
This version is not complete enough to replace 1.1.1 in distros, but it
should be stable and ready for testing by adventurous users. I'm using
it myself now.
Compared to previous updates, this one has several more disruptive
changes, which is why I would like to get feedback from real users
before releasing it.
The configuration has to be rewritten before it can be used for syncing.
The reasons are a) a format change of the libsynthesis binfiles which
would cause slow syncs after a downgrade and b) renaming configuration
options (evolutionsource/user/password -> database +
databaseUser/Password, type ->
backend/databaseFormat/syncFormat/forceSyncFormat).
Because I don't want user to unintentionally run this version and then
face issues when downgrading (see below), the configuration explicitly
has to be migrated to the new format. The command line prints
instructions as part of reporting the problem. Basically run "--migrate
@default". The UI shows a new 22005 error code. The final 1.2 release
will automatically migrate configs as needed.
Downgrading is still possible. If you plan to do that, make a copy of
~/.config/syncevolution and restore that later. You'll run into slow
syncs; resolve these with an explicit slow sync or refresh syncs. If you
didn't plan to downgrade, then find the "default.old" directory and the
"peers/*.old" directories inside, remove the more recent directories
without that suffix and remove the *.old suffix from the older ones.
Also set "consumerReady=1" in the peer config to have it show up in the
sync UI again.
Alternatively it is possible to use an older SyncEvolution command line
with the renamed configurations. In the sync UI they won't show up
because "consumerReady" was unset as part of migrating.
With that out of the way, here's why updating is worthwhile:
* improved syncevo-http-server (but the script can also be used
with 1.1.1)
* improved command line: "syncevolution --configure
addressbook/database=My_Address_Book
calendar/database=My_Calendar mobical addressbook calendar"
* no more confusion about "type" property
This was discussed in more detail on the list before, see archive.
Known issues:
https://bugs.meego.com/show_bug.cgi?id=13301 - printing available
databases broke during "type" removal
--
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.
11 years, 3 months
[SyncEvolution] Changes in calendar description not syncing
by Irihapeti
I changed the description field on an event on my Nokia E63 by deleting the
latter half of the description.
After syncing, I noticed that the change hadn't propagated to the server. I'm
running Darwin Calender Server under Ubuntu 10.04 and Evolution has this as its
main calendar. I don't know if this is relevant, but thought I'd mention it.
Looking at the logfile, it seems that the changed entry was detected, but
nothing was done about it.
I think that this has happened before, though previously I would have put it
down to intending to change something and then forgetting to do it
(happens at my age :) ).
This doesn't seem to be consistent. I deleted some words from the middle of a
description (on the phone) and it propagated successfully.
Changes done on the server seem to propagate successfully.
11 years, 3 months
[SyncEvolution] [ERROR] sync: syncevolution.xml not found
by Tino Keitel
Hi,
I just upgraded to 1.1.1 compiled from source on my Debian Lenny
system, and now I get this error:
2011-02-08_19:22:47.70121 [ERROR] sync: syncevolution.xml not found
I see that there is a file share/syncevolution/xml/syncevolution.xml in
the installation path.
Regards,
Tino
11 years, 3 months
[SyncEvolution] Building from git fails
by Ove Kaaven
How come it's not possible to build SyncEvolution 1.1.1 from git?
...
cp ../test/syncevo-phone-config.py syncevo-phone-config
make[4]: *** No rule to make target
`templates/clients/phone/nokia/S60/N85.ini', needed by `all-am'. Stop.
make[4]: Leaving directory `/home/ovek/sync/syncevolution.head/src'
make[3]: *** [install-recursive] Error 1
make[3]: Leaving directory `/home/ovek/sync/syncevolution.head/src'
make[2]: *** [install] Error 2
...
Investigating, I found that src/Makefile.am in git is different from
src/Makefile.am in the tarballs, having a different list of backends and
templates. Why would there be a non-working makefile in git, but a
working one in the tarballs?
11 years, 3 months
[SyncEvolution] Trying to follow the http-server-howto
by Carl Erberg
Hi all,
After having a look at funambol I decided not to use it (no debian
packages, only all in one blob, that opens million ports).
So now my next approach to getting my E71 to sync with several
desktops/notebooks is the syncevolution http server. I tried to follow
the description at
http://syncevolution.org/development/http-server-howto
Unfortunately it is not very precise so maybe someone can help me with
the following points:
I successfully worked through the server setup until step 7, adjusted
the commands a little as I installed in /opt. I also added an SSL
tunnel to the server via socat. I can do a connect to the http server
and it works (it answers).
Now at step 8 I was not sure which client is meant "the client". I
used one Desktop with a plain syncevolution install together with
sync-ui for a first try, is that correct?
Now the syncevolution client dies if I give it an https:// URL with a
self-signed certificate. Has anyone some hints on how to deal with
this?
Without being able to connect via SSL I was not able to continue.
Step 9 lets me wonder: Which output should I search? The client? The server?
Thanks for your help!
Regards
Carl
11 years, 3 months
[SyncEvolution] remove debian/ dir from source
by toabctl
Hi,
i want to ask if it's possible to remove the debian-directory from the git
source.
Reasons:
- the debian/control files is outdated. packages like libedataserver-dev
does not exist anymore in debian squeeze
- david bremner works on a much better packed version of syncevolution (see
git://git.debian.org/collab-maint/syncevolution.git )
- i try to set up a daily build on launchpad for syncevolution but that does
not work (or i don't know how) with a already existing debian-dir
Any reasons why the debian-dir should exist?
Cheers,
Tom
11 years, 3 months
[SyncEvolution] SyncEvolution 1.2: downgrade not possible, introduce config versioning
by Patrick Ohly
Hello!
Since the beginning it was always possible to switch back and forth
between SyncEvolution releases. When backwards-incompatible on-disk
changes were necessary, the user had to explicitly asked for them with
the --migrate option (needed only once so far, to get the config layout
change).
For 1.2, this will no longer be possible, because libsynthesis changes
its on-disk format ("binfile") in a backwards-incompatible way (can read
old format, but old version cannot read new one).
On that occasion I also want to make several other changes which will
prevent going back:
1. split "type" into independent options, to solve
http://bugs.meego.com/show_bug.cgi?id=1023
2. rename "evolutionsource" to "database", "evolutionuser/password"
to "backendusername/password", with the old names accepted as
alias, but not being written to disk
Here's how I intend to handle the transition:
* Pre-releases of 1.2 will refuse to do anything with a config
unless its complete context gets migrated with "--migrate
@<context>"; this will also migrate all configs inside that
context. The error message will explain this. Migration happens
by renaming ~/.config/syncevolution/default to
~/.config/syncevolution/default.old and then recreating
~/.config/syncevolution/default with the new content. So it will
be possible to go back, but only with slow or refresh syncs.
* The final 1.2 will do the migration automatically, because most
users (in particular those relying on a GUI) will have problems
with the pre-release error messages.
* I'll introduce .version files in ~/.config/syncevolution,
~/.config/syncevolution/* and ~/.config/syncevolution/*/peers/*.
The content are two numbers, one specifying the oldest format
definition that the directory is compatible with, the other
specifying the current definition. Each SyncEvolution binary
needs to check that it's current definition falls into that
range, otherwise it is too old and cannot use the config. Using
two numbers has the advantage that backwards-compatible
extensions are possible.
The problem will be that SyncEvolution 1.1.x does not yet check that
version. After migrating the configs, it'll fail to find the "type"
property. I hope not too many users will fall into that trap.
Any comments? Implementation will commence soonish.
--
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.
11 years, 3 months
[SyncEvolution] sync-ui: Add new service doesn't work
by Frederik Elwert
Hi!
On the German ubuntuusers.de forum, someone just pointed out that the
“add new service” button in sync-ui doesn’t work. Means, clicking it
just has no effect. Thus, it is not possible to configure services that
are not in the list of consumer ready templates (eGroupWare in this
case).
Is this already known, or did something break in the last releases?
Regards,
Frederik
11 years, 3 months
