Bug 618398
| Summary: | update to latest version | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Jiri Moskovcak <jmoskovc> | ||||||
| Component: | xfce4-notifyd | Assignee: | Christoph Wickert <christoph.wickert> | ||||||
| Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | low | ||||||||
| Version: | 14 | CC: | christoph.wickert, dfediuck, johannes.lips | ||||||
| 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: | 2010-11-27 16:46:21 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: | |||||||||
| Attachments: |
|
||||||||
|
Description
Jiri Moskovcak
2010-07-26 20:28:35 UTC
Created attachment 434523 [details]
regenerated dbus name patch
Created attachment 434524 [details]
build fixes
Thanks, I missed the new release because it wasn't announced on the Xfce mailing list. Where did you find the source of 0.2.0? I cannot find it at http://spuriousinterrupt.org/files/ or http://archive.xfce.org/src/apps/xfce4-notifyd/ I found just announcement here: http://spuriousinterrupt.org/projects/xfce4-notifyd saying: """ The current version of xfce4-notifyd is 0.2.0, released on 15 April 2010. Source: .tar.bz2 (SHA1 sum, PGP signature) """ but the download link is broken, so I compiled the latest git. J. Meanwhile I contacted Brian, let's see what he replies. If there is no source tarball available, I will use GIT. This bug appears to have been reported against 'rawhide' during the Fedora 14 development cycle. Changing version to '14'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Hey, as promised I worked on it... I took the latest git source but am totally unsure if I did this right, regarding versioning etc.. I removed all patches because it just built fine without them but perhaps there is another reason that they should be applied. SRPM URL: http://hannes.fedorapeople.org/xfce4-notifyd-0.2.0-0.2.20100826git.fc14.src.rpm SPEC URL: http://hannes.fedorapeople.org/xfce4-notifyd.spec I hope this helps as a little appetizer I add a screenshot of the new xfce4-notifyd in action... ;) http://hannes.fedorapeople.org/Screenshot%20-%2010132010%20-%2002:43:25%20PM.png Finally 0.2.0 was released today. I built it for rawhide, you also want me to push it to F14? Is there anything wrong with the 0.1.0 package that justifies an update? One thing I don't like is the fact that the new version requires libxfce4ui instead of libxfcehui4. Basically it is targeted at Xfce 4.8. I don't know if there are any known bugs which are closed by this update. But for me the new functionality which could be seen in previous screenshot is one big plus for pushing it into fedora 14. I mean all the dependencies are there and I don't think that this is such a critical package. I would go for pushing it because I don't really see any drawback of an update despite the fact that it is an "major" version update which should be avoided with the new update policy. There was indeed a problem with the 0.1.0, see bug 657781. Not sure if I'm going to push 0.2.0 to F14, ATM we are thinking of backporting 0.2.0 to libxfcegui4 and call it 0.1.5. I really dislike the idea of having libxfce4ui in F14/Xfce 4.6. The reasons I wanted this update are: 1. overlapping notifications when there are multiple notifications shown at the same time 2. the notifications are shown at wrong positions when using multiple monitors.. at least this would be nice to have fixed in F14, I think we can wait for the eycandy from 0.2.0 to F15 :) |
