-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
mock -r fedora-eln-x86_64 --init fails #28
Comments
@mohanboddu Can you look into this, please? It looks like more fallout from the F34->F35 signing issue. |
See also https://pagure.io/releng/issue/10007 (closed). Was there a successful ELN compose since then? |
distribution-gpg-keys should be updated to handle https://src.fedoraproject.org/rpms/fedora-repos/c/dac6fcdf6c063f1e049ddc7b33f3b299bb643d7f?branch=rawhide |
Filed a bz for it - https://bugzilla.redhat.com/show_bug.cgi?id=1931095 |
Seems not:
|
This happens because packages in that repo are signed with fedora-34-primary while mock is configure to use fedora-rawhide-primary which is a symlink pointing to fedora-35-primary. I will try to come with something together with @praiskup tomorrow morning - likely use N and N-1 key in Mock's config. |
Yes, this deserves work-around in mock-core-configs, rpm-software-management/mock#702 |
Well, the packages in ELN are always meant to be signed with the Rawhide key. The glitch here happened that we forgot to run the re-signing at Branch and then we have also had compose failures since we actually did so. It likely wouldn't hurt for |
But is ELN really tracking rawhide at this point. The most recent builds at https://koji.fedoraproject.org/koji/packageinfo?packageID=57 suggest that ELN is following Fedora 34 content. |
fedora-ci/eln-build-trigger@e06c43a Looks like someone forgot to update the trigger until two days ago. It should be properly tracking Rawhide at this point. |
But chkconfig-1.15-2.eln109 is signed with both F34 and F35 key. |
This is working these days, so I'm closing this ticket. |
There seems to be a key mismatch:
Seen with:
I don't see any relevant packages in updates-testing.
The text was updated successfully, but these errors were encountered: