Public bug reported:

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/libopensync0-dev.install: Do not install python stuff.
  * debian/control (Standards-Version): Bump to 3.7.3.
  * debian/control: Replaced ${Source:Version} with ${binary:Version}.

 -- Michael Banck <[EMAIL PROTECTED]>  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/build-stamp): Added --enable-tracing.
  * opensync/opensync_user.c: Change user config dir to ~/.opensync-0.22.
  * debian/rules (debian/configure-stamp): New target.
  * debian/rules (debian/build-stamp): Move configuring to it.
  * 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/python-opensync: Wildcard python directory.
  * 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 PROTECTED]>  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://ppa.launchpad.net/debian-opensync/ubuntu hardy main

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.

** Affects: opensync (Ubuntu)
     Importance: Undecided
         Status: New

-- 
[FFe request] Please sync opensync_0.22-2 from Debian unstable (main)
https://bugs.launchpad.net/bugs/214083
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to