You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jul 26, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Jul 26, 2026. It is now read-only.
3.0.0: signature key-id 763629FEC8788FC35128B5F6EE029D1E5EB40300 not found #55
Please don't mind the above, I used the wrong signing key.
The way I understand it, gitdb2 is just for use by older GitPython releases, where is gitdb is the package we use from here on. The reason for gitdb2 to 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 gitdb2 with the correct signing key for it to be picked up one last time.
Activity
Byron commentedon Feb 15, 2020
Thanks for the reminder - please refer to the linked issue for the anticipated course of action.
Byron commentedon Apr 11, 2020
@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.
dvzrv commentedon Apr 11, 2020
@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?
Byron commentedon Apr 11, 2020
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.Byron commentedon May 5, 2020
Release 4.0.5 was created and signed with 2CF6E0B51AAF73F09B1C21174D1DA68C88710E60.
Please feel free to close this issue when verified to be correct.
dvzrv commentedon Mar 25, 2021
4.0.6 is now also signed with
27C50E7F590947D7273A741E85194C08421980C9.upgpkg: python-gitdb 1:4.0.6-1: Upgrade to 4.0.6.
upgpkg: python-gitdb 1:4.0.6-1: Upgrade to 4.0.6.
Byron commentedon Mar 26, 2021
Thank you @dvzrv for staying on top of this, it's much appreciated.