I would like to request stabilization of most packages in the app-xemacs category. The reason for this mass action is that xemacs development has been dormant for ~3 years. In the past few months I've updated all xemacs packages to the latest versions and I would like to get everything up-to-date and stable now. All packages and version to be stabilized are listed in the attached file. This operation concerns 124 packages so I propose the following procedure. I will do all the keywording in one go to save everyone a lot of work, but obviously I will only do so after getting the go-ahead of the arches involved. I would like to set a deadline on this to avoid dragging this on: May 19th, 2007. If you let me know at that time that things are ok I'll keyword your arch, otherwise I'll leave it alone (but the bug will remain open ;-) I realize that not all packages are currently marked as testing by all arches, in particular HPPA and to a lesser extend PPC64 are missing keywords. I think that in this case the sensible thing is to just mark these packages directly to stable. Regarding testing: All of the individual packages are also available as a single sumo package called app-xemacs/xemacs-packages-sumo-2006.12.21. All packages have been available upstream for some time and have been found stable. Theoretically these packages should be arch-independant because they only contain elisp running within xemacs. If xemacs works on your arch then the packages should work as well. In theory, anyway. :-) Please let me know if you have other questions or concerns.
Created attachment 116984 [details] List of app-xemacs packages including versions
All app-xemacs packages that are keyworded for HPPA have the latest version stable: app-xemacs/apel-1.32 hppa app-xemacs/xemacs-base-2.08 hppa app-xemacs/mule-base-1.49 hppa app-xemacs/fsf-compat-1.15 hppa For all the other packages, insofar as they are not *DEPENDs of other packages in the tree that are keyworded for HPPA, there is a simple rule: any PA user who finds that package app-xemacs/XYZ works on PA hardware, can simply drop a note at <hppa@gentoo.org>, visit us at irc://chat.freenode.net/gentoo-hppa on Freenode or even go as far as to file a fullblown bug on https://bugs.gentoo.org/ and assign it to <hppa@gentoo.org>. Needless to say, but I will do it anyway, testing and stabilising dozens of packages just because I can is a pointless and fruitless exercise until users actually ask for it. Kind regards, JeR on behalf of the Gentoo/HPPA team
As I was voted to handle this bug for x86...it is ok for us to let the packages be keyworded by you. May 19th is ok, I will test some of the packages and let you know, if there are failures.
Feel free to take care of this for PPC.
sparc is ok with the list.
We can go too to avoid the noise :-)
So far I've got the OK from x86, sparc, and ppc. Still missing are amd64 and ppc64. As I currently don't have a broadband connection I'm going to postpone the stabling until next weekend (2/3 June). AMD64, PPC64: if you would still like to opt in to the stabling, please add a note to the bug before that time. Otherwise I'll leave the bug open after stabling so that you can get things stable in your own time.
(In reply to comment #7) > So far I've got the OK from x86, sparc, and ppc. Still missing are amd64 and > ppc64. Go ahead for amd64, too.
Feel to mark as needed for ppc64.
alpha doesn't want to do this type of keywording. We(alpha)'ll do those stabilizations, thanks.
i think alpha is done. I've stabilized the versions you specified on the packages we have a stable keyword. I just reviewed what i did and it seems i only left 3 packages which i have fixed now.
All done! Thanks everyone, now XEmacs packages are back to 2007 instead of early 2003.
