Re: Frequently broken Rawhide/Branched composes

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Pierre-Yves Chibon wrote:

> On Sat, Mar 03, 2018 at 07:35:00PM +0100, Kevin Kofler wrote:
>> So please let us just repeal that "Rawhide can never go backwards"
>> policy.
> 
> This is actually a fair point, but I wonder what prevents us from doing it
> today.

Technically, nothing. This is purely a policy issue.

> The only thing I can think of is that we have no mechanism to choose what
> goes in rawhide and what does not, from the moment you build it, it will
> go into rawhide.
> So maybe gating rawhide, would give us that mechanism to a) prevent
> package we know are broken from entering rawhide, b) potentially remove
> from rawhide package we later find are breaking things.

"b)" can be done without any gating. That's what koji untag-pkg is for.

> I guess another issue with removing something from rawhide is that
> something else may have been built on the top of it, thus removing A would
> imply, automatically rebuilding B, and C, and D...

That would have to happen anyway, even if you bump Epoch to revert A as is 
the policy now.

        Kevin Kofler
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux