| Summary: | x11-clocks/wmclockmon [PATCH] mark UNBROKEN | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Ports & Packages | Reporter: | Chris Hutchinson <portmaster> | ||||||
| Component: | Individual Port(s) | Assignee: | Soeren Straarup <xride> | ||||||
| Status: | Closed FIXED | ||||||||
| Severity: | Affects Many People | CC: | portmaster, w.schwarzenfeld | ||||||
| Priority: | --- | Keywords: | patch | ||||||
| Version: | Latest | Flags: | bugzilla:
maintainer-feedback?
(xride) |
||||||
| Hardware: | Any | ||||||||
| OS: | Any | ||||||||
| Attachments: |
|
||||||||
Created attachment 162127 [details]
QA LOG for x11-clocks/wmclockmon
Does fetch now fine. wmclock-config starts wmclock-cal starts but wmclockseems to start, but shows no clock (I am non 10.4 with fvwm-crystal) Maybe, it's a problem with fvwm-crysal. Tell me, if this will be closed, and I should open a new PR. Is not broken anymore. It is done. Solved. |
Created attachment 162126 [details] svn diff to fix x11-clocks/wmclockmon mark x11-clocks/wmclockmon NOT broken. Not sure what happened. But x11-clocks/wmclockmon is currently marked BROKEN, for being unfetchable. A quick check seems to indicate that's false -- see x11-clocks/wmclockmon-QA-LOG attached, for details. svn diff, and QA LOG attached to this pr(1). That's it! :-) --Chris