Re: [SyncEvolution] SyncEvolution 1.4.99.4
On Mon, 2014-10-27 at 15:32 +0100, Tino Mettler wrote: Hi Patrick, I just want to let you know that 1.4.99.4 is now in Debian unstable. I hope it will therefore become part of the next Debian stable release. That's good, thanks for your help. I noticed this week in an unrelated article about the systemd GR that there is a feature freeze deadline coming up for Debian early next week. Do you think it would be possible to get SyncEvolution 1.5 into that if I release it this weekend? The changes compared to 1.4.99.4 are minor, but some of the changes may be relevant for users. It would be cleaner to have a regular release in Debian, too. The NEWS entry for 1.4.99.4 - 1.5 is: * vcard: fix caching of PBAP contacts (FDO #84710) After changing PBAP to send raw items, caching them led to unnecessary disk writes and bogus contacts changed reports. That's because the merge script relied on the exact order of properties, which was only the same when doing the redundant decode/encode on the PBAP side. Instead of reverting back to sending re-encoded items, better enhance the contact merge script such that it detects contacts as unchanged when just the order of entries in the property arrays is different. This relies on an enhanced libsynthesis with the new RELAXEDCOMPARE() and modified MERGEFIELDS(). * sync: ignore unnecessary username property A local sync or Bluetooth sync do not need the 'username' property. When it is set despite that, issue a warning. Previously, the value was checked even when not needed, which caused such syncs to fail when set to something other than a plain username. * D-Bus server: fix unreliable shutdown handling Occassionally, syncevo-dbus-server locked up after receiving a CTRL-C. This primarily affected nightly testing, in particular (?) on Ubuntu Lucid. * scripting: prevent premature loop timeouts The more complex avoid data loss during merging scripting ran for longer than 5s limit under extreme conditions (full logging, busy system, running under valgrind), which resulted in aborting the script and a 10500 local internal error sync failure. * signon: fix providersignon.so (TC-1667) The shared providersignon.so ended up being compiled with gsso as prefix for the username. There also was a problem with invalid reference counting. * PBAP: support SYNCEVOLUTION_PBAP_CHUNK_TRANSFER_TIME = 0 When set to 0 or less, the chunk size is not getting adapted at all while still using transfers in chunks. -- 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. ___ SyncEvolution mailing list SyncEvolution@syncevolution.org https://lists.syncevolution.org/mailman/listinfo/syncevolution
Re: [SyncEvolution] SyncEvolution 1.4.99.4
On Fri, Oct 31, 2014 at 14:04:26 +0100, Patrick Ohly wrote: On Mon, 2014-10-27 at 15:32 +0100, Tino Mettler wrote: Hi Patrick, I just want to let you know that 1.4.99.4 is now in Debian unstable. I hope it will therefore become part of the next Debian stable release. That's good, thanks for your help. I noticed this week in an unrelated article about the systemd GR that there is a feature freeze deadline coming up for Debian early next week. Do you think it would be possible to get SyncEvolution 1.5 into that if I release it this weekend? The changes compared to 1.4.99.4 are minor, but some of the changes may be relevant for users. Just plain no, because the freeze affects Debian testing. Every package must be in testing at the time of the freeze. However, new packages are uploaded to Debian unstable, and unstable-to-testing migration was set to 10 days. Therefore, the deadline for new packages that should become a part of Jessie was last Sunday. That's why I submitted the first 1.4.99.2 package last Saturday, and another package with a small fix last Sunday. :-) So let's hope that no important bugs are found that would prevent the migration to testing for the 1.4.99.2 package. Otherwise, Jessie will be shipped with 1.4. Updates will only be allowed if they fix important bug, and only these bugs. As usual, New upstream versions won't be possible, fixes have to be backported. If you point me to critical bugs that affects users of the Debian package including a fix (or a git commit that contains the fix), I could try to provide updated packages. It would be cleaner to have a regular release in Debian, too. I know. It just didn't work out. Regards, Tino ___ SyncEvolution mailing list SyncEvolution@syncevolution.org https://lists.syncevolution.org/mailman/listinfo/syncevolution
Re: [SyncEvolution] SyncEvolution 1.4.99.4
On Fri, 2014-10-31 at 14:35 +0100, Tino Mettler wrote: On Fri, Oct 31, 2014 at 14:04:26 +0100, Patrick Ohly wrote: On Mon, 2014-10-27 at 15:32 +0100, Tino Mettler wrote: Hi Patrick, I just want to let you know that 1.4.99.4 is now in Debian unstable. I hope it will therefore become part of the next Debian stable release. That's good, thanks for your help. I noticed this week in an unrelated article about the systemd GR that there is a feature freeze deadline coming up for Debian early next week. Do you think it would be possible to get SyncEvolution 1.5 into that if I release it this weekend? The changes compared to 1.4.99.4 are minor, but some of the changes may be relevant for users. Just plain no, because the freeze affects Debian testing. Every package must be in testing at the time of the freeze. However, new packages are uploaded to Debian unstable, and unstable-to-testing migration was set to 10 days. Therefore, the deadline for new packages that should become a part of Jessie was last Sunday. Right, I hadn't thought of that. Updates will only be allowed if they fix important bug, and only these bugs. As usual, New upstream versions won't be possible, fixes have to be backported. If you point me to critical bugs that affects users of the Debian package including a fix (or a git commit that contains the fix), I could try to provide updated packages. Relevant for users of Debian binaries is: commit 50148ab580f8912fa3cf5cd55c1e68050d43cf45 Author: Patrick Ohly patrick.o...@intel.com Date: Thu Sep 25 06:57:50 2014 + scripting: prevent premature loop timeouts The more complex avoid data loss during merging scripting ran for longer than 5s limit under extreme conditions (full logging, busy system, running under valgrind), which resulted in aborting the script and a 10500 local internal error sync failure. The endless loop prevention should only be necessary to detect programming mistakes, so better disable it entirely. It would be cleaner to have a regular release in Debian, too. I know. It just didn't work out. Never mind. 1.4.99.4 is close enough. I don't mind getting prodded a bit regarding releases. I'm not actively following downstream release cycles, so telling me about them occasionally would help to get upstream releases out in time. -- 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. ___ SyncEvolution mailing list SyncEvolution@syncevolution.org https://lists.syncevolution.org/mailman/listinfo/syncevolution
Re: [SyncEvolution] SyncEvolution 1.4.99.4
On Fri, Oct 31, 2014 at 15:40:39 +0100, Patrick Ohly wrote: [...] Relevant for users of Debian binaries is: commit 50148ab580f8912fa3cf5cd55c1e68050d43cf45 Author: Patrick Ohly patrick.o...@intel.com Date: Thu Sep 25 06:57:50 2014 + scripting: prevent premature loop timeouts The more complex avoid data loss during merging scripting ran for longer than 5s limit under extreme conditions (full logging, busy system, running under valgrind), which resulted in aborting the script and a 10500 local internal error sync failure. The endless loop prevention should only be necessary to detect programming mistakes, so better disable it entirely. Hi Patrick, thanks for that. [...] I don't mind getting prodded a bit regarding releases. I'm not actively following downstream release cycles, so telling me about them occasionally would help to get upstream releases out in time. OK, I'll keep that in mind. However, saw a bit late that the deadline for updates in unstable is freeze date minus 10 days. During the last freezes, packages in unstable at the point of the freeze were allowed to migrate to testing after the freeze. And of cause, big thanks to David Bremner for uploading the packages I submitted as fast as possible. Regards, Tino ___ SyncEvolution mailing list SyncEvolution@syncevolution.org https://lists.syncevolution.org/mailman/listinfo/syncevolution
[Syncevolution-issues] [Bug 84710] Contacts are being treated as updated and written to database, but their content did not change
https://bugs.freedesktop.org/show_bug.cgi?id=84710 Patrick Ohly patrick.o...@gmx.de changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #8 from Patrick Ohly patrick.o...@gmx.de --- A better solution based on an enhanced comparison (RELAXEDCOMPARE()) was implemented in 1.5, without reverting the performance enhancement. -- You are receiving this mail because: You are on the CC list for the bug. ___ Syncevolution-issues mailing list Syncevolution-issues@syncevolution.org https://lists.syncevolution.org/mailman/listinfo/syncevolution-issues
[Syncevolution-issues] [Bug 72133] iCloud support + sync report
https://bugs.freedesktop.org/show_bug.cgi?id=72133 Patrick Ohly patrick.o...@gmx.de changed: What|Removed |Added Summary|iCloud support |iCloud support + sync ||report --- Comment #3 from Patrick Ohly patrick.o...@gmx.de --- Contacts are said to work with 1.5. Calendars need support for downloading changes via sync reports (https://tools.ietf.org/html/rfc6578) because the current approach is not supported by the iCloud server (Apple issue 17001498 CalDAV REPORT drops calendar data). -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. ___ Syncevolution-issues mailing list Syncevolution-issues@syncevolution.org https://lists.syncevolution.org/mailman/listinfo/syncevolution-issues
[Syncevolution-issues] [Bug 52682] WebDAV: use sync extension
https://bugs.freedesktop.org/show_bug.cgi?id=52682 Patrick Ohly patrick.o...@gmx.de changed: What|Removed |Added Component|SyncEvolution |CalDAV/CardDAV -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. ___ Syncevolution-issues mailing list Syncevolution-issues@syncevolution.org https://lists.syncevolution.org/mailman/listinfo/syncevolution-issues
[Syncevolution-issues] [Bug 52684] WebDAV: handle concurrent changes
https://bugs.freedesktop.org/show_bug.cgi?id=52684 Patrick Ohly patrick.o...@gmx.de changed: What|Removed |Added Component|SyncEvolution |CalDAV/CardDAV -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. ___ Syncevolution-issues mailing list Syncevolution-issues@syncevolution.org https://lists.syncevolution.org/mailman/listinfo/syncevolution-issues
[Syncevolution-issues] [Bug 52685] CalDAV: better support for meeting invitations
https://bugs.freedesktop.org/show_bug.cgi?id=52685 Patrick Ohly patrick.o...@gmx.de changed: What|Removed |Added Component|SyncEvolution |CalDAV/CardDAV -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. ___ Syncevolution-issues mailing list Syncevolution-issues@syncevolution.org https://lists.syncevolution.org/mailman/listinfo/syncevolution-issues
[Syncevolution-issues] [Bug 52682] WebDAV: use sync extension
https://bugs.freedesktop.org/show_bug.cgi?id=52682 Patrick Ohly patrick.o...@gmx.de changed: What|Removed |Added Blocks||72133 -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. ___ Syncevolution-issues mailing list Syncevolution-issues@syncevolution.org https://lists.syncevolution.org/mailman/listinfo/syncevolution-issues
[Syncevolution-issues] [Bug 72133] iCloud support + sync report
https://bugs.freedesktop.org/show_bug.cgi?id=72133 Patrick Ohly patrick.o...@gmx.de changed: What|Removed |Added Depends on||52682 -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. ___ Syncevolution-issues mailing list Syncevolution-issues@syncevolution.org https://lists.syncevolution.org/mailman/listinfo/syncevolution-issues
