Mobical seems to have switched its time handling. Several floating
time stamps are converted to UTC, using the time zone set on the
server.
This breaks all-day detection and EXDATEs. This used to work in the
past (http://bugzilla.moblin.org/web/bug_report_3009.html). Instead of
trying to find further workarounds, let's give up and declare these
aspects as unsupported: README updated, test data simplified.
We are running all tests without preventSlowSync (manual configuration
change), because the server turns all sync modes into a slow sync if
the server's database is emtpy. That's okay, but confuses the client
and tests fails when the slow sync is prevented.
Mobical has a known server issue that it initiates a
slow sync when one client syncs with it in one-way-from-client
mode from the second time.
Because Mobical has no schedule on this, we skip this
test for Mobical interoperability test.
Originally, testing against Mobical led to the conclusion that
'PHOTO' is compressed by server but still be correct
and checking of the PHOTO property was disabled in synccompare.
Later it was found that there were decoding (Mobical
not standard compliant) and encoding (libsynthesis not
compliant when folding was off) issues (MB#6668), fixed in
libsynthesis now.
Automated testing no longer falls over a modified PHOTO property.
Either the compression is not triggered for this photo, or
something has changed. In any case, this patch enables comparison
of the PHOTO property again, because that is necessary to cover
these encoding issues.
cases patches (Bug#3009)
1. Add new suppressions to synccompare for vcard21, ical20, itodo20 and
text.
2. Add README.mobical for mobical interoperability test results
3. Add 3 test patches for vcard21, ical20, itodo20
