Fvwm should be stabilized in x86 and amd64 as per bug [url=https://bugs.gentoo.org/show_bug.cgi?id=378251]378251[/url]. Can't tell about other arches, but it should be ok as well to stabilize it for all of them. Reproducible: Didn't try It's been a month and a half since 2.6.2 was introduced in ~arch.
Keywords: 2.5.28:0: alpha amd64 ia64 ppc ppc64 sparc x86 Keywords: 2.5.31:0: Keywords: 2.6.2:0: ~alpha ~amd64 ~arm ~ia64 ~ppc ~ppc64 ~sparc ~x86 ~x86-fbsd
What's up with the broken $summary? bug-wranglers should know howto do that, and use $category/$package.
Created attachment 288441 [details] repoman -pvd full opt amd64 : ok Note: Repoman complains about RDEPEND.badindev + I can confirm blocker. Other than that, it seems to be working.
amd64: yes it needs fribidi-0.19.2-r1, yes it emerges with it, the blocker fixed with that dep, yes it passes all else, now for the stable req for fribidi-0.19.2-r1. plus the dep adjustment in the ebuild
(In reply to comment #4) > amd64: > > yes it needs fribidi-0.19.2-r1, yes it emerges with it, the blocker fixed with > that dep, > yes it passes all else, now for the stable req for fribidi-0.19.2-r1. plus the > dep adjustment > in the ebuild The dep adjustment in the ebuild is in a patch I posted at bug 385169. The stabilization of fribidi 0.19.2 has just been requested at bug 385239.
+ 14 Oct 2011; Steve Dibb <beandog@gentoo.org> fvwm-2.6.2.ebuild: + amd64 stable, bug 385143
x86 stable
Dropped rest to ~arch wrt bug #390025. You can stabilize when you get a user request.
