Description

dvzrv

opened on Feb 15, 2020

Issue body actions

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.

Activity

1. Byron

   added

   acknowledged

   on Feb 15, 2020
2. Byron commented on Feb 15, 2020

   

   Byron

   on Feb 15, 2020

   Member

   More actions

   Thanks for the reminder - please refer to the linked issue for the anticipated course of action.
3. Byron commented on Apr 11, 2020

   

   Byron

   on Apr 11, 2020

   Member

   More actions

   @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.
4. dvzrv commented on Apr 11, 2020

   

   dvzrv

   on Apr 11, 2020

   Author

   More actions

   @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?
5. Byron commented on Apr 11, 2020

   

   Byron

   on Apr 11, 2020

   Member

   More actions

   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.
6. Byron commented on May 5, 2020

   

   Byron

   on May 5, 2020

   Member

   More actions

   Release 4.0.5 was created and signed with 2CF6E0B51AAF73F09B1C21174D1DA68C88710E60.
   Please feel free to close this issue when verified to be correct.
7. dvzrv commented on Mar 25, 2021

   

   dvzrv

   on Mar 25, 2021

   Author

   More actions

   4.0.6 is now also signed with 27C50E7F590947D7273A741E85194C08421980C9.

   Reacted by Sebastian Thiel
8. dvzrv

   closed this as completedon Mar 25, 2021
9. archlinux-github

   added 2 commits that reference this issue on Mar 25, 2021

   upgpkg: python-gitdb 1:4.0.6-1: Upgrade to 4.0.6.

   31f4639

   upgpkg: python-gitdb 1:4.0.6-1: Upgrade to 4.0.6.

   b7ef25f
10. Byron commented on Mar 26, 2021

    

    Byron

    on Mar 26, 2021

    Member

    More actions

    Thank you @dvzrv for staying on top of this, it's much appreciated.

Issue actions