-
Notifications
You must be signed in to change notification settings - Fork 13.1k
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
[stable] Backport fixes to build-manifest #56960
Conversation
This builder is not really the correct place to put this, but it definitely has the time budget and checking this tool builds on just one platform is more than sufficient.
GPG versions 2.x+ require that --batch be passed if --passphrase-fd is to be accepted.
Apparently this changed with gpg2 or... something like that?
@bors r+ p=1000 |
📌 Commit 0a3f194 has been approved by |
⌛ Testing commit 0a3f194 with merge a1d478bb0641cc3750b78043b31bbdb398f22dc0... |
💔 Test failed - status-travis |
Your PR failed on Travis (raw log). Through arcane magic we have determined that the following fragments from the build log may contain information about the problem. Click to expand the log.
I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
@bors retry please |
[stable] Backport fixes to build-manifest Backports the following changes to stable: * #56703: Fix build of the `build-manifest` tool *(partial, just added last commit)* * #56783: Add `--pinentry-mode=loopback` to deployment script * #56735: Fix gpg signing in manifest builder r? @ghost cc @Mark-Simulacrum @alexcrichton
☀️ Test successful - status-appveyor, status-travis |
Backports the following changes to stable:
build-manifest
tool #56703: Fix build of thebuild-manifest
tool (partial, just added last commit)--pinentry-mode=loopback
to deployment script #56783: Add--pinentry-mode=loopback
to deployment scriptr? @ghost
cc @Mark-Simulacrum @alexcrichton