<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN" "http://www.w3.org/TR/REC-html40/strict.dtd"><html><head><meta name="qrichtext" content="1" /><style type="text/css">p, li { white-space: pre-wrap; }</style></head><body style=" font-family:'Monospace'; font-size:10pt; font-weight:400; font-style:normal;"><p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p><p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>On Monday 13 April 2009 10:35:39 Adam Williamson wrote:<br>
> On Thu, 2009-04-09 at 23:15 +0200, Kevin Kofler wrote:<br>
> <br>
> > > Some contacts had got duplicated for some reason, but still, nice effort.<br>
> > <br>
> > Unfortunately, as I've been told, duplication of data is an inherent issue<br>
> > with libopensync 0.22, and the main reason why they're working on<br>
> > redesigning everything in 0.3x/0.40. Unfortunately, their redesign is<br>
> > breaking everything at the moment. :-(<br>
> <br>
> Yes, but it's more of a long-term issue (or if you get an incomplete<br>
> sync - the problem is a 'slow sync' duplicates data). I wouldn't expect<br>
> it as a matter of course on a single-shot test sync. As I said, though,<br>
> it could actually have been duplicated prior to the sync, I didn't think<br>
> to check. I'll do some more extensive testing with various devices in a<br>
> bit.<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>- In normal use, it will at some point fall into slow sync, sooner or later <br>
and create duplicates¹. I don't think any user would want that.<br>
- opensync 0.2x cannot detect² the SAME/SIMILAR cases reliably.<br>
- Thus only because of these two issues, (plus hundred two smaller ones) <br>
opensync 0.2x is broken, by design, inside the core - regardless of plugins.<br>
- It's useless to ship completely broken (not low Quality, broken) software.<br>
- Fedora 11 will ship them anyway.<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>Only thing unclear to me is why?<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p><p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>Tuju<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p><p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>¹ will be solved with capabilities/merger which is still not used by any trunk plugin.<br>
http://www.opensync.org/wiki/trunk/features/mergerCapabilities<br>
http://opensync.org/wiki/trunk/features/mergerFormatConversion<br>
² http://www.opensync.org/ticket/883<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>> --<br>
> Adam Williamson<br>
> Fedora QA Community Monkey<br>
> IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org<br>
> http://www.happyassassin.net<br>
-- <br>
Varo hattupäisiä autoilijoita.</p></body></html>