please merge 0.22 from debian unstable

Bug #81831 reported by mangar
50
Affects Status Importance Assigned to Milestone
opensync (Debian)
Fix Released
Unknown
opensync (Ubuntu)
Fix Released
Wishlist
Unassigned
Nominated for Hardy by Serge

Bug Description

there's a new version of opensync - 0.22
Source files:
http://www.opensync.org/wiki/download

debs:
http://www.in.fh-merseburg.de/~jahn/

Tags: upgrade
Revision history for this message
triceo (lukas-petrovicky) wrote :

And now there's one more (0.21) with 0.22 to come.

Revision history for this message
Stefano Costa (steko) wrote :

The developers aren't even willing to give support for the old version in Ubuntu repositories, as I found last week when trying to get opensync to work on my feisty laptop. They provide an external repository but only for edgy.

Revision history for this message
Niels Abspoel (aboe) wrote :

I confirm this, would love to see opensync updated the new version has lots of bugfixes...
having this package up to date with it depencies correct gives better bluetooth support to gnome and kde

Changed in opensync:
status: Unconfirmed → Confirmed
Revision history for this message
Wouter Stomp (wouterstomp-deactivatedaccount) wrote :

In the mean time version 0.30 is available. Please update it to this version.

Changed in opensync:
importance: Undecided → Wishlist
Revision history for this message
Wouter Stomp (wouterstomp-deactivatedaccount) wrote :

0.31 has been released

Revision history for this message
Wouter Stomp (wouterstomp-deactivatedaccount) wrote :

0.22 is the latest stable release that should be packaged. 0.31 is the development release for the upcoming 0.40 version

Revision history for this message
Nicolò Chieffo (yelo3) wrote :

Yes the package should be updated! 0.19 does not support my nokia 6630

Revision history for this message
Saivann Carignan (oxmosys) wrote :

Like Wouter Stomp said, the latest version that can be packaged is the 0.22. The plugins doesn't exist anyway in 0.31 version so they aren't compatible.

Revision history for this message
Saivann Carignan (oxmosys) wrote :

Added the bug to Debian.

Changed in opensync:
status: Unknown → New
Revision history for this message
Ali Sabil (asabil) wrote :

Could this please be updated for gutsy ?

Revision history for this message
Saivann Carignan (oxmosys) wrote :

Opensync 0.22 isn't packaged in Debian anyway, so I think it's too late for Gutsy but maybe it'll be possible for Gutsy backports. I'm new to packaging but I'll look if I can do something around that package.

