Please backport multisync 0.82-8 to Dapper

Bug #71916 reported by robepisc
6
Affects Status Importance Assigned to Milestone
Dapper Backports
Invalid
Undecided
Unassigned
Edgy Backports
Invalid
Undecided
Unassigned
multisync (Ubuntu)
Fix Released
Undecided
Unassigned
Dapper
Invalid
Undecided
Unassigned
Edgy
Won't Fix
Undecided
Unassigned

Bug Description

Multisync in Dapper is 0.82-5.2build1.
Fiesty has 0.82-7 and Debian 0.82-8.

Many SonyEricssons (e.g. T630) represent non ASCII characters with UTF-7.
However multisync, untill release 0.82-7, had a bug that didn't allow it to convert from UTF-7 to UTF-8.

In 0.82-7, the Debian maintainer fixed that little bug (debian #274022), making multisync useful for me for the first time.

TIA,
  robepisc

Revision history for this message
John Dong (jdong) wrote :

Does not build in either Dapper or Edgy due to dependency changes, but this is a pretty significnat backport, so I'll see what I can do to work around this.

Revision history for this message
John Dong (jdong) wrote :
Revision history for this message
John Dong (jdong) wrote :

Testing packages for Dapper built from the proposed debdiff available at http://buntudot.org/people/~jdong/backports/dapper/71916/

Please let me know if they work or not.

Changed in dapper-backports:
status: Unconfirmed → Confirmed
Revision history for this message
John Dong (jdong) wrote :
Revision history for this message
John Dong (jdong) wrote :
Changed in edgy-backports:
status: Unconfirmed → Confirmed
Revision history for this message
John Dong (jdong) wrote :

It would seem like apt needs to do a dist-upgrade to fully upgrade to this testing backport.

IMO this is undesirable behavior for backports, as the dist-upgrade fallback for update-manager is:

(1) nonexistent in Dapper
(2) Intimidating/confusing in Edgy

Revision history for this message
robepisc (robepisc) wrote :

Just tried to install your 0.82-7 backport in Dapper.
It can't install libmultisync-plugin-irmc-bluetooth because it depends on the inexistent "bluez-tools" package.
The right package name is "bluez-utils".
Note that this issue also hit Debian (#398308): this is why they released 0.82-8, which fixes this (and only this).

Moreover the palm and syncml plugins are not built anymore in 0.82-7.
This, added to the dist-upgrade issue you mentioned, makes the package, as is, in a bad condition for a backport.

Can't the backport only fix the bug with UTF-7?
The patch is really trivial (see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=274022).
Or this would violate the backport policy?

Ciao,
  robepisc

PS: Thanks for your work on this bug!

Revision history for this message
John Dong (jdong) wrote : Re: [Bug 71916] Please backport multisync 0.82-8 to Dapper

the patch should be considered for dapper updates

On 11/17/06, robepisc <email address hidden> wrote:
> Just tried to install your 0.82-7 backport in Dapper.
> It can't install libmultisync-plugin-irmc-bluetooth because it depends on
> the inexistent "bluez-tools" package.
> The right package name is "bluez-utils".
> Note that this issue also hit Debian (#398308): this is why they released
> 0.82-8, which fixes this (and only this).
>
> Moreover the palm and syncml plugins are not built anymore in 0.82-7.
> This, added to the dist-upgrade issue you mentioned, makes the package, as
> is, in a bad condition for a backport.
>
> Can't the backport only fix the bug with UTF-7?
> The patch is really trivial (see
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=274022).
> Or this would violate the backport policy?
>
> Ciao,
> robepisc
>
> PS: Thanks for your work on this bug!
>
> --
> Please backport multisync 0.82-8 to Dapper
> https://launchpad.net/bugs/71916
>
> --
> ubuntu-backports mailing list
> <email address hidden>
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
>

Revision history for this message
John Dong (jdong) wrote :

Rejected from backports for given reasons

Changed in edgy-backports:
status: Confirmed → Rejected
Changed in dapper-backports:
status: Confirmed → Rejected
Changed in multisync:
status: Unconfirmed → Fix Released
Revision history for this message
John Dong (jdong) wrote :

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=274022

Requesting the patch to fix the above bug in -updates for edgy and dapper...

Revision history for this message
Marius Mikučionis (mmikucionis) wrote :

I am not sure how and whom you are "requesting the patch" but the patch is attached there...

http://bugs.debian.org/cgi-bin/bugreport.cgi/multisync-utf7.patch?bug=274022;msg=15;att=1

Revision history for this message
John Dong (jdong) wrote :

i was requesting action from ubuntu devs :)

On 11/23/06, Marius Mikučionis <email address hidden> wrote:
> I am not sure how and whom you are "requesting the patch" but the patch
> is attached there...
>
> http://bugs.debian.org/cgi-bin/bugreport.cgi/multisync-
> utf7.patch?bug=274022;msg=15;att=1
>
> --
> Please backport multisync 0.82-8 to Dapper
> https://launchpad.net/bugs/71916
>
> --
> ubuntu-backports mailing list
> <email address hidden>
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
>

Revision history for this message
Hew (hew) wrote :

Ubuntu Edgy Eft is no longer supported, so a SRU will not be issued for this release. Marking Edgy as Won't Fix.

Changed in multisync:
status: New → Won't Fix
Akshat Jain (akshatj)
Changed in multisync (Ubuntu Dapper):
status: New → Invalid
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.