Le jeudi 01 mars 2018 à 12:42 -0800, Kevin Fenzi a écrit :
I disagree entirely with the above. I think the solution is to gate
packages coming into rawhide and hold or reject those that break the
compose until they are fixed.
While I don't disagree with the sentiment there needs to be a mechanism
to handle bootstraps, where there are known-broken repository statuses
between the beginning of the operation, when first bootstapped pavkages
are injected, and the end, when several rebuild passes managed to get
them all in fully build status.
Also, how would you handle obsolete forgotten stray packages that linger
in the repo (because they've not been killed properly, or a tool bug
resulted in their non removal)? Gating gives any such package the power
to block all updates in more critical packages
Regards,
--
Nicolas Mailhot