Comment 16 for bug 888665

For backports, I agree entirely that ignoring NotAutomatic is just lovely, and likely the right thing. I understand that this is also being discussed as a solution to turning on NotAutomatic for proposed, however.

The above solution is perfectly reasonable if we also bring britney into play for proposed->updates migration in stable series as we plan to do for proposed->release in the development series. Without that, though, we end up building against bits that we might then be kicking out of proposed. Of course, this happens today, and doesn't seem to be much of a big deal, we manually sort it out when we mess it up, but it would still be nicer to have automated installability checks to go with this whole plan.