On 2/18/20 1:00 PM, Stephen John Smoogen wrote:
The mock in f30 updates-testing mock-2.0-2.fc30.noarch fixed it for me
and I was able to build packages for f32 and rawhide locally.
Ugh. The maintainer used a custom update name and that threw me off. First time I've
seen that used.
___
On Tue, 18 Feb 2020 at 13:55, Michael Cronenworth wrote:
>
> On 2/18/20 8:49 AM, Till Hofmann wrote:
> > On 2/18/20 3:44 PM, Richard Shaw wrote:
> >> I am unable to build packages using mock for either f32 or f33 which is
> >> very problematic.
> > Afaik you need mock from updates-testing for the
On 2/18/20 8:49 AM, Till Hofmann wrote:
On 2/18/20 3:44 PM, Richard Shaw wrote:
I am unable to build packages using mock for either f32 or f33 which is
very problematic.
Afaik you need mock from updates-testing for the new config/keys.
No one has pushed out an update for them besides Rawhide.
Hi Richard,
On 2/18/20 3:44 PM, Richard Shaw wrote:
> I am unable to build packages using mock for either f32 or f33 which is
> very problematic.
Afaik you need mock from updates-testing for the new config/keys.
Kind regards,
Till
___
devel mailing lis
I am unable to build packages using mock for either f32 or f33 which is
very problematic.
warning:
/var/lib/mock/fedora-rawhide-x86_64/root/var/cache/dnf/fedora-2d95c80a1fa0a67d/packages/gdb-minimal-9.1-3.fc33.x86_64.rpm:
Header V3 RSA/SHA256 Signature, key ID 9570ff31: NOKEY
fedora
1.6 MB
