Bug 185683 - Update to 0.3.4
Summary: Update to 0.3.4
Alias: None
Product: Fedora
Classification: Fedora
Component: notify-daemon   
(Show other bugs)
Version: rawhide
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: John (J5) Palmieri
QA Contact:
Depends On: FC5Update
Blocks: 179960 183238
TreeView+ depends on / blocked
Reported: 2006-03-16 21:35 UTC by Brian Pepple
Modified: 2013-03-13 04:50 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-07-25 17:47:27 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Brian Pepple 2006-03-16 21:35:12 UTC
Description of problem: notify-daemon needs to be updated so libnotify can be
updated to 0.3.2.

Spec: http://piedmont.homelinux.org/fedora/notify/notification-daemon.spec

I've gone ahead and created a patch to remove the dependency on libsexy, so that
notify-daemon can be update.  Here's link to the modified spec & a source-rpm. 
In the spec, I've also changed the package name to reflect upstream. If you've
got any questions, don't hestitate to contact me.

Comment 1 John (J5) Palmieri 2006-03-16 21:40:16 UTC
Thanks, putting on update tracker.

Comment 2 Brian Pepple 2006-03-16 21:48:23 UTC
Here's the bug for the update to libnotify, since it appears to be assigned to a
different person.


Comment 3 sangu 2006-05-27 05:30:27 UTC
Please update notification-daemon to 0.3.5 for   libnotify-0.4.0-1 ( bug 179960 ), 
because maybe notify-daemon 0.3.1-10 doesn't support libnotify-0.4.0.

Comment 4 John (J5) Palmieri 2006-05-28 21:10:48 UTC
It is in the process of being updated.  Because of teh rename it needs to go
through the package approval process which is making it take a bit longer.

Comment 5 Matthias Clasen 2006-07-25 17:47:27 UTC
I see notification-daemon 0.3.5 in rawhide, so 
I guess this can be closed. Holler if now.

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