Repository navigation
3.0.0: signature key-id 763629FEC8788FC35128B5F6EE029D1E5EB40300 not found #55
Description
Activity
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.
Please don't mind the above, I used the wrong signing key.
The way I understand it,
gitdb2is just for use by older GitPython releases, where isgitdbis the package we use from here on. The reason forgitdb2to come into existence in the first place was me losing access to my pypi account when they disabled support for Google as login mechanism.It's a great reminder though, as probably I should also re-release
gitdb2with the correct signing key for it to be picked up one last time.Release 4.0.5 was created and signed with 2CF6E0B51AAF73F09B1C21174D1DA68C88710E60.
Please feel free to close this issue when verified to be correct.4.0.6 is now also signed with
27C50E7F590947D7273A741E85194C08421980C9.Reacted by Sebastian Thiel- added 2 commits that reference this issue
on Mar 25, 2021
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.