[SyncEvolution] SyncEvolution 1.1.99.2 ready for testing

[Peter Robinson]

On Wed, Feb 9, 2011 at 10:28 PM, Peter Robinson <pbrobinson at gmail.com> wrote:
> Hi Patrick,
>
> On Tue, Feb 8, 2011 at 7:55 AM, Patrick Ohly <patrick.ohly at gmx.de> wrote:
>> 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
>
> Two issues. First one is easy, is there a source file? :-)
>
> Second one is a query about the libgdbus fork. Its causing me a lot of
> problems in Fedora. There are now a number of packages using the
> upstream version including gupnp (which is now used by parts of gnome
> 3) which is causing problems in Fedora and basically makes
> syncevolution unusable in a lot of cases. What are the plans on
> getting your patches upstream?

Oh and does it have the option to use both gtk2 and gtk3 as evolution
and e-d-s for gnome3 will require it if you use any of the e-d-s/evo
gui components.

Peter