Bug#599247: syncevolution: Syncing with horde3 - always only slow-sync possible
On Wed, 06 Oct 2010 08:28:47 +0200 Thomas Maass wrote: > If i want to sync with horde3, always only a slow-sync is possible. > This causes double entries. 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 -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#599247: syncevolution: Syncing with horde3 - always only slow-sync possible
On Sun, 2012-08-12 at 01:02 +0200, Thomas Maass wrote: Package: syncevolution Version: 1.2.99.1-1 Followup-For: Bug #599247 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. Perhaps they don't check the server's anchor. libsynthesis does (as it 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? -- 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. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#599247: syncevolution: Syncing with horde3 - always only slow-sync possible
Package: syncevolution Version: 1.2.99.1-1 Followup-For: Bug #599247 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. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages syncevolution depends on: ii libc6 2.13-33 ii libcppunit-1.12-1 1.12.1-4 ii libgcc1 1:4.7.1-2 ii libgdbussyncevo0 1.2.99.1-1 ii libglib2.0-0 2.32.3-1 ii libpcre3 1:8.30-5 ii libpcrecpp0 1:8.30-5 ii libstdc++64.7.1-2 ii libsyncevolution0 1.2.99.1-1 ii syncevolution-common 1.2.99.1-1 ii syncevolution-libs1.2.99.1-1 Versions of packages syncevolution recommends: ii bluez 4.99-2 ii evolution-data-server 3.4.3-1 syncevolution suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#599247: syncevolution: Syncing with horde3 - always only slow-sync possible
Package: syncevolution Version: 1.0+ds1~beta2a-1+b1 Severity: normal 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. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages syncevolution depends on: ii libbluetooth3 4.66-1Library to use the BlueZ Linux Blu ii libc6 2.11.2-6 Embedded GNU C Library: Shared lib ii libdbus-1-31.2.24-3 simple interprocess messaging syst ii libdbus-glib-1-2 0.88-2simple interprocess messaging syst ii libebook1.2-9 2.30.2.1-1Client library for evolution addre ii libecal1.2-7 2.30.2.1-1Client library for evolution calen ii libedataserver1.2-13 2.30.2.1-1Utility library for evolution data ii libgcc11:4.4.4-8 GCC support library ii libgconf2-42.28.1-4 GNOME configuration database syste ii libglib2.0-0 2.24.2-1 The GLib library of C routines ii libgnome-keyring0 2.30.1-1 GNOME keyring services library ii libical0 0.44-3iCalendar library implementation i ii libopenobex1 1.5-2 OBEX protocol library ii libsoup2.4-1 2.30.2-1 an HTTP library implementation in ii libstdc++6 4.4.4-8 The GNU Standard C++ Library v3 ii libsynthesis0 3.4.0.5+ds1-1 library for SyncML-DS (SyncML Data ii libxml22.7.7.dfsg-4 GNOME XML library Versions of packages syncevolution recommends: ii evolution 2.30.2-1 groupware suite with mail client a syncevolution suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#599247: syncevolution: Syncing with horde3 - always only slow-sync possible
On Wed, 2010-10-06 at 07:28 +0100, Thomas Maass wrote: 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. -- 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. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#599247: syncevolution: Syncing with horde3 - always only slow-sync possible
On Wed, 06 Oct 2010 09:21:30 +0200, Patrick Ohly patrick.o...@intel.com wrote: 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. 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 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#599247: syncevolution: Syncing with horde3 - always only slow-sync possible
On Wed, 2010-10-06 at 11:41 +0100, David Bremner wrote: On Wed, 06 Oct 2010 09:21:30 +0200, Patrick Ohly patrick.o...@intel.com wrote: 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. 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. The syncevolution-evolution package declares a conflict, so this worked for me. 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. What would be easier to get included: another 1.0.x bug fix update (which I hadn't intend to prepare in favor of releasing 1.1) or 1.1? -- 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. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#599247: syncevolution: Syncing with horde3 - always only slow-sync possible
On Wed, 06 Oct 2010 13:23:06 +0200, Patrick Ohly patrick.o...@intel.com wrote: What would be easier to get included: another 1.0.x bug fix update (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 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#599247: syncevolution: Syncing with horde3 - always only slow-sync possible
On Wed, 2010-10-06 at 12:44 +0100, David Bremner wrote: On Wed, 06 Oct 2010 13:23:06 +0200, Patrick Ohly patrick.o...@intel.com wrote: What would be easier to get included: another 1.0.x bug fix update (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. Then also the diff between 1.0 beta 2 and the 1.0.x release series is too large. Another option is just to add the patch to the debian package if you don't want to make a bug fix release. 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. 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. I'm sure there are examples for that. -- 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. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#582376: Bug#599247: syncevolution: Syncing with horde3 - always only slow-sync possible
On Wed, 06 Oct 2010 14:06:41 +0200, Patrick Ohly patrick.o...@intel.com wrote: I moved this discussion to the please upgrade syncevolution bug. Then also the diff between 1.0 beta 2 and the 1.0.x release series is too large. Ah, true, I should have thought of that. Then I suppose it probably doesn't matter much from a Debian point of view. 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. Hmm. I guess I'm not using syncevolution enough myself to hit them. None of these bugs have been reported as Debian bugs. If you could point me to a couple that you consider particularly bad, I could try and duplicate them with the Debian builds. There was some shared library issues (on Ubuntu?), but I never was able to duplicate them. All the best, David -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#582376: Bug#599247: syncevolution: Syncing with horde3 - always only slow-sync possible
On Wed, 2010-10-06 at 14:29 +0100, David Bremner wrote: On Wed, 06 Oct 2010 14:06:41 +0200, Patrick Ohly patrick.o...@intel.com wrote: I moved this discussion to the please upgrade syncevolution bug. Eh, how? ;-) The reply was still for 582376, the one about Horde. I'll reply likewise, but I agree, this belongs elsewhere. 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. Hmm. I guess I'm not using syncevolution enough myself to hit them. None of these bugs have been reported as Debian bugs. If you could point me to a couple that you consider particularly bad, I could try and duplicate them with the Debian builds. From 1.1, candidates for 1.0.2 (if there ever will be one): * bug fix in sync-ui: wrong direction of one-way data transfers with devices (BMC #7091) * Nokia phones: avoid data loss in two-way sync due to X-EVOLUTION-UI-SLOT (BMC #2566) * Nokia phones: alarm times in UTC, sending PHOTO (BMC #1657, #5860) * fixes for time zone handling in libsynthesis 1.0.1: * sync-ui: prevent overwriting device configs by accident (BMC #3566,1194) 1.0: * Mobical.net (and other, similar services): fix vCalendar 1.0 alarm specifications before importing them (MB #10458) * workaround for Evolution 2.30: timezone cannot be retrieved because it doesn't exist is triggered incorrectly when importing non-standard timezone definitions because libecal change an error code (MB #9820) * GTK GUI: improved setup of devices, automatic sync switch, some fixes for crashes and other tweaks * Nokia 7210c: send time as UTC instead of relying on time zone information (MB #9907). * Nokia E55: convert alarm times (BMC #1657). * GTK GUI: styling fix (BMC #1372), updated toolbar for MeeGo 1.0 (BMC #1970), avoid duplicating configs when selecting a config created by syncevo-phone-config or the command line (BMC #1266), scroll bars for emergency window (BMC #1296), * HTTP server: fix for potential crash when second session was requested while an older one was still running, initial sync was done without libical time zone information and thus may have mismatched times (BMC #2435) * Fix for potential out-of-bounds memory access (BMC #1007). * Funambol, Memotoo (and probably others): preserve meeting series when receiving update for detached recurrence (BMC #1916) * Better handling of certain third-party time zone definitions (BMC #1332). Better logging to track down such problems. -- 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. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
