packaging bugs in uim prevent upgrade to edgy

Bug #69020 reported by Rumpeltux
48
Affects Status Importance Assigned to Milestone
Universal Input Method (UIM)
Won't Fix
Critical
uim (Ubuntu)
Won't Fix
High
MOTU

Bug Description

When updating dapper to edgy, the update-manager failed while configuring uim-common:

Preparing to replace uim-common 1:1.0.0-1ubuntu1 (using .../uim-common_1%3a1.2.1-3ubuntu2_all.deb) ...
ERROR: unbound variable (errobj is-set-ugid?)
*backtrace*
>>(is-set-ugid?)
>>(if (is-set-ugid?) (list (string-append (sys-pkglibdir) "/plugin")) (filter string? (append (list (getenv "LIBUIM_PLUGIN_LIB_DIR") (string-append (getenv "HOMEuim-common") "/.uim.d/plugin") (string-append (sys-pkglibdir) "/plugin")) (if (getenv "LD_LIBRARY_PATH") (string-split (getenv "LD_LIBRARY_PATH") ":") ()))))
>>(define uim-plugin-lib-load-path (if (is-set-ugid?) (list (string-append (sys-pkglibdir) "/plugin")) (filter string? (append (list (getenv "LIBUIM_PLUGIN_LIB_DIR") (string-append (getenv "HOME") "/.uim.d/plugin") (string-append (sys-pkglibdir) "/plugin")) (if (getenv "LD_LIBRARY_PATH") (string-split (getenv "LD_LIBRARY_PATH") ":") ())))))
>>(require "plugin.scm")
>>(require "init.scm")
>>(*catch (quote errobj) (require "init.scm"))
>>(eq? (quote *init.scm-loaded*) (*catch (quote errobj) (require "init.scm")))
ERROR: unbound variable (errobj custom-reload-customs)
ERROR: unbound variable (errobj custom-choice-rec-sym)
ERROR: unbound variable (errobj plugin-alist)
ERROR: wta to car (errobj t)

Tags: edgy-upgrade
Revision history for this message
Rumpeltux (rumpeltux) wrote :

After failing parts of the installation the file-open-dialog of firefox (for attaching a file) shows unreadable filename (lots of \square s), proably to locale/encoding problems. Might affect other applications as well.

Michael Vogt (mvo)
Changed in update-manager:
importance: Undecided → High
status: Unconfirmed → Confirmed
description: updated
Revision history for this message
In , Bugs-freedesktop-org (bugs-freedesktop-org) wrote :

Copying from https://bugs.launchpad.net/products/uim/+bug/69020 and
https://bugs.launchpad.net/products/uim/+bug/71542

The upgrade of uim completely messes up the upgrade from dapper to edgy. This
leaves the users of uim at risk of ending up with a useless installation of
ubuntu if they cannot find the workarounds.

Revision history for this message
In , Ek-kato (ek-kato) wrote :

(In reply to comment #0)
> Copying from https://bugs.launchpad.net/products/uim/+bug/69020 and
> https://bugs.launchpad.net/products/uim/+bug/71542

Hmm, this seems a packaging bug in Ubuntu, and not our bug.
Please consult uim package maintainer of Ubuntu.

As I don't use Debian/Ubuntu, I'm totally not sure about their packages. But as
far as I can tell, it seems something is wrong in updating sequence in uim
packages (mismatch in libuim version and uim-common package).

With a quick search, uim package in Debian is already in 1.2.1-9, so possibly
checking their bugs and changelog can help
(http://packages.debian.org/changelogs/pool/main/u/uim/uim_1.2.1-9/changelog).

Revision history for this message
In , Bugs-freedesktop-org (bugs-freedesktop-org) wrote :

カトウさん、

返事ありがとうございます。

Revision history for this message
Rolf Leggewie (r0lf) wrote : Re: update-manager failed for configuring uim-common

Just marked my bug 71542 as a dupe to this one. There might be some interesting information there as well.

Revision history for this message
Rolf Leggewie (r0lf) wrote :

BTW, for anybody else that has this problem. I was able to forcefully resolve this by fiddling with /var/lib/dpkg/status as suggested in support ticket 2451.

Rolf Leggewie (r0lf)
Changed in uim:
status: Confirmed → Unknown
Revision history for this message
Rolf Leggewie (r0lf) wrote :

Oh no! It seems my addition of the freedesktop bug to this tracker removed the confirmed flag for this bug and with it the high importance status :-( This is all the worse since one of the uim devs already answered that this looks more like a packaging than an upstream bug. He did provide some valuable information which I quote here.

"But as far as I can tell, it seems something is wrong in updating sequence in uim packages (mismatch in libuim version and uim-common package).

With a quick search, uim package in Debian is already in 1.2.1-9, so possibly checking their bugs and changelog can help (http://packages.debian.org/changelogs/pool/main/u/uim/uim_1.2.1-9/changelog)."

Changed in uim:
status: Unconfirmed → Confirmed
Rolf Leggewie (r0lf)
Changed in uim:
importance: Undecided → High
Rolf Leggewie (r0lf)
Changed in uim:
assignee: nobody → motu
Changed in uim:
status: Unknown → Confirmed
Revision history for this message
In , Yamaken (yamaken) wrote :

Closed since not an our bug although it's a critical problem. Thanks for the
report. And continue feeling free to post any bugs that uncertain about who is
responsible for the bug.

Changed in uim:
status: Confirmed → Rejected
Revision history for this message
Jérôme Guelfucci (jerome-guelfucci-deactivatedaccount) wrote :

Is this still an issue ?

Changed in uim:
status: Confirmed → Incomplete
Revision history for this message
Rolf Leggewie (r0lf) wrote :

What kind of answer do you expect for an upgrade bug?

I can only assume yes.

Changed in uim:
status: Incomplete → Confirmed
Revision history for this message
Rolf Leggewie (r0lf) wrote :

FWIW, edgy is close to becoming unsupported and the subsequent upgrades of uim went fine. If there is no objection, I'll close this bug as wontfix soon.

Revision history for this message
Daniel T Chen (crimsun) wrote :

Expiring due to edgy lapsing from supported. Thanks for keeping an eye on this bug, and please reopen it if it's reproducible in further distribution upgrades between supported release versions.

Changed in uim:
status: Confirmed → Won't Fix
Changed in uim:
importance: Unknown → Critical
status: Invalid → Won't Fix
Changed in uim:
importance: Critical → Unknown
Changed in uim:
importance: Unknown → Critical
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

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