Bug 133227
Summary: | iiimf-server blocking yum update | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Zack Cerza <zcerza> |
Component: | im-sdk | Assignee: | Yu Shao <yshao> |
Status: | CLOSED NEXTRELEASE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | rawhide | CC: | eng-i18n-bugs, petersen, thierryn, wtogami |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2004-09-24 02:37:04 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 130887 |
Description
Zack Cerza
2004-09-22 16:16:34 UTC
iiimf-le-newpy should be disabled, which version of im-sdk are you using? I think the problem is that the old iiimf-le-newpy required a particular EVR of iiimf-server, but since it does not get obsoleted/removed it conflicts with newer im-sdk packages. Here's what I have. Not sure if im-sdk creates any packages that don't start with 'iiimf'. $ rpm -qa | grep iiimf iiimf-le-chinput-0.3-6 iiimf-csconv-12.0.1-3.svn1891 iiimf-le-xcin-0.1.7-4 iiimf-le-newpy-12.0.1-3.svn1891 iiimf-docs-12.0.1-3.svn1891 iiimf-le-canna-12.0.1-3.svn1891 iiimf-libs-devel-12.0.1-3.svn1891 iiimf-libs-12.0.1-3.svn1891 iiimf-le-unit-12.0.1-3.svn1891 iiimf-emacs-12.0.1-3.svn1891 iiimf-gtk-12.0.1-3.svn1891 iiimf-x-12.0.1-3.svn1891 iiimf-server-12.0.1-3.svn1891 iiimf-le-hangul-12.0.1-3.svn1891 iiimf-le-newpy will be obsoleted by iiimf-le-chinput, the new build of iiimf-le-chinput-0.3-6 will be ready soon. This hopefully will fix the problem. Note that "yum update" does not follow obsoletes, only "yum upgrade" does. typo, next build of iiimf-le-chinput will be version 0.3-7 *** Bug 133690 has been marked as a duplicate of this bug. *** |