Bug 500588

Summary: Hardcoded requirement for notification-daemon
Product: [Fedora] Fedora Reporter: Christoph Wickert <christoph.wickert>
Component: ibusAssignee: Peng Huang <phuang>
Status: CLOSED NEXTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: urgent Docs Contact:
Priority: low    
Version: rawhideCC: i18n-bugs, phuang
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: 1.1.0.20090508-2.fc11 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-05-14 01:12:39 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:

Description Christoph Wickert 2009-05-13 11:37:35 UTC
Description of problem:
I recently imported xfce4-notifyd into F-11 and rawhide, so we have two alternative implementations of a notification daemon, but this package has a hardcoded requirement for notification-daemon instead of the virtual package "desktop-notification-daemon".

Please change the requirement for notification-daemon into desktop-notification-daemon ASAP, because several builds already failed due to the conflicting packages being pulled in both.

Version-Release number of selected component (if applicable):
ibus-0:1.1.0.20090423-1.fc11.i586

Additional info:
https://www.redhat.com/archives/fedora-devel-list/2009-May/msg01062.html
https://bugzilla.redhat.com/show_bug.cgi?id=500513
https://fedorahosted.org/rel-eng/ticket/1788

Comment 1 Peng Huang 2009-05-14 01:12:39 UTC
Fixed in ibus-1.1.0.20090508-2.fc11

Comment 2 Fedora Update System 2009-05-14 01:15:10 UTC
ibus-1.1.0.20090508-2.fc11 has been submitted as an update for Fedora 11.
http://admin.fedoraproject.org/updates/ibus-1.1.0.20090508-2.fc11

Comment 3 Fedora Update System 2009-05-15 23:34:18 UTC
ibus-1.1.0.20090508-2.fc11 has been pushed to the Fedora 11 stable repository.  If problems still persist, please make note of it in this bug report.