Bug 953986 - Something should obsolete uim-gnome
Summary: Something should obsolete uim-gnome
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: uim
Version: 19
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Akira TAGOH
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-04-19 19:27 UTC by Bruno Wolff III
Modified: 2013-05-03 02:48 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-05-03 02:47:59 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Bruno Wolff III 2013-04-19 19:27:10 UTC
Description of problem:
uim-gnome has been dropped from uim but is not obsoleted. This complicates updates since uim cannot be updated while uim-gnome is installed. Currently on multilib f19 systems its a bit worse since yum tries to install a conflicting i686 dependency of uim-gnome to replace the upgraded dependency. This breaks the yum update totally even if skip_broken is used.

Version-Release number of selected component (if applicable):
uim-1.8.5-3.fc19

Comment 1 Fedora Update System 2013-04-22 03:48:04 UTC
uim-1.8.5-4.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/FEDORA-2013-5683/uim-1.8.5-4.fc19

Comment 2 Fedora Update System 2013-04-22 17:18:49 UTC
Package uim-1.8.5-4.fc19:
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing uim-1.8.5-4.fc19'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-5683/uim-1.8.5-4.fc19
then log in and leave karma (feedback).

Comment 3 Fedora Update System 2013-05-03 02:48:01 UTC
uim-1.8.5-4.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, 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.