mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

Added a comment: .gitconfig was the cause, git-remote-gcrypt probably at fault

Browse source
This commit is contained in:
anarcat 2018-05-17 20:42:37 +00:00 • committed by admin
parent 295447a406
commit 2c6c77bc16
1 changed files with 21 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

21
doc/bugs/gcrypt_repository_not_found/comment_2_bc67619191380b6cb2555998b2da9e88._comment Normal file
View file

@ -0,0 +1,21 @@
[[!comment format=mdwn
username="anarcat"
avatar="http://cdn.libravatar.org/avatar/4ad594c1e13211c1ad9edb81ce5110b7"
subject=".gitconfig was the cause, git-remote-gcrypt probably at fault"
date="2018-05-17T20:42:37Z"
content="""
I understand, thanks for the analysis!
As it turns out, the problem was that I had this block in my `~/.gitconfig`:
[push]
gpgSign = if-asked
This means that git-annex is not the component that was passing the
argument. That's why I couldn't find it anywhere in the source. git
itself was passing this along.
I would then make the argument that git-remote-gcrypt is the one that
should be more tolerant to those arguments. Should I send a pull
request for this?
"""]]