COPR build of package fails for epel9

Ask Fedora
,
1

Hi there!

The last few days I try to build some packages in COPR for epel9 and they all failed with error messages referring to GPG package signatures.

I tried rebuilding a package that was successfully built 15 days ago (9982368) and it also failed (10049909).

Comparing the logs, I see that this most probably started after a recent change in the COPR backend build machines from fc42 to fc43.

Under fc43 the following errors occur several times in the logs before the built is aborted:

Import of key(s) didn't help, wrong key(s)?
Public key for glib2-2.68.4-18.el9_7.1.x86_64.rpm is not installed. Failing package is: glib2-2.68.4-18.el9_7.1.x86_64
 GPG Keys are configured as: file:///usr/share/distribution-gpg-keys/redhat/RPM-GPG-KEY-redhat9-release
Public key for kernel-headers-5.14.0-611.24.1.el9_7.x86_64.rpm is not installed. Failing package is: kernel-headers-5.14.0-611.24.1.el9_7.x86_64
 GPG Keys are configured as: file:///usr/share/distribution-gpg-keys/redhat/RPM-GPG-KEY-redhat9-release
Public key for glib2-devel-2.68.4-18.el9_7.1.x86_64.rpm is not installed. Failing package is: glib2-devel-2.68.4-18.el9_7.1.x86_64
 GPG Keys are configured as: file:///usr/share/distribution-gpg-keys/redhat/RPM-GPG-KEY-redhat9-release

Any help / suggestion would be appreciated.

Best regards

  • George
2

Why is the f43 build trying to install EL9 RPMs?

3

Many thos Making sure you're not a bot!

1 Like
Mock RHEL 10 chroot cannot install glib2
4

Hi, thanks for the link.

Apparently there is some general issue with GPG package signatures in RHEL affecting epel9 & 10