Bug 428454 – dev-ruby/amatch-0.2.10 and dependencies stable request

• Product: Gentoo Linux
• Status: RESOLVED FIXED

[Description Hans de Graaff 2012-07-28 17:23:17 UTC]

Please test and mark stable:

=dev-ruby/tins-0.3.14
=dev-ruby/amatch-0.2.10

[Comment 1 Anthony Basile 2012-07-29 21:58:18 UTC]

Why only ppc64 and x86?  I see KEYWORDS="~amd64 ~hppa ~ppc ~ppc64 ~x86".  I can do both ppc and ppc64.

[Comment 2 Jeff (JD) Horelick (RETIRED) 2012-07-30 00:20:27 UTC]

x86 stable

[Comment 3 Hans de Graaff 2012-07-30 15:46:47 UTC]

(In reply to comment #1)
> Why only ppc64 and x86?  I see KEYWORDS="~amd64 ~hppa ~ppc ~ppc64 ~x86".  I
> can do both ppc and ppc64.

Because these are the only arches that already have a stable keyword, and I think new stable keywords should be added only on user request.

[Comment 4 Anthony Basile 2012-07-30 19:39:44 UTC]

(In reply to comment #3)
> (In reply to comment #1)
> > Why only ppc64 and x86?  I see KEYWORDS="~amd64 ~hppa ~ppc ~ppc64 ~x86".  I
> > can do both ppc and ppc64.
> 
> Because these are the only arches that already have a stable keyword, and I
> think new stable keywords should be added only on user request.

Okay, I asked because its usually ppc that everyone wants stabilized, not ppc64.  This time its the other way around.

Anyhow, with FEATURES="test" we need to stabilize:

    =dev-ruby/test-unit-2.4.8
    =dev-ruby/tins-0.3.14
    =dev-ruby/amatch-0.2.10

So far test-unit-2.4.8 is fine, so I marked it stable.

tins-0.3.14 fails its tests, I'll open a blocking bug, however, tins-0.4.3 passes.  amatch-0.2.10 also passes but we'll wait for its dep to be fixed.

[Comment 5 Anthony Basile 2012-08-01 10:11:59 UTC]

Stable ppc64.  Closing as the last arch.