On Mon, Nov 26, 2012 at 14:17:27 +0100, Patrick Ohly wrote:
> On Mon, 2012-11-26 at 13:47 +0100, [email protected]
> wrote:
> > I'm looking for the reason why syncevolution 1.3 requires libsynthesis
> > 3.4.0.16.8. I'm not shure what to look for. Could you point me to
> > specific commits in syncevolution? The dependency change in
> > configure.ac came in with a commit that also added a lot of stuff to
> > the NEWS file.
> 
> In that commit I was just cleaning up for the release. The actual
> changes were there before.
> 
> Have a look at the commit messages in libsynthesis where I bump the
> version. That together with the libsynthesis patches gives an idea why
> the new version is needed for SyncEvolution:
> 
> $ git log 
> libsynthesis_3.4.0.16+syncevolution-1-2-99-1..libsynthesis_3.4.0.16+syncevolution-1-3-1
> commit 99159e0991664f8c8319e634598ea6c9bd73fcc2
> Author: Patrick Ohly <[email protected]>
> Date:   Mon Sep 10 09:15:20 2012 +0200
> 
>     autotools: bumped minor version
>     
>     Bumped minor version so that SyncEvolution can ensure that the version
>     it is compiled against really fixes the VJOURNAL<->plain text
>     conversion problem.                     ^^^^^^^^^^^^^^^^^^^^^
>     ^^^^^^^^^^^^^^^^^^^
> 
> A fix required for 1.3, which introduces the VJOURNAL<->plain feature
> (part of WebDAV: support tasks and memos (BMC #24893)).
> 
> commit 0a4a64f976a0f1812c9011efe7d832e381889e97
> Author: Patrick Ohly <[email protected]>
> Date:   Thu Aug 16 18:59:22 2012 +0200
> 
>     engine: allow text->VJOURNAL conversion
>     
>     SyncEvolution uses the Synthesis engine to convert a plain text memo
>     to iCalendar 2.0 in the local storage. ...
> 

Hi,

I noticed that. I was merely interested in specific _syncevolution_
commits that require this.  I could not find any relevant syncevolution
commits in the timeframe of the above commit.

Background: I'm preparing a new upload for Debian that is based on
1.2.99.1 and fixes for important bugs.  I decided to not package 1.3.x
for Debian Wheezy, as the freeze policy is too strict meanwhile.

Regards,
Tino
_______________________________________________
SyncEvolution mailing list
[email protected]
http://lists.syncevolution.org/listinfo/syncevolution

Reply via email to