Hi!
If i want to sync with horde3, always only a slow-sync is possible.
This causes double entries.
Maybe an update to the latest version 1.0.99.7 would solve this.

I doubt that this depends on the version of SyncEvolution.

But you can try that yourself. Please add
  deb http://downloads.syncevolution.org/apt unstable main
to your apt sources and install "syncevolution-evolution". That'll give
you 1.0.99.7.

Regarding the problem itself, search the syncevolution-log.html about
"slow sync" and you'll find the reason why it always uses that. I
suspect that the server asks for it, in which case you'll have to look
into the server's logs and ask the Horde developers.

That Horde duplicates items on slow syncs is also a server problem.

I doubt that this depends on the version of SyncEvolution.

But you can try that yourself. Please add
  deb http://downloads.syncevolution.org/apt unstable main
to your apt sources and install "syncevolution-evolution". That'll give
you 1.0.99.7.

Regarding the problem itself, search the syncevolution-log.html about
"slow sync" and you'll find the reason why it always uses that. I
suspect that the server asks for it, in which case you'll have to look
into the server's logs and ask the Horde developers.

That Horde duplicates items on slow syncs is also a server problem.

This is a good suggestion, but note that you will probably have to
manually deinstall all of the debian syncevolution packages (at least
syncevolution and syncevolution-common) because they don't declare
conflicts with syncevolution-evolution.

About upgrading, the main reason the packages in Debian have not been
upgraded is that we are in release freeze for squeeze, and this makes
getting new upstream versions into the archive rather difficult.

d

This is a good suggestion, but note that you will probably have to
manually deinstall all of the debian syncevolution packages (at least
syncevolution and syncevolution-common) because they don't declare
conflicts with syncevolution-evolution.

About upgrading, the main reason the packages in Debian have not been
upgraded is that we are in release freeze for squeeze, and this makes
getting new upstream versions into the archive rather difficult.

d

The "syncevolution-evolution" package declares a conflict, so this
worked for me.
(which I hadn't intend to prepare in favor of releasing 1.1) or 1.1?

The "syncevolution-evolution" package declares a conflict, so this
worked for me.
(which I hadn't intend to prepare in favor of releasing 1.1) or 1.1?

Probably a bug fix release; I think the diff with 1.1 is now too large
for anyone in Debian to sensibly analyze.  Another option is just to add
the patch to the debian package if you don't want to make a bug fix
release.

To justify an upload at this point, we would need to argue that this bug
(or some other)

    makes the package in question unusable or mostly so, or causes data
    loss, or introduces a security hole allowing access to the accounts
    of users who use the package.

or, that the package violated some important debian policy.

It's a pain, but otherwise we'd never release.

David

Probably a bug fix release; I think the diff with 1.1 is now too large
for anyone in Debian to sensibly analyze.  Another option is just to add
the patch to the debian package if you don't want to make a bug fix
release.

To justify an upload at this point, we would need to argue that this bug
(or some other)

    makes the package in question unusable or mostly so, or causes data
    loss, or introduces a security hole allowing access to the accounts
    of users who use the package.

or, that the package violated some important debian policy.

It's a pain, but otherwise we'd never release.

David

Then also the diff between 1.0 beta 2 and the 1.0.x release series is
too large.

I don't have a full list of critical bugs in 1.0 beta 2, but I suspect
that there are too many to make back-porting all of them feasible.

I'm sure there are examples for that.

Then also the diff between 1.0 beta 2 and the 1.0.x release series is
too large.

I don't have a full list of critical bugs in 1.0 beta 2, but I suspect
that there are too many to make back-porting all of them feasible.

I'm sure there are examples for that.

Hi Thomas;

Is this bug still present in the latest version of syncevolution in
unstable (1.1+ds1-5) ?

d

The Problem disappeared with syncevolution 1.0+ds1~beta2a-2
and libsynthesis0 4.0.0+git20101024-1. But I think, libsynthesis
was the solution.
I hope, this was it.

Where did you get this version of libsynthesis? I don't see it in the synthesis or
moblin git repositories.

David

I have just packaged the git version.
I am doing a fresh Squeeze installation this moment.
I will report then, if there are any problems
with the Squeeze packages.

Thomas

Am Sonntag, den 12.12.2010, 09:33 -0400 schrieb David Bremner:

Sorry, I forgot:
I checked out from
http://www.synthesis.ch/indefero/index.php/p/libsynthesis/

Thomas

Which branch did you use?

Lukas has pushed several changes to his "luz" branch which are not yet
used in the libsynthesis bundled with SyncEvolution. I decided against
switching to the very latest version because that version introduced a
backwards-incompatible change of on-disk files. Once you upgrade, you
cannot go back. I wanted to combine that change with another such change
in SyncEvolution itself, probably in 1.2 or 1.3.

If you can pin the solution to a specific change in libsynthesis, then I
would back-port it to the version of libsynthesis in SyncEvolution
1.1.x. I looked through the changes, but saw nothing relevant.

Hi!
I have tested the default syncevolution shipped by Squeeze.
Til now no more problems. I think, you can mark the bug as
solved.

Thomas

Am Sonntag, den 12.12.2010, 15:58 +0100 schrieb Patrick Ohly:

According to the submitter, this bug is no longer present in squeeze.

Thanks to Thomas for the report, and to Thomas and Patrick for following
up on this.

David

Hi again!
This bug is still there with the latest syncevolution package and horde4.
I wonder, that other funambol clients on other devices don't have this
problem.

should). Look at your syncevolution-log.html and search for "anchor", it
should tell you when it falls back to a slow sync because of a mismatch.

Looks like this Horde bug to me:
http://bugs.horde.org/ticket/10008

Thomas, can you reassign this bug to the Debian Horde maintainers with
information about your installed Horde version?

Dear submitter,

as the package syncevolution has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/935239

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmaster@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

This bug has likely been fixed in the last decade, please check
syncevolution version 2.0.0-3 from Debian testing/bookworm or later.
If you still have the same issue, please report it upstream and let us
know the URL of the new upstream issue.

https://syncevolution.org/support