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.