On Mon, Feb 8, 2021 at 7:18 PM Petr Menšík <pemen...@redhat.com> wrote: > > Hi, > > I were unable to find time in the schedule, at which the new F35 GPG key > would be activated to sign new builds.
It will be done a week before mass branching, but we are thinking of doing it a bit earlier to give more time. > > In order to prevent bug 1872248 [1], new key must not be used until all > stable releases got new key with symlinks for all supported arches. New > builds were done few days ago, f33 is already in stable [2]. Yet it is > again incomplete and unusable. If the new key is activated now, it would > break (again!) gpg validation of rpm updates. It is my mistake for breaking the symlinks, thanks for the PR, it still needs some fixes but I made the new updates for f33 and f32 with symlinks fixed - https://bodhi.fedoraproject.org/updates/FEDORA-2021-0f90d0c2b0 and https://bodhi.fedoraproject.org/updates/FEDORA-2021-0fe981f3aa > > Please tell me I am missing something. I tried to help with fixing this > state, yet my PR[3] are still not merged. Could be new GPG key > activation explicitly mentioned in the schedule? Isn't it also the key step? We could add it to the schedule, but it wasn't trivial as we generally used to create the key a week before branching and it wasn't used until we hit branching date. > > So, how does Rawhide choose GPG key to sign built packages? Would it > break (again) today? Our automated signing process, robosignatory, does the signing in fedora, in the config[1] of it we will configure what koji keys should be used to sign what tags tags. Is there anything in particular you are looking for. [1] https://pagure.io/fedora-infra/ansible/blob/main/f/roles/robosignatory/templates/robosignatory.toml.j2 > > Regards, > Petr > > 1. https://bugzilla.redhat.com/show_bug.cgi?id=1872248 > 2. https://bodhi.fedoraproject.org/updates/FEDORA-2021-d17f7e917c > 3. https://src.fedoraproject.org/rpms/fedora-repos/pull-requests > > On 2/8/21 5:39 PM, Mohan Boddu wrote: > > Hello All, > > > > Fedora 34 will be branched from rawhide on Feb 09th 2021 as per the > > Fedora 34 schedule[1]. The process takes about a day and everything > > should be ready by Feb 10th 2021. You can still be able to build > > packages normally until then, but after the mass branching, rawhide > > and F34 will be separated. > > > > We will send another email once the branching is done. > > > > Thanks, > > Mohan Boddu. > > > > [1] https://fedorapeople.org/groups/schedule/f-34/f-34-key-tasks.html > > _______________________________________________ > > devel mailing list -- devel@lists.fedoraproject.org > > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > > Fedora Code of Conduct: > > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > > List Archives: > > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org > > > > -- > Petr Menšík > Software Engineer > Red Hat, http://www.redhat.com/ > email: pemen...@redhat.com > PGP: DFCF908DB7C87E8E529925BC4931CA5B6C9FC5CB > _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
