On 8/19/19 5:17 AM, Pavel Raiskup wrote:
Hello Iñaki,
On Monday, August 19, 2019 1:29:31 PM CEST Iñaki Ucar wrote:
> On Mon, 19 Aug 2019 at 13:03, Pavel Raiskup <praiskup(a)redhat.com> wrote:
>>
>> On Saturday, August 17, 2019 1:07:04 PM CEST Iñaki Ucar wrote:
>>> The same happens in Copr.
>>
>> Copr is fixed now, builders have installed mock-core-configs and
>> distribution-gpg-keys from updates-testing:
>>
https://bodhi.fedoraproject.org/updates/FEDORA-2019-4724515cbd
>>
https://bodhi.fedoraproject.org/updates/FEDORA-2019-4644c0ee93
>
> Great, thanks. But as Zbigniew said in another thread [1], it would be
> great to anticipate gpg key distribution in the future, to avoid this
> problem every 6 months.
I concur with Zbigniew that we should have F33 keys in advance (see the
different thread) to not repeat this situation for the third time.
I don't think that would help any of the issues in this thread at least.
Unless I am missing some...
> Also, the projects marked to automatically follow Fedora
branching haven't
> branched yet. How long does it take?
The process has not been initiated yet in copr (no F31 at this moment).
Seems like builds in F31 chroot are signed by F32 keys (or the F31 chroot
is effectively F32 chroot, I haven't had a time to check this).
Right. Mirrormanager is pointing both f31 and f32 at rawhide (f32).
So this (mock -r fedora-31-x86_64) should be sorted out first before
we
enable F31 in copr.
Which will be sorted out once we have a fedora 31 compose.
kevin