Hi!
On Thu, 09 Jul 2015, Rich Freeman wrote:
> 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.
What can I say? Apparently some devs file stabilization bugs
without checking these things. I run repoman full before
committing anything, so that's where the buck stops.
> If it isn't ~alpha to begin with, then it shouldn't be going
> stable on alpha.
Ack. Hence my mention of "keyword and soak."
I am confident that nobody here would argue that "casual
stabilization bugs" are okay and the arch teams should just suck
it up. But unfortunately, it still happens.
Regards,
Tobias
--
Sent from aboard the Culture ship
GCU (River Class) Displacement Activity
