On Mon, Mar 04, 2019 at 10:11:27AM -0800, Kevin Fenzi wrote:
On 3/4/19 12:47 AM, Pierre-Yves Chibon wrote:
> On Mon, Mar 04, 2019 at 09:40:32AM +0100, Vít Ondruch wrote:
>> Also, how are the mass rebuilds envisioned?
>
> Just as anyone would: by opting-out of gating.
> Maybe that term is overloaded. The way I see it there are two ways to opt-out:
> - remove the gating.yml file in the package's git repo, not scalable especially
> for mass-rebuild
> - build in the koji candidate tag directly, thus by-passing the testing tag
> where tests happen. This would be the approach releng would do for
> mass-rebuild.
Well, to be clear, mass rebuilds already use a side tag and then are
merged in. So they would just be merged into the candidate tag or whatever.
>
>> I can't imagine that Ruby
>> rebuild will be held from entering rawhide due to some broken
>> dependency. Not sure how you want distinguish the package, which is
>> typically "single" from "multi" package.
>
> This is a decision left in the hands of the packagers, I'm pretty sure they
know
> more their packages than I do and thus I'm in no position to make this
decision.
I think perhaps it would be useful to easily show waivers?
like a weekly waiver report or something so we could tell what packages
and maintainers are waiving results?
We will definitely want to look into waivers at one point (both which tests as
well as which maintainers), I am not sure we need it from the get go though :)
Pierre