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

Avoid a test suite failure when the environment does not let gpg be tested

Browse source 
Due to eg, too long a path to the agent socket, caused by running gpg in a
container where /run is not mounted, and/or some other gpg behavior like
unnecessarily making relative paths to its home directory absolute.
This commit is contained in:
Joey Hess 2020-04-28 15:47:23 -04:00
parent 24eabbbc55
commit 4a6d328ae9
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
5 changed files with 42 additions and 13 deletions
Download patch file Download diff file Expand all files Collapse all files

2
doc/bugs/tests_fail___40__gpg-agent_related__63____41___when_running_build_inside_singularity_container.mdwn
View file

@ -41,3 +41,5 @@ FWIW,
[[!meta author=yoh]]
[[!tag projects/datalad]]
> [[fixed|done]] --[[Joey]]

11
doc/bugs/tests_fail___40__gpg-agent_related__63____41___when_running_build_inside_singularity_container/comment_6_d358bf55d89f5d0609d792a26757d0f4._comment Normal file
View file

@ -0,0 +1,11 @@
[[!comment format=mdwn
username="joey"
subject="""comment 6"""
date="2020-04-28T19:29:05Z"
content="""
Hmm, it could be that /run is not mounted in the container and then gpg
falls back to putting the socket in the home directory.
Ok, I'm just going to make this test be skipped if it fails to import the
test key.
"""]]