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.

Sign up for GitHub

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

Jump to bottom

Address the GnuPG mess #9

Closed

dscho opened this issue Dec 21, 2022 · 2 comments

Member

dscho commented Dec 21, 2022

Neither https://gnupg.org/news.html nor https://gnupg.org/index.html nor https://github.com/gpg/gnupg/releases.atom seem to have any reliable information about what version of GNU Privacy Guard is the latest.

Let's monitor https://git.gnupg.org/cgi-bin/gitweb.cgi?p=libgpg-error.git;a=tags, https://git.gnupg.org/cgi-bin/gitweb.cgi?p=libgcrypt.git;a=tags and https://git.gnupg.org/cgi-bin/gitweb.cgi?p=gnupg.git;a=tags, (which do not provide any RSS/Atom feed because... GitWeb) and then decide on a case by case basis whether the newest tag actually corresponds to any stable release.

dscho mentioned this issue

mingw-w64-curl: update to 7.87.0 git-for-windows/MINGW-packages#63

Merged

Member Author

dscho commented Dec 21, 2022

Once we do that, we will want to remove gpg and friends from the monitor-components workflow.

Member Author

dscho commented Jan 10, 2025

It does seem as if https://github.com/gpg/gnupg/releases.atom (which we use in monitor-components) has gotten a bit more reliable. At least v2.5.3 (which has been released 24h ago as of time of writing) has been picked up in git-for-windows/git#5355.

So we happily do not need to invest any more energy into this here ticket.

dscho closed this as not planned

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment