On 9/20/19 4:39 AM, jkonecny(a)redhat.com wrote:
On Thu, 2019-09-19 at 14:29 -0700, Kevin Fenzi wrote:
> On 9/18/19 1:41 AM, jkonecny(a)redhat.com wrote:
...snip...
>> In my F31 case most importantly copr will be in similar
situation
>> that
>> they will use Rawhide *new* compose (if they won't be really fast)
>> instead of the old one for a new Fedora chroot. And I don't think
>> we
>> want to add some lag between the successful Fedora compose and the
>> Rawhide one.
>
> I'm not sure what you mean here, can you expand on it or provide an
> example?
What COPR was doing (I think they changed it after F31) then before a
new chroot in COPR appeared they copied the latest Rawhide chroot to
have something working in the new chroot. So, if we build the new
Rawhide the same day as F31 branch compose is ready then they don't
have a time to react and sync "the old Rawhide" version.
I thought that was not manually copied, but just that way because we had
no f31 compose, so f31 and rawhide were the same thing (due to
mirrormanager).
However, that above is just an example of what happened to me. I
think
most of people here dealing with this stuff have to somehow react that
the compose is available. So or so, you are trying to solve something
else by the freeze than me.
I'm not sure If I can help you with the "Rawhide freeze" decision I
didn't had the problem you are describing.
Sure.
kevin