Matthew Palmer <[EMAIL PROTECTED]> writes: > Practically, buildd admins can notice a longer-than-usual queue and throw > hardware at the problem, and that seems to work well enough, and we could > reduce the rate of package inflow through various means, but the problem > still remains -- the queue prioritisation *can* lead to starvation. I'm not > advocating that it be on the top of anyone's todo list to fix it, because we > have relatively effective workarounds, but it's not healthy to say the > problem does not exist, either.
What are these "relatively effective workarounds"? I recall recently hearing that the buildd admins don't want extra machines. So what then? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
