Would be interesting as it uses new distutils eclasses. Thanks
Pacho, please, if you file stabilisation requests, don't open a bug and leave it open, halfway done. We have a slew of bugs in the queue so if you could make our lifes easy and speed up the process a bit by filing a complete stabilisation request, and not just "hi, how about stabilisating this package?", it'd be great. Muchas gracias! :)
Go ahead, thanks.
(In reply to Patrice Clement from comment #1) > Pacho, please, if you file stabilisation requests, don't open a bug and > leave it open, halfway done. We have a slew of bugs in the queue so if you > could make our lifes easy and speed up the process a bit by filing a > complete stabilisation request, and not just "hi, how about stabilisating > this package?", it'd be great. Muchas gracias! :) Hi Patrice Well, in general the rule is to let the maintainer decide if arches should be CCed as they are the ones that know the package more, of course we can make an exception (and it's not a problem for me at all to CC arches myself... but please take a look to that bug reports to ensure you un-CC arches if I missed something :)) Best regards!
ppc stable
ppc64 stable
amd64 stable
x86 stable
+ 14 Jun 2015; Patrice Clement <monsieurp@gentoo.org> + javatoolkit-0.3.0-r9.ebuild: + Stable for sparc via ALLARCHES. Drop ia64. Fix bug 529560. + As mentioned by Chewi, we (Gentoo Java) are dropping support for the ia64 altogether.
