On Wed, 15 Feb 2012 20:38:35 -0500, TH (Tom) wrote: > I'm talking a simple practical system to catch > most errors, not the ultimate perfect system > which will never actually be finished :-). It doesn't need to be perfect, but delaying security updates because something else breaks deps isn't a brilliant idea either. And even security updates can break dependencies, too, so they cannot be excluded from such tests. In old Extras pushscripts, I've had the RCNeedsign.py script, which did a repoclosure run on everything including the build system's repo and excluding packages on a blacklist. It was a manual step (although Plague can be configured to run a script after every successful build job). What wasn't trivial was to figure out which builds cause broken deps (sometimes even via non-obvious "Obsoletes" tags, or only multiarch breakage) and to exclude only the bad packages, then run the check once more. An automated and safe skip-broken/remove-broken checker would be the way to go. Progress with AutoQA would be to detect breakage as early as possible and prevent such packages from entering any public repo. Where multiple builds from different people are needed (possibly including builds done with buildroot overrides), it would be the Update System's job to keep these in a non-public "pending" repo, from which to take only those sets of packages which can propagate to updates-testing without causing (dep-)breakage there. -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
