Monitor libgpg-error and libgcrypt versions #3275
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rimrul
reviewed
Jun 16, 2021
Let's watch out for new libgcrypt versions, too (this component is a pretty important dependency of gnupg). Signed-off-by: Johannes Schindelin <[email protected]>
Since we're now watching out for new libgcrypt versions, let's also watch out for its dependency libgpg-error. Signed-off-by: Johannes Schindelin <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In our GitHub workflow that notifies us about new versions of important Git for Windows components, we already watch out for new GNU Privacy Guard versions. For v2.2.28, it became painfully clear, though, that this is not enough: we also have to build the GNU Privacy Guard dependencies
libgpg-errorandlibgcryptourselves. So let's watch out for new versions of those libraries, too.