I tried it this way naming key file as RPM-GPG-KEY-Local, placing it into /etc/pki/mock and adding the following entry for my repository to cfg file:
gpgkey=file:///etc/pki/mock/RPM-GPG-KEY-Local
I'm getting same error:
Curl error (37): Couldn't read a file:// file for file:///etc/pki/mock/RPM-GPG-KEY-Local [Couldn't open file /etc/pki/mock/RPM-GPG-KEY-Local]
Best regards,
On 22.01.2021 21:13, Todd Zullinger wrote:
Pavel Raiskup wrote:
On Friday, January 22, 2021 8:55:02 AM CET Daniel Mach wrote:
Isn't the problem that mock uses rpm and dnf from the host environment and expects the GPG key to be there too?
That would be good guess, with '--no-bootstrap-chroot'. But nowadays there are two steps by default:
- Host RPM/DNF installs target RPM/DNF into "bootstrap" chroot
- RPM/DNF from bootstrap is used to install the final chroot
And so the gpg keys need to be available in bootstrap chroot, and sometimes also on host, depending on use-case.
There's a mock's internal method [1] which copies GPG keys into both bootstrap and normal chroot, but it only looks at /usr/share/distribution-gpg-keys - so the easiest way is to put the custom GPG keys there.
Or in /etc/pki/mock, named RPM-GPG-KEY-*. For keys which are not likely to be added to distribution-gpg-keys, this is probably a better location. And then be sure to set the gpgkey parameter in rpm/cs8.cfg appropriately, e.g.:
gpgkey=file:///etc/pki/mock/RPM-GPG-KEY-foo
buildsys mailing list -- buildsys@lists.fedoraproject.org To unsubscribe send an email to buildsys-leave@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/buildsys@lists.fedoraproject.o...
buildsys@lists.fedoraproject.org