as subject. emerging 21.3.50 -> 22.0.50 as I think 22 becomes the main stream in CVS now. Reproducible: Always Steps to Reproduce: 1. 2. 3.
emacs-21.3.50.ebuild has "x86 ppc sparc ~amd64" keywords, so emacs-22.0.50.ebuild should be marked stable on x86, ppc, and sparc before removing emacs-21.3.50.ebuild. ppc and sparc team: please mark emacs-22.0.50.ebuild stable on your arch.
Sparctastic
Marked ppc stable.
Thanks. Removed emacs-cvs-21.3.50.ebuild from CVS.
Why is this ebuild stable? Its a CVS ebuild, therefore, can't be considered "stable". We should throw this back to atleast ~arch for everyone, if not KEYWORDS="-*".
Based on some reasearch, it has to do with bug 22225, which is now fixed. http://sources.gentoo.org/viewcvs.py/gentoo-x86/app-editors/emacs-cvs/emacs-cvs-21.3.50.ebuild?hideattic=0&rev=1.28&view=log
emacs-cvs-22.0.50 is stable on a few archs. As far as I can tell this is a live CVS ebuild. Why are any of these unmasked?
Did you fail to read the hint posted in Comment #6?
That hasn't been an issue for a very long time.
(In reply to comment #8) > Did you fail to read the hint posted in Comment #6? > I don't see how comment #6 is related. There are live CVS ebuilds in the tree that are not package.masked. If I'm wrong, someone please correct me.
I removed the ebuild containing stable keywords. app-editors/emacs-cvs won't be package.masked however.