Your message dated Sat, 20 Nov 2010 18:10:03 +0100 with message-id <20101120171003.GP5063@radis.liafa.jussieu.fr> and subject line Re: Bug#599472: Permission to upload opensync-0.22 to testing-proposed-updates has caused the Debian Bug report #599472, regarding Permission to upload opensync-0.22 to testing-proposed-updates to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 599472: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=599472 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: Permission to upload opensync-0.22 to testing-proposed-updates
- From: Michael Banck <mbanck@debian.org>
- Date: Thu, 7 Oct 2010 20:58:07 +0200
- Message-id: <20101007185807.GB29051@nighthawk.chemicalconnection.dyndns.org>
Package: release.debian.org I have finally found time earlier this week to revert opensync packaging to the stable 0.2x branch, and I would like to propose this as a way to ship opensync to our users. This would make users of Blackberry (via barry) and Windows Mobile (via synce-sync-engine) devices able to sync. I have talked to a couple of users, and they said those worked more or less fine before opensync got all messed up in unstable and finally removed from testing (but I do not own such a device myself). As the 0.39 packages got uploaded (accidently, thanks to sbuild) to unstable some time ago, an upload to testing-proposed-updates would be the way to go. I have prepared such an upload (0.22-4squeeze1) with a couple of additional fixes from upstream's subversion repository: 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. The interdiff to 0.22-4 is attached; I do not think an interdiff to the current package in unstable would make sense. This is the diffstat: formats/vformats-xml/vformat.c | 5 +++++ opensync-0.22/debian/changelog | 12 ++++++++++++ opensync-0.22/wrapper/Makefile.am | 2 +- wrapper/opensync.i | 2 +- 4 files changed, 19 insertions(+), 2 deletions(-) Uploading this would make it possible to potentially transition the barry and synce-sync-engine packages (which I believe were removed due to opensync), as well as the currently still at 0.22 kdepim plugin and the multisync0.90 package in unstable. Other still at 0.22 plugins in unstable could be transitioned as well, but they are less important. Further testing-proposed-updates uploads of the file and evolution2 plugins should be done as well, as they are quite central. The syncml plugin should get dropped, as it does not work with libsyncml-0.5.4 (and reverting that does not make sense to me). For syncml, syncevolution is probably the better alternative anyway. I have build and made available some of those packages built against opensync_0.22-4squeeze1 (barry, synce-sync-engine, libopensync-plugin- {file,evolution2,kdepim,google-calendar} at deb http://people.debian.org/~mbanck/opensync-squeeze/ ./ Unfortunately, my internet connection is extremely limited at the moment as I am on vacation. I will check this bug report via my mobile, and will be able to discuss (with some latency) in #debian-release, however. Thanks for considering, Michaeldiff -u opensync-0.22/wrapper/Makefile.am opensync-0.22/wrapper/Makefile.am --- opensync-0.22/wrapper/Makefile.am +++ opensync-0.22/wrapper/Makefile.am @@ -24,3 +24,3 @@ nodist__opensync_la_SOURCES = opensync_wrap.c -_opensync_la_LDFLAGS = @PACKAGE_LIBS@ @XML_LIBS@ $(PYTHON_LDFLAGS) -module -avoid-version +_opensync_la_LDFLAGS = @PACKAGE_LIBS@ @XML_LIBS@ -module -avoid-version _opensync_la_LIBADD = $(top_builddir)/opensync/libopensync.la diff -u opensync-0.22/debian/changelog opensync-0.22/debian/changelog --- opensync-0.22/debian/changelog +++ opensync-0.22/debian/changelog @@ -1,3 +1,15 @@ +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. + + -- Michael Banck <mbanck@debian.org> Mon, 04 Oct 2010 19:35:19 +0200 + opensync (0.22-4) unstable; urgency=low * debian/control (Maintainer): Really remove Robert Collins now. only in patch2: unchanged: --- opensync-0.22.orig/wrapper/opensync.i +++ opensync-0.22/wrapper/opensync.i @@ -82,7 +82,7 @@ %extend OSyncChange { OSyncChange(PyObject *obj=NULL) { OSyncChange *change = NULL; - if (obj) + if ((obj) && (obj != Py_None)) change = (OSyncChange *)PyCObject_AsVoidPtr(obj); else change = osync_change_new(); only in patch2: unchanged: --- opensync-0.22.orig/formats/vformats-xml/vformat.c +++ opensync-0.22/formats/vformats-xml/vformat.c @@ -571,6 +571,11 @@ osync_trace(TRACE_INTERNAL, "invalid character found in parameter spec: \"%i\" String so far: %s", lp[0], str->str); g_string_assign (str, ""); _skip_until (&lp, ":;"); + if (*lp == '\r') { + osync_trace(TRACE_INTERNAL, "string ended unexpectedly with \\r, skipping it"); + break; + } + } }
--- End Message ---
--- Begin Message ---
- To: Michael Banck <mbanck@debian.org>, 599472-done@bugs.debian.org
- Cc: "Adam D. Barratt" <adam@adam-barratt.org.uk>
- Subject: Re: Bug#599472: Permission to upload opensync-0.22 to testing-proposed-updates
- From: Julien Cristau <jcristau@debian.org>
- Date: Sat, 20 Nov 2010 18:10:03 +0100
- Message-id: <20101120171003.GP5063@radis.liafa.jussieu.fr>
- In-reply-to: <[🔎] 20101119185118.GC3615@nighthawk.chemicalconnection.dyndns.org>
- References: <20101007185807.GB29051@nighthawk.chemicalconnection.dyndns.org> <20101025184913.GP3167@radis.liafa.jussieu.fr> <[🔎] 1289165200.27850.7433.camel@hathi.jungle.funky-badger.org> <[🔎] 20101112171303.GD3736@nighthawk.chemicalconnection.dyndns.org> <[🔎] 20101114202733.GL5063@radis.liafa.jussieu.fr> <[🔎] 20101119185118.GC3615@nighthawk.chemicalconnection.dyndns.org>
On Fri, Nov 19, 2010 at 19:51:18 +0100, Michael Banck wrote: > Hi, > > On Sun, Nov 14, 2010 at 09:27:33PM +0100, Julien Cristau wrote: > > On Fri, Nov 12, 2010 at 18:13:03 +0100, Michael Banck wrote: > > > > > Would it be fine to close the FTBFS/unresolved dependency RC bugs on the > > > various plugins in unstable now? > > > Which bugs is this about, and are they resolved? I must admit I haven't > > kept track. > > For example #569382 - I removed the squeeze tag, but not sure this will > help. > Adam forced multisync0.90 and libopensync-plugin-kdepim so they should migrate tonight. Closing the bug, please reopen if there are still actions needed from -release. Cheers, JulienAttachment: signature.asc
Description: Digital signature
--- End Message ---