Description of problem: There is a newer version of opensync (0.21) with some significant updates including "The most important new feature will be the NOT-UNIQUE-UID fix." (opensync changelog). It is also the earliest version that can be used in conjuction with Synce and a Windows Mobile 5 PDA. http://www.opensync.org/wiki/opensync-0.21-notes Version-Release number of selected component (if applicable): 0.20 is current in Extras How reproducible: n/a Steps to Reproduce: n/a Actual results: n/a Expected results: n/a Additional info: It would be great if this could get a version bump. There is a not about the API and DB change (relating to the above mentioned fix) - not sure how this is handled regarding users. Thanks
Thanks for reporting. I am already working on this but had no time these past days to get all the packages up do speed. Hopefully I will have the update out till end of the week.
Almost, there's a typo in the spec-file... Index: libopensync.spec =================================================================== RCS file: /cvs/extras/devel/libopensync/libopensync.spec,v retrieving revision 1.14 diff -u -r1.14 libopensync.spec --- libopensync.spec 25 Apr 2007 16:42:35 -0000 1.14 +++ libopensync.spec 26 Apr 2007 13:02:16 -0000 @@ -75,10 +75,11 @@ %{_libdir}/opensync/plugins/ EOF %else -cat > $RPM_BUILD_ROOT%{_sysconfdir}/ld.so.conf.d/opensync-64.conf << EOF +cat > $RPM_BUILD_ROOT%{_sysconfdir}/ld.so.conf.d/opensync.conf << EOF %{_libdir}/opensync/ %{_libdir}/opensync/formats/ %{_libdir}/opensync/plugins/ +EOF %endif %clean On a topic related to this update (that may be out of scope for this bugzilla) do note that in the release notes for 0.21 (http://www.opensync.org/wiki/opensync-0.21-notes) it's written that there's been a "DB change" so all users must remove the DB files from all their sync groups. How shall this be handled? Can users be expected to read a release note? The nice way I guess would be to patch the tool to detect the DB change and scrap the old DB itself...
Uhoh... c&p really is evil +). Thanks for reporting. Fixed and pushed. As to the db format. I read about it. I will see if it is possible (= not to hard) to make a patch to detect the old format. If so I will make an upgrade and submit it upstream otherwise I will just file an RFE upstream. Thanks so for the pointer.