On Wed, 2010-10-06 at 14:29 +0100, David Bremner wrote:
> On Wed, 06 Oct 2010 14:06:41 +0200, Patrick Ohly <patrick.o...@intel.com> 
> wrote:
> 
> I moved this discussion to the "please upgrade syncevolution" bug.

Eh, how? ;-) The reply was still for 582376, the one about Horde. I'll
reply likewise, but I agree, this belongs elsewhere.

> > I don't have a full list of critical bugs in 1.0 beta 2, but I suspect
> > that there are too many to make back-porting all of them feasible.
> > 
> 
> Hmm. I guess I'm not using syncevolution enough myself to hit them. None
> of these bugs have been reported as Debian bugs. If you could point me
> to a couple that you consider particularly bad, I could try and
> duplicate them with the Debian builds.

>From 1.1, candidates for 1.0.2 (if there ever will be one):

* bug fix in sync-ui: wrong direction of one-way data transfers with devices 
(BMC #7091)
* Nokia phones: avoid data loss in two-way sync due to X-EVOLUTION-UI-SLOT (BMC 
#2566)
* Nokia phones: alarm times in UTC, sending PHOTO (BMC #1657, #5860)
* fixes for time zone handling in libsynthesis

1.0.1:
* sync-ui: prevent overwriting device configs by accident (BMC #3566,1194)

1.0:
* Mobical.net (and other, similar services): fix vCalendar 1.0 alarm
  specifications before importing them (MB #10458)
* workaround for Evolution 2.30: "timezone cannot be retrieved because it
  doesn't exist" is triggered incorrectly when importing non-standard
  timezone definitions because libecal change an error code (MB #9820)
* GTK GUI: improved setup of devices, automatic sync switch,
  some fixes for crashes and other tweaks
* Nokia 7210c: send time as UTC instead of relying on time zone
  information (MB #9907).
* Nokia E55: convert alarm times (BMC #1657).
* GTK GUI: styling fix (BMC #1372), updated toolbar for MeeGo 1.0 (BMC #1970),
  avoid duplicating configs when selecting a config created by 
syncevo-phone-config 
  or the command line (BMC #1266), scroll bars for emergency window (BMC #1296),
* HTTP server: fix for potential crash when second session was requested while 
an
  older one was still running, initial sync was done without libical time zone
  information and thus may have mismatched times (BMC #2435)
* Fix for potential out-of-bounds memory access (BMC #1007).
* Funambol, Memotoo (and probably others): preserve meeting series when
  receiving update for detached recurrence (BMC #1916)
* Better handling of certain third-party time zone definitions (BMC #1332).
  Better logging to track down such problems.

-- 
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.





-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to