Re: Import of key(s) didn't help, wrong key(s)?

On Wed, 22 Mar 2017 12:59:07 -0600 Kevin Fenzi wrote: > For f25 and before there's 2 keys per release: a primary key and a > secondary key. For f26 and later there are still two keys, but only > s390 is signed by the secondary one now. > > i686 and x86_64 have always been

Re: Import of key(s) didn't help, wrong key(s)?

On 03/22/2017 06:29 AM, Richard W.M. Jones wrote: > On Tue, Mar 21, 2017 at 05:22:23PM -0700, stan wrote: >> On Tue, 21 Mar 2017 21:21:25 + >> "Richard W.M. Jones" wrote: ...snip... >> Maybe you should try installing the i686 key package? > > Oh right, well spotted. > >

Re: Import of key(s) didn't help, wrong key(s)?

On Tue, Mar 21, 2017 at 05:22:23PM -0700, stan wrote: > On Tue, 21 Mar 2017 21:21:25 + > "Richard W.M. Jones" wrote: > > > Obviously this could be worked around using --nogpgcheck, > > but what does it mean? > > [snip] > > > 00:01 > > warning: > >

Re: Import of key(s) didn't help, wrong key(s)?

the fix was committed with this pull-request [0] due to the present freeze things may be a bit delayed: [0] https://pagure.io/fedora-repos/pull-request/28 Corey W Sheldon: > This is a known issue the gpg key that is shipped in the > fedora-repos-25-3.noarch has an temporary key that was killed,

Re: Import of key(s) didn't help, wrong key(s)?

This is a known issue the gpg key that is shipped in the fedora-repos-25-3.noarch has an temporary key that was killed, work is in progress to fix this, see https://keys.fedoraproject.org/pks/lookup?op=get=0x812A6B4B64DAB85D curl the static key for this one and rpm --import it and try again.

Re: Import of key(s) didn't help, wrong key(s)?

On Tue, 21 Mar 2017 21:21:25 + "Richard W.M. Jones" wrote: > Obviously this could be worked around using --nogpgcheck, > but what does it mean? [snip] > 00:01 > warning: > /var/cache/dnf/fedora-6dbd63560daef6bf/packages/glibc-devel-2.25-4.fc26.i686.rpm: > Header V3