Is it OK to stabilize =net-analyzer/labrea-2.5-r2 ? If so, please CC all arches which have stable keywords for older versions of this package and add STABLEREQ keyword to the bug.
Nothing interesting happened in this revision.
(In reply to comment #1) > Nothing interesting happened in this revision. Please proceed with stabilization at least on amd64. x86 may pass, if they want to.
(In reply to comment #2) > (In reply to comment #1) > > Nothing interesting happened in this revision. > > Please proceed with stabilization at least on amd64. x86 may pass, if they > want to. No, x86 should stabilise too.
(In reply to comment #1) > Nothing interesting happened in this revision. I never seen comment like this in stabilization request. The obviously answer is: why has been committed a new revision if we won't stabilize?
(In reply to comment #4) > (In reply to comment #1) > > Nothing interesting happened in this revision. > > I never seen comment like this in stabilization request. You're new here, right? > The obviously answer is: why has been committed a new revision if we won't > stabilize? That's not an answer. You committed a revision that changed absolutely nothing interesting whatsoever for any users out there, except adding the ~amd64 keyword which you could have safely added to the previous revision. But do go ahead, if it is "keywording theatre" you want.
(In reply to comment #5) > That's not an answer. You committed a revision that changed absolutely > nothing interesting whatsoever for any users out there, except adding the > ~amd64 keyword which you could have safely added to the previous revision. Are you able to see the changelog? -> Eapi4, convert src_install to emake, add ~amd64 If possible I don't like to do a big change into stable version, so I made a new revision. > But do go ahead, if it is "keywording theatre" you want. I don't want anything. I requested the stabilization to have an available stable version on amd64.
x86 stable
amd64 stable. Last arch, closing