blocks|key|118152|text|解决了它。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|118153|所以当GitHub桌面抱怨找不到gpg+(我是通过自制软件安装的)时，我想应该有一种方法来告诉git+gpg的确切路径，结果是：|118154|118155|+gpg.program在制作或验证PGP签名时使用此自定义程序，而不是在$PATH上找到的"gpg“。该程序必须支持与GPG相同的命令行界面，即，为了验证一个分离的签名，运行"gpg+--verify+$file+-+<$+signature“，程序期望通过代码0退出表示一个好的签名，并生成一个装甲ASCII码的分离签名，"gpg+-bsau+$key”的标准输入输入要签名的内容，程序期望将结果发送到它的标准输出。https://git-scm.com/docs/git-config|blockquote|offset|length|118156|118157|118158|所以运行以下命令就解决了这个问题：|118159|git+config+--global+gpg.program+"$(which+gpg)"|code-block|syntax|javascript|118160|GitHub回复我说，一些用户还需要使用：|118161|echo+"no-tty"+>>+~/.gnupg/gpg.conf|118162|entityMap|0|LINK|mutability|MUTABLE|url|https://git-scm.com/docs/git-config^0|0|0|0|5U|Z|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|14|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|15|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|16|8|@]|9|@]|A|$]]|$1|E|3|F|5|G|7|17|8|@]|9|@$H|18|I|19|1|1A]]|A|$]]|$1|J|3|-4|5|6|7|1B|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|1C|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|1D|8|@]|9|@]|A|$]]|$1|N|3|O|5|P|7|1E|8|@]|9|@]|A|$Q|R]]|$1|S|3|T|5|6|7|1F|8|@]|9|@]|A|$]]|$1|U|3|V|5|P|7|1G|8|@]|9|@]|A|$Q|R]]|$1|W|3|-4|5|6|7|1H|8|@]|9|@]|A|$]]]|X|$Y|$5|Z|10|11|A|$12|13]]]]

Solved it.
So as GitHub Desktop was complaining about not being able to find gpg (I had installed it via homebrew), I figured there should be a way to tell git the exact path of gpg, turns out there is:
<blockquote>
gpg.program
Use this custom program instead of &quot;gpg&quot; found on $PATH when making or verifying a PGP signature. The program must support the same command-line interface as GPG, namely, to verify a detached signature, &quot;gpg --verify $file - &lt;$signature&quot; is run, and the program is expected to signal a good signature by exiting with code 0, and to generate an ASCII-armored detached signature, the standard input of &quot;gpg -bsau $key&quot; is fed with the contents to be signed, and the program is expected to send the result to its standard output.
<a href="https://git-scm.com/docs/git-config" rel="noreferrer">https://git-scm.com/docs/git-config</a>
</blockquote>
So running the following solved the problem:
<pre class="lang-sh prettyprint-override"><code>git config --global gpg.program &quot;$(which gpg)&quot;
</code></pre>
GitHub got back to me and said that some users also need to use:
<pre class="lang-sh prettyprint-override"><code>echo &quot;no-tty&quot; &gt;&gt; ~/.gnupg/gpg.conf
</code></pre>

blocks|key|115225|text|它与commit+signing+(https://help.github.com/en/articles/signing-commits)有关。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|115226|如果你使用Github+Desktop+(它不支持提交签名，就像上面链接的文章开头突出显示的那样)，或者如果你不需要提交签名(或者甚至不知道它是什么)，你可以做的一件事是通过运行像git+config+--global+commit.gpgsign+false这样的命令来禁用gpg提交签名，或者手动编辑你的.git/config文件：|CODE|115227|[commit]
++#+https://help.github.com/articles/signing-commits-using-gpg/
++gpgsign+=+false|code-block|syntax|javascript|115228|希望这能帮助到别人。|115229|entityMap|0|LINK|mutability|MUTABLE|url|https://help.github.com/en/articles/signing-commits^0|2|E|I|1F|0|0|2I|14|4A|B|3U|7|0|0|0^^$0|@$1|2|3|4|5|6|7|X|8|@$9|Y|A|Z|B|C]]|D|@$9|10|A|11|1|12]]|E|$]]|$1|F|3|G|5|6|7|13|8|@$9|14|A|15|B|H]|$9|16|A|17|B|H]|$9|18|A|19|B|C]]|D|@]|E|$]]|$1|I|3|J|5|K|7|1A|8|@]|D|@]|E|$L|M]]|$1|N|3|O|5|6|7|1B|8|@]|D|@]|E|$]]|$1|P|3|-4|5|6|7|1C|8|@]|D|@]|E|$]]]|Q|$R|$5|S|T|U|E|$V|W]]]]

It has something to do with commit signing (<a href="https://help.github.com/en/articles/signing-commits" rel="noreferrer">https://help.github.com/en/articles/signing-commits</a>).

In case you use Github Desktop (which doesn't support commit signing as highlighted right at the beginning of the article linked above) or if you don't need commit signing (or don't even know what it is), one thing you can do is to disable gpg commit signing by running a command like <code>git config --global commit.gpgsign false</code> or edit your <code>.git/config</code> file manually:

<pre><code>[commit]
 # https://help.github.com/articles/signing-commits-using-gpg/
 gpgsign = false
</code></pre>

Hope it helps someone.

blocks|key|116055|text|VSCODE用户的解决方案：|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|116056|在设置下搜索GPG，然后取消选中：|116057|​|116058|📷|atomic|116059|116060|现在，为什么要取消选中它？|116061|只有在使用Gnu+Privacy+Guard时才需要此扩展。如果你不知道它是什么，那么你绝对不需要担心。|116062|但是，如果您想知道发生了什么，请查看：|116063|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/5518ec9eac24a5bae02b94df9f381e56.png|imageAlt^0|9|5|0|0|0|0|1|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|12|8|@$9|13|A|14|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|15|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|16|8|@]|D|@]|E|$]]|$1|J|3|K|5|L|7|17|8|@]|D|@$9|18|A|19|1|1A]]|E|$]]|$1|M|3|I|5|6|7|1B|8|@]|D|@]|E|$]]|$1|N|3|O|5|6|7|1C|8|@]|D|@]|E|$]]|$1|P|3|Q|5|6|7|1D|8|@]|D|@]|E|$]]|$1|R|3|S|5|6|7|1E|8|@]|D|@]|E|$]]|$1|T|3|-4|5|6|7|1F|8|@]|D|@]|E|$]]]|U|$V|$5|W|X|Y|E|$Z|10|11|-4]]]]

