Skip to content
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.7: signature key-id 763629FEC8788FC35128B5F6EE029D1E5EB40300 not found #980

Open
dvzrv opened this issue Feb 8, 2020 · 2 comments
Open
Assignees
Labels

Comments

@dvzrv
Copy link

@dvzrv dvzrv commented Feb 8, 2020

Hi!

I'm currently trying to build 3.0.7 as a package for Arch Linux. It seems a new key was used for signing this release, but this is not mentioned in the release notes, nor can the key be found on any keyserver yet.

Please sign the new key 763629FEC8788FC35128B5F6EE029D1E5EB40300 with the old key 2CF6E0B51AAF73F09B1C21174D1DA68C88710E60 and upload the new key (plus signature) to the keyservers, so a chain of trust can be established.
In the current situation I feel not comfortable packaging this version.

In case you want to make sure that the key ends up on (all) key servers, you can use this script:
https://paste.xinu.at/axX1B9w/

@Harmon758

This comment has been minimized.

Copy link
Member

@Harmon758 Harmon758 commented Feb 8, 2020

According to 6b8e7b7 and 7b74a5b, this was due to @Byron's hardware situation.

@Byron

This comment has been minimized.

Copy link
Member

@Byron Byron commented Feb 12, 2020

Indeed! I will fix it as soon as I can, which is when the travel ban in China is lifted.

wip-sync pushed a commit to NetBSD/pkgsrc-wip that referenced this issue Mar 7, 2020
3.1.0
=====

* Switched back to using gitdb package as requirement
  (`gitdb#59 <https://github.com/gitpython-developers/gitdb/issues/59>`_)

3.0.9
=====

* Restricted GitDB (gitdb2) version requirement to < 4
* Removed old nose library from test requirements

Bugfixes
--------

* Changed to use UTF-8 instead of default encoding when getting information about a symbolic reference
  (`#774 <https://github.com/gitpython-developers/GitPython/issues/774>`_)
* Fixed decoding of tag object message so as to replace invalid bytes
  (`#943 <https://github.com/gitpython-developers/GitPython/issues/943>`_)

3.0.8
=====

* Added support for Python 3.8
* Bumped GitDB (gitdb2) version requirement to > 3

Bugfixes
--------

* Fixed Repo.__repr__ when subclassed
  (`#968 <https://github.com/gitpython-developers/GitPython/pull/968>`_)
* Removed compatibility shims for Python < 3.4 and old mock library
* Replaced usage of deprecated unittest aliases and Logger.warn
* Removed old, no longer used assert methods
* Replaced usage of nose assert methods with unittest

3.0.7
=====

Properly signed re-release of v3.0.6 with new signature
(See `#980 <https://github.com/gitpython-developers/GitPython/issues/980>`_)

3.0.6
=====

| Note: There was an issue that caused this version to be released to PyPI without a signature
| See the changelog for v3.0.7 and `#980 <https://github.com/gitpython-developers/GitPython/issues/980>`_

Bugfixes
--------

* Fixed warning for usage of environment variables for paths containing ``$`` or ``%``
  (`#832 <https://github.com/gitpython-developers/GitPython/issues/832>`_,
  `#961 <https://github.com/gitpython-developers/GitPython/pull/961>`_)
* Added support for parsing Git internal date format (@<unix timestamp> <timezone offset>)
  (`#965 <https://github.com/gitpython-developers/GitPython/pull/965>`_)
* Removed Python 2 and < 3.3 compatibility shims
  (`#979 <https://github.com/gitpython-developers/GitPython/pull/965>`_)
* Fixed GitDB (gitdb2) requirement version specifier formatting in requirements.txt
  (`#979 <https://github.com/gitpython-developers/GitPython/pull/965>`_)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants
You can’t perform that action at this time.