Debian Bug report logs - #580867
opensync: Unfit for release

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Michael Banck <mbanck@debian.org>

To: submit@bugs.debian.org

Subject: opensync: Unfit for release

Date: Sun, 9 May 2010 15:05:19 +0200

Package: opensync
Version: 0.39-4
Severity: serious

At this point, opensync is not ready for release.

Message #10 received at 580867@bugs.debian.org (full text, mbox, reply):

From: "Adam D. Barratt" <adam@adam-barratt.org.uk>

To: Michael Banck <mbanck@debian.org>, 580867@bugs.debian.org

Subject: Re: Bug#580867: opensync: Unfit for release

Date: Mon, 28 Jun 2010 20:52:09 +0100

Hi,

On Sun, 2010-05-09 at 15:05 +0200, Michael Banck wrote:
> At this point, opensync is not ready for release.

Is this still the case?

opensync is involved in the transition to using python2.6 by default
(via python-opensync, which depends on "python << 2.6" in testing) so we
will either need to be able to migrate the new opensync packages, or
remove them from testing; given this bug and the number of FTBFS bugs
against packages in the dependency chain, the latter looks more likely.

For reference, this would involve the removal of:

opensync
libopensync-plugin-file
libopensync-plugin-google-calendar
libopensync-plugin-gpe
libopensync-plugin-irmc
libopensync-plugin-kdepim
libopensync-plugin-opie
libopensync-plugin-palm
libopensync-plugin-python
libopensync-plugin-sunbird

barry
multisync0.90
synce-sync-engine
synce-kpm

Regards,

Adam

Message #15 received at 580867@bugs.debian.org (full text, mbox, reply):

From: Michael Banck <mbanck@debian.org>

To: "Adam D. Barratt" <adam@adam-barratt.org.uk>

Cc: 580867@bugs.debian.org

Subject: Re: Bug#580867: opensync: Unfit for release

Date: Wed, 30 Jun 2010 15:12:38 +0200

Hi,

On Mon, Jun 28, 2010 at 08:52:09PM +0100, Adam D. Barratt wrote:
> Hi,
> 
> On Sun, 2010-05-09 at 15:05 +0200, Michael Banck wrote:
> > At this point, opensync is not ready for release.
> 
> Is this still the case?
 
Yes, at least 0.3x isn't, and upstream is not moving.

> opensync is involved in the transition to using python2.6 by default
> (via python-opensync, which depends on "python << 2.6" in testing) so we
> will either need to be able to migrate the new opensync packages, or
> remove them from testing; given this bug and the number of FTBFS bugs
> against packages in the dependency chain, the latter looks more likely.

Hrm, it seems opensync and the rest got removed from testing already?  I
was going to propose to drop all non-python plugins and fix
opensync-0.22 in testing to work with python2.6 and thus keeping barry
and synce-sync-engine on board, as people seem to be successfully using
those.  But I am not sure this would be the best, either.


Michael

Message #20 received at 580867@bugs.debian.org (full text, mbox, reply):

From: "Adam D. Barratt" <adam@adam-barratt.org.uk>

To: "Michael Banck" <mbanck@debian.org>

Cc: 580867@bugs.debian.org

Subject: Re: Bug#580867: opensync: Unfit for release

Date: Wed, 30 Jun 2010 14:34:21 +0100

On Wed, June 30, 2010 14:12, Michael Banck wrote:
> On Mon, Jun 28, 2010 at 08:52:09PM +0100, Adam D. Barratt wrote:
>> On Sun, 2010-05-09 at 15:05 +0200, Michael Banck wrote:
>> > At this point, opensync is not ready for release.
[...]
>> opensync is involved in the transition to using python2.6 by default
>> (via python-opensync, which depends on "python << 2.6" in testing) so we
>> will either need to be able to migrate the new opensync packages, or
>> remove them from testing; given this bug and the number of FTBFS bugs
>> against packages in the dependency chain, the latter looks more likely.
>
> Hrm, it seems opensync and the rest got removed from testing already?

Yeah.  We had an opportunity to get the python transition (mostly)
finished somewhat earlier than we expected, so we took it; unfortunately
opensync was a casualty of that.

> I was going to propose to drop all non-python plugins and fix
> opensync-0.22 in testing to work with python2.6 and thus keeping barry
> and synce-sync-engine on board, as people seem to be successfully using
> those.  But I am not sure this would be the best, either.

I wouldn't be averse to helping them back in to testing minus the opensync
plugins, if they're otherwise useful.

Regards,

Adam

Message #25 received at 580867@bugs.debian.org (full text, mbox, reply):

From: Fernando Toledo <ftoledo@docksud.com.ar>

To: 580867@bugs.debian.org

Subject: opensync: Unfit for release

Date: Wed, 28 Jul 2010 16:26:51 -0300

[Message part 1 (text/plain, inline)]