SOLUTION FOR VSCODE USERS:
Under settings search for GPG and uncheck it:
<a href="https://i.stack.imgur.com/ZadUT.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/ZadUT.png" alt="VS CODE IMAGE" /></a>
Now, why would you uncheck it?
You only need this extension if using the Gnu Privacy Guard. If you don't know what it is, then you definitely do not need to worry.
However, just in case you want to know what is going on check out:
<a href="https://www.gnupg.org/" rel="nofollow noreferrer">https://www.gnupg.org/</a>

blocks|key|116065|text|适用于已安装的Mac和gpg2|type|unstyled|depth|inlineStyleRanges|entityRanges|data|116066|git+config+--global+gpg.program+$(which+gpg2)|code-block|syntax|javascript|116067|这对我很有效。|116068|在上面的命令之后，你的.gitconfig应该如下所示|116069|[user]
++++email+=+yogesh.jadhav@xxx.com.au
++++name+=+jadhavy
++++signingkey+=+xxx
[credential]
++++helper+=+osxkeychain
[gpg]
++++program+=+/usr/local/MacGPG2/bin/gpg2
[commit]
++++gpgsign+=+true
[core]
++++autocrlf+=+input|116070|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|R|8|@]|9|@]|A|$]]|$1|K|3|L|5|D|7|S|8|@]|9|@]|A|$E|F]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

For Mac and gpg2 installed
<pre><code>git config --global gpg.program $(which gpg2)
</code></pre>
This works for me.
And after above command, your .gitconfig should look like below
<pre><code>[user]
 email = yogesh.jadhav@xxx.com.au
 name = jadhavy
 signingkey = xxx
[credential]
 helper = osxkeychain
[gpg]
 program = /usr/local/MacGPG2/bin/gpg2
[commit]
 gpgsign = true
[core]
 autocrlf = input
</code></pre>

Trying to commit my changes by using GitHub Desktop and getting this:
<a href="https://i.stack.imgur.com/yYem2.png" rel="noreferrer"><img src="https://i.stack.imgur.com/yYem2.png" alt="enter image description here" /></a>
<blockquote>
error: cannot run gpg: No such file or directory
error: could not run gpg.
fatal: failed to write commit object
(128)
</blockquote>
Firstly that not worked for terminal too and i create gpg-key and plugged in to my GitHub Account
Now it's working well in Terminal but Desktop version still not working.
<blockquote>
In Oficial doccumentation for GitHub Desktop i found some notation:
Note: GitHub Desktop does not support GPG signing.
</blockquote>

Git Hub Desktop on Mac, error: cannot run gpg: No such file or directory

尝试通过使用GitHub桌面提交我的更改，并获得以下结果：​​错误:无法运行gpg:没有这样的文件或目录错误:无法运行gpg。致命:无法写入提交对象(128)首先，这不适用于终端，我创建了gpg-key，并插入到我的GitHub帐户，现在它在终端上工作得很好，但桌面版仍然不能工作。在GitHub桌面的原始文档中，我发现...

问Mac上的Git Hub Desktop，错误:无法运行gpg:没有这样的文件或目录
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Mac上的Git Hub Desktop，错误:无法运行gpg:没有这样的文件或目录EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Mac上的Git Hub Desktop，错误:无法运行gpg:没有这样的文件或目录
EN