needed to fix bug 527188 Thanks
11 keywords were dropped at some point.
commit 29142fb582cf5658e3ddd01f85e1d3038c6bbd5e Author: Brian Dolbec <dolsen@gentoo.org> Date: Thu Aug 10 21:53:09 2017 +0000 dev-util/buildbot: Version bump, clean oldest -0.8 release Package-Manager: Portage-2.3.6, Repoman-2.3.1
commit 6876c4d431ee294c53d563d6542f582da9722900 Author: Brian Dolbec <dolsen@gentoo.org> Date: Tue Aug 9 15:46:55 2016 -0700 dev-util/buildbot: Version bump, update live ebuild This version is a major change from previous version.
That last commit did this: - KEYWORDS="~alpha ~amd64 ~arm ~hppa ~ia64 ~ppc ~ppc64 ~s390 ~sh ~sparc ~x86 ~x86-interix ~amd64-linux ~x86-linux ~x64-macos ~x86-macos ~sparc-solaris ~sparc64-solaris ~x64-solaris" + KEYWORDS="~amd64" without opening a keyword request bug report.
I have not opened a re-keyword request bug for buildbot due to several reasons. 1) the miriad of dependencies required to be keyworded, most prominient of them being twisted which has been an ongoing re-keyword request nearly with each new release for the last few years. Current keywords for the latest release: KEYWORDS="~amd64 ~arm ~mips ~s390 ~amd64-fbsd". 2) it is not easy to properly test buildbot for stabilization without having a configured and used buildbot instance. So, setting up a buildbot instance and running it to properly test requires some buildbot knowledge. I have only been using it on amd64 for work. So can not make any claims as to it working correctly on other arches. Although, it is a python based app so should work. But there have been problems with some of the dependencies on other arches. 3) in all this time since I took over buildbot packaging, There has not been a single request to add any other arches to the newer buildbot versions. The old buildbot-0.8 releases are NOT supported upstream any longer, nor are the old split twisted releases which it depends on. We need to get the newer buildbot releases stablized in order to remove the old buildbot-0.8 release and old split twisted pkgs. This will mean the pkg being dropped from many arches. But for the above reasons, I think it is the best couse of action. I think it is only prudent to forget the old keywords list for now and continue stabilizing the only known arch that has been getting used. Keyword requests can be dealt with as they come up.
ok then CCing amd64?
We will soon have to cleanup <dev-python/sqlalchemy-1.3 because of a security issue and buildbot is among the few revdeps holding it up. We might have to de-stabilize the package by cleaning up old buildbots.
