mockbuild: Import of key(s) didn't help, wrong key(s)?
by Brad Bell
I am having trouble with mockbuild on rawhide and do not know how to proceed ?
First I tried
fedpkg mockbuild
and got the response
Could not execute mockbuild: Could not find the release/dist from branch name rawhide
Please specify with --release
Then I tried
fedpkg --release rawhide
and got the same response.
Then I checked
git show-ref rawhide
git show-ref f34
and determined that they were the same.
Then I tried
fedpkg --release f34 mockbuild
and got the response
... snip ...
warning:
/var/lib/mock/fedora-rawhide-x86_64/root/var/cache/dnf/fedora-2d95c80a1fa0a67d/packages/alternatives-1.15-2.fc34.x86_64.rpm:
Header V4 RSA/SHA256 Signature, key ID 9867c58f: NOKEY
fedora 1.6 MB/s | 1.6 kB 00:00
Importing GPG key 0x45719A39:
Userid : "Fedora (34) <fedora-34-primary(a)fedoraproject.org>"
Fingerprint: 8C5B A699 0BDB 26E1 9F2A 1A80 1161 AE69 4571 9A39
From : /usr/share/distribution-gpg-keys/fedora/RPM-GPG-KEY-fedora-34-primary
Key imported successfully
fedora 1.6 MB/s | 1.6 kB 00:00
GPG key at file:///usr/share/distribution-gpg-keys/fedora/RPM-GPG-KEY-fedora-34-primary (0x45719A39)
is already installed
fedora 1.6 MB/s | 1.6 kB 00:00
Importing GPG key 0x9570FF31:
Userid : "Fedora (33) <fedora-33-primary(a)fedoraproject.org>"
Fingerprint: 963A 2BEB 0200 9608 FE67 EA42 49FD 7749 9570 FF31
From : /usr/share/distribution-gpg-keys/fedora/RPM-GPG-KEY-fedora-33-primary
Key imported successfully
Import of key(s) didn't help, wrong key(s)?
Public key for alternatives-1.15-2.fc34.x86_64.rpm is not installed. Failing package is:
alternatives-1.15-2.fc34.x86_64
GPG Keys are configured as:
file:///usr/share/distribution-gpg-keys/fedora/RPM-GPG-KEY-fedora-34-primary,
file:///usr/share/distribution-gpg-keys/fedora/RPM-GPG-KEY-fedora-34-primary,
file:///usr/share/distribution-gpg-keys/fedora/RPM-GPG-KEY-fedora-33-primary
Public key for audit-libs-3.0.1-1.fc35.x86_64.rpm is not installed. Failing package is:
audit-libs-3.0.1-1.fc35.x86_64
... snip ...
3 years, 2 months
Re: Stale provenpackagers to be removed from group
by Brad Bell
I build a new upstream source for the package I maintain during January of each year, instead of
once every six months.
Currently I only submit other builds when a problem arises (with my package) during the production
engineering builds a the new release of Fedora. (Each build of my package automatically does
extensive testing).
In accordance with the new policy, should I submit a build with not real changes for each release of
Fedora ?
On 2/10/21 8:44 AM, Ben Cotton wrote:
> In accordance with the new FESCo policy[1] the following
> provenpackagers will be submitted for removal in two weeks based on a
> lack of builds submitted in the last six months. If you received this
> directly, you can reply off-list to indicate you believe you should
> still have provenpackager status.
>
> This is the first time we have done a regular audit of the
> provenpackagers group, so please be patient with any hiccups in the
> process. This will be done regularly at the branch point in each
> release.
>
... snip ...
3 years, 2 months