Bug 220140 - update-gtk-immodules fails when updating scim-libs.i386
Summary: update-gtk-immodules fails when updating scim-libs.i386
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: scim
Version: 6
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jens Petersen
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-12-19 04:00 UTC by Michel Alexandre Salim
Modified: 2007-11-30 22:11 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-12-22 23:15:24 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Michel Alexandre Salim 2006-12-19 04:00:06 UTC
Description of problem:
scim-libs has an update-gtk-immodules that is called post-install; this script
needs to specially handle the i386 architecture, which puts its gtk-immodules in
/etc/gtk-2.0/i686-redhat-gnu-linux, not /etc/gtk-2.0/i386-redhat-gnu-linux


Version-Release number of selected component (if applicable):
scim-libs-1.4.4-36.fc6

How reproducible:
Always

Steps to Reproduce:
1. rpm -e scim-libs --nodeps
2. yum install scim-libs

  
Actual results:
  Updating  : scim-libs                    ####################### [ 3/19] 
/usr/bin/update-gtk-immodules: line 27:
/etc/gtk-2.0/i386-redhat-linux-gnu/gtk.immodules: No such file or directory


Expected results:
No error


Additional info:

Comment 1 Jens Petersen 2006-12-19 04:43:02 UTC
Apparently the value of %{_host} for i386 has changed without warning
in the buildsystem. :-(

(Pity noone spotted this last week while the package was in testing.)

Comment 2 Jens Petersen 2006-12-19 04:48:31 UTC
FWIW this should be fixed by gtk2-2.10.4-7.fc6.i386 and gtk2-2.10.4-8.fc6.i386
currently in Updates Testing now.

Comment 3 Fedora Update System 2006-12-22 20:20:50 UTC
scim-1.4.4-37.fc6 has been pushed for fc6, which should resolve this issue.  If these problems are still present in this version, then please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.