Merged
Conversation
Member
|
you have to add a validpgpkeys in the PKGBUILD containing the full key ID |
jannick0
force-pushed
the
patchutils_update-0.4.3
branch
2 times, most recently
from
1cf93d4 to
1c407ca
Compare
lazka
force-pushed
the
patchutils_update-0.4.3
branch
from
1c407ca to
b832106
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
@lazka The package cleanly compiles locally including all tests - with
--skippgpcheck. However, the CI build currently fails because of an unknown PGP signature.Is the package author's public key to be added to the PGP database? I cannot do that for CI supposedly.
NB: The added patch is PRed upstream on top of version 0.4.3, cf. twaugh/patchutils#98.