-
Notifications
You must be signed in to change notification settings - Fork 67
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
3.0.0: signature key-id 763629FEC8788FC35128B5F6EE029D1E5EB40300 not found #55
Comments
Thanks for the reminder - please refer to the linked issue for the anticipated course of action. |
@dvzrv I have just released v4.0.4 which should be signed with the known key. CC @Harmon758 In May we should be able to move package signing to CI while maintaining a chain of trust. |
@Byron thanks for being on top of this! :) I have one follow up question: Why is the package now again pushed to gitdb and not as before gitdb2? |
Please don't mind the above, I used the wrong signing key. The way I understand it, It's a great reminder though, as probably I should also re-release |
Release 4.0.5 was created and signed with 2CF6E0B51AAF73F09B1C21174D1DA68C88710E60. |
4.0.6 is now also signed with |
Upstream switched to new key-id 27C50E7F590947D7273A741E85194C08421980C9 after breaking their hardware key which carried the previous: gitpython-developers/gitdb#55 git-svn-id: file:///srv/repos/svn-community/svn@903436 9fca08f4-af9d-4005-b8df-a31f2cc04f65
Upstream switched to new key-id 27C50E7F590947D7273A741E85194C08421980C9 after breaking their hardware key which carried the previous: gitpython-developers/gitdb#55 git-svn-id: file:///srv/repos/svn-community/svn@903436 9fca08f4-af9d-4005-b8df-a31f2cc04f65
Thank you @dvzrv for staying on top of this, it's much appreciated. |
For the same reasons I can not build and package gitpython for Arch Linux, I can not build and package gitdb in version 3.0.0.
Please fix the trust chain for the new key or release a new version with the already trusted key.
The text was updated successfully, but these errors were encountered: