| Summary: | Please rekeyword x11-wm/fvwm-2.5.27 | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Christian Faulhammer (RETIRED) <fauli> |
| Component: | New packages | Assignee: | Desktop WM Team (OBSOLETE) <desktop-wm+disabled> |
| Status: | RESOLVED FIXED | ||
| Severity: | enhancement | Keywords: | KEYWORDREQ |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | fvwm-2.5.27.ebuild re-keyworded | ||
|
Description
Christian Faulhammer (RETIRED)
2009-07-08 07:05:52 UTC
I've decided that it's better to stabilize xlockmore for amd64. I have no real experience with the rest of the architectures, so we could leave the arches just like they are for xlockmore, for convenience. Anyone using any of the ~arches is free to do his tests and submit another bug for stabilization on that architecture. I'll briefly submit a new fvwm ebuild with the correct keywords. Created attachment 197200 [details] fvwm-2.5.27.ebuild re-keyworded keywords fixed to work in conjunction with xlockmore 5.28 once it's been stabilized for amd64 as well, bug here: http://bugs.gentoo.org/show_bug.cgi?id=277043 (In reply to comment #1) > I've decided that it's better to stabilize xlockmore for amd64. I have no real > experience with the rest of the architectures, so we could leave the arches > just like they are for xlockmore, for convenience. fvwm had ~alpha and ~ia64 in KEYWORDS and needs xlockmore in 2.5.27. The latter does have neither ~alpha nor ~ia64, so we need to add both architectures for both packages. Stabilisation is still 30 days away. Keyworded fvwm and xlockmore on alpha. ~ia64 done, closing |