description: updated
Changed in opensync:
assignee: nobody → debian-opensync
Revision history for this message
Turgon (hormigon-pretensado-ubuntu) wrote : Re: new version of opensync was released (0.22)

 Hello. After some searching and testing, I think that the version of Opensync available for Gutsy is too old to support my Nokia N70, while a bit newer version is reported to work ( http://geektalk.andreat.de/2006/11/how-to-syncronize-nokia-n70-palm.html ).
 I don't know if this issue is important enough to justify a backport; if not, it would be nice if the package could be updated for Ubuntu 8.04, if all you people who kindly contribute with your work don't find another more pressing task.

Revision history for this message
Michael Banck (mbanck) wrote : Re: [Bug 81831] Re: new version of opensync was released (0.22)

Hi,

On Tue, Nov 06, 2007 at 12:10:40PM -0000, Turgon wrote:
> Hello. After some searching and testing, I think that the version of
> Opensync available for Gutsy is too old to support my Nokia N70,
> while a bit newer version is reported to work (
> http://geektalk.andreat.de/2006/11/how-to-syncronize-nokia-n70-palm.html
> ). I don't know if this issue is important enough to justify a
> backport; if not, it would be nice if the package could be updated
> for Ubuntu 8.04, if all you people who kindly contribute with your
> work don't find another more pressing task.

Updated opensync packages (from the 0.3x development series) will
shortly be updated to Debian experimental (as soon as uploads to Debian
are possible again) and then synced to hardy.

As the user databas of 0.2x is incompatible to both what's in gutsy
(0.19) and what will be in hardy (0.4x), I don't think backporting the
0.2x series to gutsy makes sense.

When 0.40 gets released and synced to hardy, it might make sense to
backport that for gutsy, but this will probably not happen until late
this year or early 2008.

Michael

Revision history for this message
Thorsten "stan" Koelbl (rockin-stan) wrote : Re: new version of opensync was released (0.22)

Hoping for the backport.
I think, working sync is becoming more and more important and for some people a reason not to use ubuntu as productive system.

Revision history for this message
Michael Banck (mbanck) wrote :

As an update, opensync-0.35 packages are available in Debian experimental; however they are still not very usable and I have refrained from syncing them to hardy for now, anticipating the flow of "it doesn't work for me" bugs, even more so as the there are no GUI tools yet and the documentation is scarce.

Changed in opensync:
status: New → Fix Released
Revision history for this message
Wouter Stomp (wouterstomp-deactivatedaccount) wrote :

0.22-1 is in debian unstable now.

Revision history for this message
Saivann Carignan (oxmosys) wrote :

To all other members of the opensync team, can we work to merge 0.22 from debian and ask for a FeatureFreeze? I believe that upgrading from 0.19 to 0.22 is worth asking for a Feature Freeze, however, I am not able to merge this package from debian without problems so I would need the help of the team, thanks!

Revision history for this message
Michael Banck (mbanck) wrote : Re: [Bug 81831] Re: please merge 0.22 from debian unstable

On Sat, Mar 01, 2008 at 02:57:20AM -0000, Saïvann Carignan wrote:
> To all other members of the opensync team, can we work to merge 0.22
> from debian and ask for a FeatureFreeze? I believe that upgrading from
> 0.19 to 0.22 is worth asking for a Feature Freeze, however, I am not
> able to merge this package from debian without problems so I would need
> the help of the team, thanks!

I suggest waiting for the weekend to pass before merging, and seeing
whether any bugs in Debian show up.

What were the merge problems you had?

Revision history for this message
Saivann Carignan (oxmosys) wrote :

Michael Banck : Thanks for your fast answer. Excellent idea. Concerning the build problem, I attached my build log for ubuntu AMD64 in a clean pbuilder environment. dh_install complains that it does not find some files (python*).

Revision history for this message
Michael Banck (mbanck) wrote :

Thanks for the report. opensync_0.22-2 is now in Debian incoming, which should fix this.

Revision history for this message
Saivann Carignan (oxmosys) wrote :

That's great, let me know if I can take some task that would speed up that process, thanks for working on this.

Revision history for this message
Gavin Hamill (gdh) wrote :

Just a lame 'me too' to request newer opensync in hardy

It will make the 'Windows Mobile howto' at http://www.synce.org/moin/SynceWithUbuntu that little shorter for new users.

Data sync with a PDA is too useful a thing to not have!

Revision history for this message
Michael Banck (mbanck) wrote :

Packages compiled for hardy are now available at the following PPA:

deb http://ppa.launchpad.net/debian-opensync/ubuntu hardy main

Please test them and report bugs.

Revision history for this message
Saivann Carignan (oxmosys) wrote :

Thanks for your work! As far as I tried, bluetooth IRMC plugin does not seem to connect ( it worked with the actual opensync version in hardy ). When connecting to my sony ericson z520a cell phone via bluetooth IRMC, it just fails, here's the terminal outputs :

Member 1 of type evo2-sync just connected
Member 2 of type irmc-sync had an error while connecting: Request failed
Member 1 of type evo2-sync just disconnected
All clients have disconnected
The sync failed: Unable to connect one of the members

I gave the good channel and Mac address, the phone shows that it sync for a second before stoping. The cell phone is correctly paired with the computer. Please ask if I can provide useful informations around this.

Revision history for this message
Michael Banck (mbanck) wrote :

On Sat, Mar 08, 2008 at 04:38:55AM -0000, Saïvann Carignan wrote:
> Thanks for your work! As far as I tried, bluetooth IRMC plugin does not
> seem to connect ( it worked with the actual opensync version in hardy ).
> When connecting to my sony ericson z520a cell phone via bluetooth IRMC,
> it just fails, here's the terminal outputs :
>
> Member 1 of type evo2-sync just connected
> Member 2 of type irmc-sync had an error while connecting: Request failed
> Member 1 of type evo2-sync just disconnected
> All clients have disconnected
> The sync failed: Unable to connect one of the members
>
> I gave the good channel and Mac address, the phone shows that it sync
> for a second before stoping. The cell phone is correctly paired with the
> computer. Please ask if I can provide useful informations around this.

run "export OSYNC_TRACE=/tmp" (or a directory to your liking) before
running msynctool or multisync0.90. Then, grep for ERROR in the
resulting files and/or put the whole files (Thread*) up somewhere for me
to look at.

I just tried here, and it works for me (with a Siemens S55 and on Debian
unstable though).

thanks,

Michael

Revision history for this message
Saivann Carignan (oxmosys) wrote :

I reproduced this problem on Hardy but I did not test Debian Sid. This problem seems to happen in all circumstances as long as I use IRMC bluetooth. Debug files you asked are attached. Thanks!

Revision history for this message
Michael Banck (mbanck) wrote :

On Sun, Mar 09, 2008 at 05:08:36AM -0000, Saïvann Carignan wrote:
> I reproduced this problem on Hardy but I did not test Debian Sid. This
> problem seems to happen in all circumstances as long as I use IRMC
> bluetooth. Debug files you asked are attached. Thanks!

Thanks, seems it's failing to check for slow-sync for notes - can you
try to disable the notes object format in multisync0.90/msynctool and
try again?

Also, which version works for you, the 0.19 packages in hardy, or the
0.22 3rd party packages from http://opensync.gforge.punktart.de ?

Michael

Revision history for this message
Saivann Carignan (oxmosys) wrote :

The 0.22 from ppa repository have this problem. The 0.19 from Hardy worked ( with some bugs, but it worked ).

Actually, notes are already disabled in multisync0.90. They should not sync and even if they should sync, my phone has note functionalities so it should normally work. I will try to test this with msynctool today.

Revision history for this message
Michael Banck (mbanck) wrote :

On Mon, Mar 10, 2008 at 01:01:37AM -0000, Saïvann Carignan wrote:
> Actually, notes are already disabled in multisync0.90.

Hrm, for me, none of the checkboxes under "Disable syncing of objtype:"
are ever automatically disabled, so you did it yourself? Then maybe
there is a bug in multisync0.90, which version of the packages do you
have installed?

Michael

Revision history for this message
Saivann Carignan (oxmosys) wrote :

multisync0.90 0.92.0~svn355-1

Revision history for this message
Saivann Carignan (oxmosys) wrote :

I now have errors with evolution sync that I did not have + the errors I already had. I attached debug files.

You are right, no cases are checked by default, I disabled notes to test if it has some chances to work with notes disabled but it does not change anything.

Also, I tried to sync my cell phone over IRMC with the file plugin and multisync0.90 says that the sync was successful but no files are created.

If you want, I can open separate bug reports and keep active.

Revision history for this message
Kemotaha (kemotaha) wrote :

I tried installed these and did a quick evolution to File sync and it seems to work well. I have a blackberry which I need barry to sync it with. I will try it and let you know if that works.

Revision history for this message
Sammy Spets (sammys) wrote :

For those of you wanting OpenSync 0.22 packages for Ubuntu Gutsy amd64 architecture i've created them and put them into a repository. Add this as a third party repository in Software Sources:

deb http://synerger.com/opensync-amd64 gutsy main

Please note that i'm not providing support or warranty for these packages. They are simply a rebuild for amd64 using the source packages provided at http://opensync.gforge.punktart.de/repo/opensync-0.21

Use these packages at your own risk! I've tested it using my N82 and the sync gives no errors.

Enjoy!

Revision history for this message
Pander (pander) wrote :

Please, let Hardy offer opensync and friends of the latest stable version. On 2008-01-26, OpenSync 0.36 has been released.

For Feisty and Gutsy the (now one and a half year old) 0.19 version was used and hopefully this will not be the case for Hardy. But here:
https://launchpad.net/ubuntu/+source/opensync
it is still listed as 0.19.

Can the latest stable release of OpenSync be distributed with Hardy?

And what about https://bugs.launchpad.net/ubuntu/+bug/183264 in Hardy?

Revision history for this message
Michael Banck (mbanck) wrote :

> And what about https://bugs.launchpad.net/ubuntu/+bug/183264 in Hardy?

bluezync is for opensync-0.3x so that is not feasable for hardy. It will hopefully appear in Debian experimental along with the other 0.3x stuff soonish and should then get merged for intrepid.

Revision history for this message
Michael Banck (mbanck) wrote :

Did anybody try the http://ppa.launchpad.net/debian-opensync/ubuntu packages with kitchensync from hardy? Does it still work? How is the user experience? (I never used kitchensync myself)

Revision history for this message
Scott Kitterman (kitterman) wrote :

If this is wanted it will need a Feature Freeze exception for Hardy. See https://wiki.ubuntu.com/FreezeExceptionProcess

Revision history for this message
Saivann Carignan (oxmosys) wrote :

Unfortunately, I believe that opensync is still unstable. I'm not sure how upgrading to 0.22 would be a advantage. Maybe we should wait for the next stable release.

Revision history for this message
Michael Banck (mbanck) wrote :

On Mon, Apr 07, 2008 at 04:20:50AM -0000, Saïvann Carignan wrote:
> Unfortunately, I believe that opensync is still unstable. I'm not sure
> how upgrading to 0.22 would be a advantage. Maybe we should wait for the
> next stable release.

I don't think shipping 0.19 is better than shipping 0.22, do you? If we
don't ship 0.22, then we should rather remove 0.19, but as it's a
Build-Depends on kdepim, which is in main, this is rather awkward at
this point in the release cycle.

Michael

Revision history for this message
Saivann Carignan (oxmosys) wrote :

Shipping 0.22 would be better because we would report bugs for a more recent branch of opensync but as far as I tested opensync 0.22, it is not usable yet (at least for the tasks I tested with opensync). So yes, I believe that we should upgrade opensync, can you take care to ask for the FeatureFreeze?

Revision history for this message
Michael Banck (mbanck) wrote :

FeatureFreezeExceptionRequest filed as #214083

Revision history for this message
Saivann Carignan (oxmosys) wrote :

0.22 is now in Hardy repositories, a huge thanks to Michael Banck for all his work on this!

Changed in opensync:
status: Confirmed → Fix Released
Revision history for this message
CosminG (ordercomp) wrote :

here is libopensync-plugin-gnokii ?:(

Curtis Hovey (sinzui)
Changed in opensync (Ubuntu):
assignee: Registry Administrators (registry) → nobody
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.