Re: Answers to "Why is package X not in testing yet?"
Joey Hess wrote:
> I think that shows a bug of some sort.
Actually, it doesn't. A package can break itself. See update_output.txt:
skipped: trophy (6 <- 562)
got: 5+0: a-5
* alpha: trophy
I'm not sure what is going on behind the scenes when this happens,
though. Could someone give a few examples of when this can happen?
The number of broken packages reported is also correct, even though it does
not match the list. This is because update_output.txt only contains the first
port with broken packages, even though the package breaks on several ports.
I've added some explaining text to the page.