Hi I would really like regular contributor access to the Guru repository. I've written a bunch of ebuilds for small python utilities for work and would like to contribute those. I have read and am in agreement with the regulations as stated in the Wiki at https://wiki.gentoo.org/wiki/Project:GURU#The_regulations.
We need your public SSH key.
That makes so much sense. Could have thought of it myself. Well, here it is: > ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAILbPKG6QdqFwB3gbcYvFVJjrJYWrtWj9KI6mYGMs4ZHV gentoo-bugzilla@vimja.email
Welcome!
Hi Just tried to do my first push. However, it is rejected. If I understand correctly, it's because my PGP key is not yet know, which makes sense. > pkgdev push -A > [...] > remote: FAIL: Unknown GIT_PUSH_CERT_STATUS > remote: Your push was not signed with a known key. > remote: You MUST use git push --signed with a known key. > remote: Known keys are the subkeys of all primary keys in LDAP. > remote: If you add a new (primary) key to LDAP, please ask Infra to sync gitolite. > remote: If you modified your key and uploaded to keyservers, please wait 4 hours for sync (SKS pool is slow, keys.gentoo.org pool is faster) > remote: If you haven't done either of these things, please see https://wiki.gentoo.org/wiki/Project:Gentoo-keys/> Generating_GLEP_63_based_OpenPGP_keys#Next_steps > [...] How / where can I put my PGP key? Do I just post it in here? -----BEGIN PGP PUBLIC KEY BLOCK----- mDMEYU8cXhYJKwYBBAHaRw8BAQdA29XEC3H6qhLtHG85VX3yAu4JoWgTcGT08YMp fnGVeOW0M05pa2xhdXMgJ3ZpbWphJyBIb2ZlciA8Z2VudG9vLWJ1Z3ppbGxhQHZp bWphLmVtYWlsPoiZBBMWCgBBFiEENoRBcNlpiSwCwzIap7aFIxKOWDsFAmbOF1cC GwEFCQnnGVIFCwkIBwICIgIGFQoJCAsCBBYCAwECHgcCF4AACgkQp7aFIxKOWDu3 QAD/e6Iq1JA0mqTjblnrGoiLec8MRKTRtsbVafcobg+uRSoA/0IvW0iQgbmMbjdo aNdE1s/l7Rs9XFODshxgTkJa5vcAuDMEYU8ctxYJKwYBBAHaRw8BAQdAMV1JuWif 0URLiYEwqvcmXDEiInME9jCJBOQBdfZC746I9QQYFgoAJhYhBDaEQXDZaYksAsMy Gqe2hSMSjlg7BQJhTxy3AhsCBQkJ5xj5AIEJEKe2hSMSjlg7diAEGRYKAB0WIQTU iIbpswhlr9/J0T8kQkqlgqpUzgUCYU8ctwAKCRAkQkqlgqpUzivCAP9MHTPSHYnH CW2gtXMJsYwC392yVETkp0C9w7wPOOLwpAEA9S8nacc5u+jiWilUoeS4Kj961InK yBwEaEXLCGKJWwh3cAEA94A1EG5DVLr95e3E8MnNWyvVMGNeCivslXNWWvEVzPUA /2xXQZGqHRJeqIvMNq/9aDkvFN8IapHeTo6dss1vZfwMuDgEYU8c1RIKKwYBBAGX VQEFAQEHQHusEy0f2WWtpLYZpe7zsAHZjDR60HFkTiyZpQbpTf18AwEIB4h+BBgW CgAmFiEENoRBcNlpiSwCwzIap7aFIxKOWDsFAmFPHNUCGwwFCQnnGNsACgkQp7aF IxKOWDvk5gEA8qNTnfY/6LSIv/uqCuHjlESz2ImWQYQsuwISFgVDfZ4A/1sdtQsY RZe9TdHHW+5o2D8ygwNzqMQnIgRP9ae3BvQN =bQmp -----END PGP PUBLIC KEY BLOCK-----
No, we don't check PGP keys. Did you use `git push --signed`?
Hmm, wait, that's a PGP message. Did something change? I've just pushed your key to our keyservers, try in a few hours.
Thank's. It works now. Although I've found I have to do > pkgdev push -A --signed not just > pkgdev push -A So now I am not sure if the issue was one or the other or maybe even both... I'm just happy it's working now :)
