Re: fedora-gpg-keys not updated yet again

[Kevin Fenzi]

On 8/24/19 4:12 AM, Dusty Mabe wrote:
>  
>  
>  On 8/23/19 12:21 PM, Kevin Fenzi wrote:
> > On 8/23/19 4:12 AM, Dusty Mabe wrote:
> >>
> >>
> >> On 8/22/19 12:58 PM, Kevin Fenzi wrote:
> >>> On 8/21/19 9:27 AM, Dusty Mabe wrote:
> >>>>
> >>>>
> >>>> On 8/19/19 6:59 AM, Pavel Raiskup wrote:
> >>>>> On Monday, August 19, 2019 10:50:52 AM CEST Zbigniew
> Jędrzejewski-Szmek wrote:
> >>>>>> Can we *please* send out the FN+1 and FN+2 keys a month before
> branching,
> >>>>>> to *all* releases of Fedora, so we can avoid this pointless
> scramble?
> >>>>>
> >>>>> What about to have F33 keys right now, when the fresh F31 branch is
> out?
> >>>>>
> >>>>
> >>>> +1. Go ahead and make the f33 keys when we branch for f31. 
> >>>
> >>> I don't see how this helps any. I agree we should push out the f33 keys
> >>> before next branching, but why now?
> >>>
> >>
> >> For me it solves any "timing" issues. We often get into a state where
> we're
> >> trying to upgrade to something that is signed with a key we don't have yet.
> >
> > Yes, but it would also be solved by pushing the F33 key out a few weeks
> > or a month or so before branching next time right?
> >
>  
>  It depends on how often people update. If they wait a month to do an update we
>  still get into a situation like this where fedora-gpg-keys doesn't have the key
>  but they are trying to update to a system that has content signed by it.
>  
>  Creating the key for the next next rawhide at time of branching would also mean
>  that we make minimal changes to our existing SOPs. The ONLY change is that now
>  we're creating the key for the next next rawhide instead.    
Sure, I suppose. I'll see about moving that around in the SOP.

kevin