Le vendredi 02 mars 2018 à 10:52 +0100, Pierre-Yves Chibon a écrit : > On Fri, Mar 02, 2018 at 10:04:35AM +0100, Nicolas Mailhot wrote: > > 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. > > Wouldn't side-tags in koji handle this? Imagining there was a tool to > let packagers create/merge them as they need. Maybe. Let's just say, than after working for a few months with go, I've severely revised my understanding of bootstrapping complexity, both on the number of packages it may involve and the number of build phases it may need before succeeding. > > 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 > > That'd actually give us the opportunity to clean up more our repos no? > :) Explain that to someone who had several hours/days of builds rejected because of a broken obsolete package somewhere in the repo :( -- Nicolas Mailhot _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
