[FFe request] Please sync opensync_0.22-2 from Debian unstable (main)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
libopensync-plugin-evolution2 (Ubuntu) |
Fix Released
|
Undecided
|
Steve Langasek | ||
libopensync-plugin-google-calendar (Ubuntu) |
Fix Released
|
Undecided
|
Steve Langasek | ||
libopensync-plugin-kdepim (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
libopensync-plugin-sunbird (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
opensync (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Rationale for dropping Ubuntu changes:
The python build process got fixed in Debian and now supports multiple python versions, so the current Ubuntu hardcoding is no longer necessary. Further, .a/.la files for the python extensions are no longer shipped. No other Ubuntu changes were present.
debian/changelog:
opensync (0.22-2) unstable; urgency=low
* debian/
* debian/control (Standards-
* debian/control: Replaced ${Source:Version} with ${binary:Version}.
-- Michael Banck <email address hidden> Sun, 02 Mar 2008 12:39:41 +0100
opensync (0.22-1) unstable; urgency=low
* New upstream release (Closes: #404856, #442827)
* debian/control (Uploaders): Added myself.
* debian/rules (debian/
* opensync/
* debian/rules (debian/
* debian/rules (debian/
* debian/copyright: Added download location and clarified copyright and
licensing (Closes: #439876, #455827).
* debian/pyversions: Set 2.4 as minimum version (Closes: #445394).
* debian/rules: Ported generic python handling from experimental branch.
* debian/
* acinclude.m4: Add python2.5 to list of python interpreters.
* Reran aclocal and autoconf.
* debian/control (libopensync0-dbg): Set Priority to extra.
* debian/control (python-opensync): Set Section to python.
* debian/rules (binary-arch): Tighten shlibs to dh_makeshlibs -V.
-- Michael Banck <email address hidden> Fri, 29 Feb 2008 00:45:57 +0100
Rationale for new upstream version:
opensync-0.19 has been unmaintained upstream for years now and should not get shipped in a LTS release. opensync-0.22 has been released last autumn and is the currently recommended version by upstream for distributions to include, while the opensync-0.3x is still considered experimental and is discouraged from packaging by upstream. Opensync-0.22 works fine with kitchensync (universe) and reasonably well with multisync0.90 and msynctool (both universe as well). Even though no support for Windows Mobile or Blackberry devices is available in hardy, shipping opensync-0.22 (and the accompayning plugins in universe) will give hardy (KDE) users a reasonable syncing experience, compared to the last couple of Ubuntu releases.
Conducted testing:
The opensync_0.22-2 package has been made available as hardy packages (together with the plugins and multisync-gui) as PPA at
deb http://
for several weeks. User testing has been unconclusive (some success reports, one failure report). I have verified that kitchensync still works after upgrading to opensync-0.22. Partial upgrades have not been extensively tested I believe.
If this FFE is getting accepted, FFEs for the plugins in universe should get issued accordingly.
Diffstat output (136 files changed, 10434 insertions(+), 34491 deletions(-)) is being attached.
Related branches
Changed in opensync: | |
status: | New → Confirmed |
Changed in libopensync-plugin-evolution2: | |
assignee: | nobody → vorlon |
status: | New → In Progress |
Changed in libopensync-plugin-google-calendar: | |
assignee: | nobody → vorlon |
I'm inclined to ok this in spite of the lateness of the change, but for the plugins we also need sign-off from motu-release; subscribing them now.
Do you have a list of the affected source packages for the plugins?