please. fix it ASAP!
its broken all my sync with my phone via Synce.
=(
-- 
Dock Sud BBS
http://bbs.docksud.com.ar
telnet://bbs.docksud.com.ar

[signature.asc (application/pgp-signature, inline)]

Message #32 received at 580867-close@bugs.debian.org (full text, mbox, reply):

From: Michael Banck <mbanck@debian.org>

To: 580867-close@bugs.debian.org

Subject: Bug#580867: fixed in opensync 0.22-4squeeze1

Date: Tue, 02 Nov 2010 10:32:04 +0000

Source: opensync
Source-Version: 0.22-4squeeze1

We believe that the bug you reported is fixed in the latest version of
opensync, which is due to be installed in the Debian FTP archive:

libopensync0-dbg_0.22-4squeeze1_i386.deb
  to main/o/opensync/libopensync0-dbg_0.22-4squeeze1_i386.deb
libopensync0-dev_0.22-4squeeze1_i386.deb
  to main/o/opensync/libopensync0-dev_0.22-4squeeze1_i386.deb
libopensync0_0.22-4squeeze1_i386.deb
  to main/o/opensync/libopensync0_0.22-4squeeze1_i386.deb
opensync_0.22-4squeeze1.diff.gz
  to main/o/opensync/opensync_0.22-4squeeze1.diff.gz
opensync_0.22-4squeeze1.dsc
  to main/o/opensync/opensync_0.22-4squeeze1.dsc
opensyncutils_0.22-4squeeze1_i386.deb
  to main/o/opensync/opensyncutils_0.22-4squeeze1_i386.deb
python-opensync_0.22-4squeeze1_i386.deb
  to main/o/opensync/python-opensync_0.22-4squeeze1_i386.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 580867@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Michael Banck <mbanck@debian.org> (supplier of updated opensync package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160

Format: 1.8
Date: Mon, 04 Oct 2010 19:35:19 +0200
Source: opensync
Binary: libopensync0 opensyncutils libopensync0-dev libopensync0-dbg python-opensync
Architecture: source i386
Version: 0.22-4squeeze1
Distribution: testing
Urgency: low
Maintainer: Michael Banck <mbanck@debian.org>
Changed-By: Michael Banck <mbanck@debian.org>
Description: 
 libopensync0 - Synchronisation framework for email/pdas/and more
 libopensync0-dbg - Debug symbols for libopensync0
 libopensync0-dev - Headers and static libraries for libopensync
 opensyncutils - Command line utilities for libopensync
 python-opensync - Python bindings to the opensync synchronisation engine
Closes: 470290 562159 580867
Changes: 
 opensync (0.22-4squeeze1) testing-proposed-updates; urgency=low
 .
   * Upload to testing-proposed-updates (Closes: #580867).
   * wrapper/opensync.i: Applied patch by Mark Ellis, porting opensync.i to
     swig-1.3.40 (Closes: #562159).
   * wrapper/Makefile.am: Do not pass $(PYTHON_LDFLAGS) when linking the python
     extensions (Closes: #470290).
   * formats/vformats-xml/vformat.c: Applied upstream revision 3575 fixing an
     infinite loop in vformat.
Checksums-Sha1: 
 054ca36ab03b4ac1b9ca1abca5434efbccf2828d 1211 opensync_0.22-4squeeze1.dsc
 fc7affbfd409d5192cabca897222c374d3d3e27f 71977 opensync_0.22-4squeeze1.diff.gz
 076ca315bab0090c9eaa7ed9deecff8f8399c0d6 243314 libopensync0_0.22-4squeeze1_i386.deb
 5d6455a25312b2a90a9f00384bdf5030141d102e 27346 opensyncutils_0.22-4squeeze1_i386.deb
 9f6777e6940bf2f888e5493490e9cbbd33cdf604 449696 libopensync0-dev_0.22-4squeeze1_i386.deb
 fcd758700c59c3640b3b7b7032fc30c660695d86 522450 libopensync0-dbg_0.22-4squeeze1_i386.deb
 146e8d4f7745c387eccd34287610f24b65c1de75 46052 python-opensync_0.22-4squeeze1_i386.deb
Checksums-Sha256: 
 9ec3bad8ce3c42e3aa0b4cd9490a780c8ef57c6e57565ebe2568cbe06230fcb6 1211 opensync_0.22-4squeeze1.dsc
 8828ea184911fca96b9ac08496b26feedb569eed8b6fc1f4f02d6af6bbb08bc8 71977 opensync_0.22-4squeeze1.diff.gz
 c5821540e73bdb92996ed6afbe9c461543c8b3f3ea845949c21a90ab866aa801 243314 libopensync0_0.22-4squeeze1_i386.deb
 aedcac65b9014336806089b0436e13e33b5d7c4b265514c20b753b9f882ee6f6 27346 opensyncutils_0.22-4squeeze1_i386.deb
 409979c7c3f1103127f7fec0f66216b5ab935a307bc585061ed986e48629abb8 449696 libopensync0-dev_0.22-4squeeze1_i386.deb
 b21a7315e70d4cbbf1b4c795e1262b0f77ba95725d82ddb332532270455aac59 522450 libopensync0-dbg_0.22-4squeeze1_i386.deb
 02f7b82e415ed82ae7673b5ecc78695bc52d96ac03bb0c494c31a80358528b54 46052 python-opensync_0.22-4squeeze1_i386.deb
Files: 
 be1808f755243fd129bb7ac046541c52 1211 libs optional opensync_0.22-4squeeze1.dsc
 e61edbc30f2c2be2547c2dc4a44ff8f4 71977 libs optional opensync_0.22-4squeeze1.diff.gz
 ba861b77cd7985bfef5d72bfcb674917 243314 libs optional libopensync0_0.22-4squeeze1_i386.deb
 f33cb946c5fe9248df72f883e45f053c 27346 libs optional opensyncutils_0.22-4squeeze1_i386.deb
 14d082b5881868b36a29c622587ed73a 449696 libdevel optional libopensync0-dev_0.22-4squeeze1_i386.deb
 b22b994c645c6c1fb6a65c4afa3ca52b 522450 libs extra libopensync0-dbg_0.22-4squeeze1_i386.deb
 de3a05afc4f7d2d7973013f95c1a7634 46052 python optional python-opensync_0.22-4squeeze1_i386.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iD8DBQFMzwTFmHaJYZ7RAb8RA4UAAKCoQF/LGnDBAEt+nRJ7FYpslAL0rgCfRaYp
d7k4zHU99N0HxYhn8qotuFg=
=xvB6
-----END PGP SIGNATURE-----

Send a report that this bug log contains spam.