-
-
Notifications
You must be signed in to change notification settings - Fork 80
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
gpg: signing failed: Inappropriate ioctl for device #201
Comments
Hi @craftyphotons, this is because you |
Unfortunately it's still occurring even with that step removed: https://github.com/protomy/protomy/runs/690511183 |
Ok how do you export your GPG key? Do you follow the Prerequesites? |
Yep! I even re-followed everything just now to be sure, and reuploaded secrets with the keys https://github.com/protomy/protomy/runs/690545899 I included an additional step as you show in the documentation to echo out the GPG key/user information to verify that the gpg import action is working appropriately. The only difference I can ascertain at this point is that your build from a couple days ago ran against version 20200430.1 of I'm also getting the error on |
I re-run our CI workflow and everything works fine. |
Thanks @crazy-max — definitely must be something with my key then. I'll dig into it from my side some more and see if I can narrow things down more. |
@craftyphotons Can you test with |
@craftyphotons Ok thanks for your feedback. I've made some new changes, can you try it? (with |
Ok this is what I tought. It looks like your GPG key requires a special input which is not allowed in batch mode. Could you give me more information on how you created the key? In particular the version of GnuPG. Can you also try creating a key following those steps of GitHub. |
I think I just came to the same conclusion myself by creating a new key here on my laptop, which worked. However now the mystery deepens, as the non-working key was created on a different machine with the same procedure and the same Here's the
Both machines are also running gpg 2.2.17. In any case though, sounds like I'm probably an odd edge case here... I'll keep trying to determine how the key on the other machine might be different though and let you know if I find anything. Thanks a lot for spending the time to help me track this down! |
Thanks, don't hesitate to come back to me, I close this issue in the meantime. |
I'm throwing a breadcrumb here for future searchers... a key generated with GPG2 gave me the same error. Using a key generated by GPG1 worked just fine. actions/runner#241 (comment) was helpful in figuring this out. |
@crazy-max I have the same issue with an RSA 4096 bit signing key generated with |
In attempting to use the GPG signing functionality as documented with the use of crazy-max/ghaction-import-gpg I can't seem to find a way around the following error when GoReleaser gets to the signing pipe:
(See here for the full action log)
I've been comparing back and forth between my own GitHub workflow configuration and the one in use by this repository's own CI workflow, but can't seem to spot any differences between the two that could lead to this error, which has been confounding given that the CI workflow for goreleaser/gorelease-action itself is passing, with virtually the same configuration other than the key itself.
Seems as though there's been a similar issue referenced elsewhere in actions/runner#241 (comment) but again that would be confusing given that the workflow is passing in the GoReleaser action's own tests 😄
The text was updated successfully, but these errors were encountered: