On Thu, Jul 9, 2015 at 10:51 AM, Tobias Klausmann <klaus...@gentoo.org> wrote: > > What I meant is when I get a stabilization bug for > cat-egory/foo-1.2.3 which depends on >=other-cat/bar-1.0.5. The > latter is amd64 but not alpha or ~alpha. And it, in turn, has yet > more deps in the same vein. Now I have several options:
If bar-1.0.5 isn't alpha or ~alpha, then foo-1.2.3 shouldn't be ~alpha either, and repoman should complain about this for any non-dev/exp arches. If it isn't ~alpha to begin with, then it shouldn't be going stable on alpha. I do agree that at the first bump that triggers the need to drop alpha keywords (testing or stable) there should be a keyword request submitted to the alpha team to get that sorted out. They could choose at that time to do the testing/keywording/etc to get foo-1.2.3 back onto ~alpha so that it is ready to be stabilized at the right time (or at least with less delay), or they could choose at that time to just leave the keywords off in which case they aren't pestered about stabilization. -- Rich
