projects/repronim/bugs-done/gpgconf: invalid option "--kill" (gpg 2.0.22) yohhttp://git-annex.branchable.com/projects/repronim/bugs-done/gpgconf__58___invalid_option___34__--kill__34_____40__gpg_2.0.22__41___/git-annexikiwiki2023-01-05T17:30:31Zcomment 1http://git-annex.branchable.com/projects/repronim/bugs-done/gpgconf__58___invalid_option___34__--kill__34_____40__gpg_2.0.22__41___/comment_1_0351276d5eeb5d8af0cf0e72c3a213fd/joey2023-01-05T17:30:31Z2021-08-24T15:54:15Z
<p>It already ignores nonzero exit status of that command, since
old gpg's don't support it.</p>
<p>So, it must not really be the <code>gpgconf --kill</code> that is causing the test
failure.</p>
<p>Please post the actual test failure message.</p>
more infohttp://git-annex.branchable.com/projects/repronim/bugs-done/gpgconf__58___invalid_option___34__--kill__34_____40__gpg_2.0.22__41___/comment_2_a8565fb1657318092a22e8ed18ae6cbc/yarikoptic2023-01-05T17:30:31Z2021-08-24T16:35:26Z
<p>full log is available <a href="https://git-annex.branchable.com/bugs/__34__357_out_of_984_tests_failed__34___on_NFS_lustre_mount/">for another issue</a> <a href="http://www.onerussian.com/tmp/git-annex-noretry+pidlock1-1.log">http://www.onerussian.com/tmp/git-annex-noretry+pidlock1-1.log</a> which shows the same error as well.</p>
<p>FWIW</p>
<pre><code>[d31548v@discovery7 ~]$ /usr/bin/gpgconf --kill
gpgconf: invalid option "--kill"
[d31548v@discovery7 ~]$ echo $?
2
</code></pre>
comment 3http://git-annex.branchable.com/projects/repronim/bugs-done/gpgconf__58___invalid_option___34__--kill__34_____40__gpg_2.0.22__41___/comment_3_d3a478e3f7da91ab14c9b1e24d3e07d6/joey2023-01-05T17:30:31Z2021-10-12T16:42:02Z
<p>From the log:</p>
<pre><code> crypto: gpgconf: invalid option "--kill"
gpgconf: invalid option "--kill"
FAIL (22.13s)
./Test/Framework.hs:57:
copy --to encrypted remote failed (transcript follows)
copy foo (to foo...)
gpg: can't connect to the agent: Invalid value passed to IPC
gpg: problem with the agent: No agent running
</code></pre>
<p>That is not really be a problem with gpgconf --kill, but a problem
talking to gpg-agent.</p>
<p>The same crypto test fails a couple more times in that log, like this:</p>
<pre><code> crypto: gpgconf: invalid option "--kill"
gpgconf: invalid option "--kill"
FAIL (12.00s)
./Test/Framework.hs:57:
get of file failed (transcript follows)
get foo (not available)
No other repository is known to contain the file.
failed
get: 1 failed
</code></pre>
<p>That is also not a problem with gpgconf --kill, it's actually due to an
earlier test failure, unrelated to this. That earlier failure was
the one <a href="https://git-annex.branchable.com/bugs/__34__357_out_of_984_tests_failed__34___on_NFS_lustre_mount/">the other issue</a>
was about, which has since been fixed. So we can ignore these I think,
leaving only the one above as an unexplained failure.</p>
<p>"gpg: can't connect to the agent: Invalid value passed to IPC" could
be some kind of gpg bug. I found some other instances of gpg failing that way.
One involved using --homedir (similar to the test suite's
use of GNUPGHOME) but on windows.
<a href="https://lists.gnupg.org/pipermail/gnupg-users/2016-October/056817.html">https://lists.gnupg.org/pipermail/gnupg-users/2016-October/056817.html</a>
And here's another one, in WSL when apt runs
gpg. <a href="https://github.com/microsoft/WSL/issues/5125">https://github.com/microsoft/WSL/issues/5125</a></p>
<p>Perhaps this is a problem with the location of the gpg agent socket in the
filesystem that git-annex test is running in. That somehow messes up not
creation of that socket, but later use of it. It seems that the earlier
self-test of the test harness did not trigger the problem though, which is
odd because it sets up a gpg private key and I'd think would use the agent
too.</p>
<p>In <a href="http://source.git-annex.branchable.com/?p=source.git;a=commitdiff;h=b426ff682570d8600dc8025bbcd20aa95819a7e4">b426ff682570d8600dc8025bbcd20aa95819a7e4</a> I considered
putting the gpg directory inside the system temp dir, which would perhaps
avoid the problem here. I've made that change.</p>
<p>Please test a fresh build on this system again, if you can..</p>
comment 4http://git-annex.branchable.com/projects/repronim/bugs-done/gpgconf__58___invalid_option___34__--kill__34_____40__gpg_2.0.22__41___/comment_4_9add6c8e1d5b722eaeb2e5a0fe67cd32/joey2023-01-05T17:30:31Z2022-06-02T16:23:44Z
Any chance you can try to reproduce this with a recent build of git-annex?
still reports about invalid option but doesn't failhttp://git-annex.branchable.com/projects/repronim/bugs-done/gpgconf__58___invalid_option___34__--kill__34_____40__gpg_2.0.22__41___/comment_5_e3a79f9480a7123feb924f3c1e72ce62/yarikoptic2023-01-05T17:30:31Z2022-06-03T01:36:38Z
<p>so I should try with outdated gpgconf on some older CentOS? ..already done - we do run annex tests daily on ndoli (part of discovery) now and apparently: tests passed, but it did have those reports</p>
<pre><code>(git)smaug:/mnt/datasets/datalad/ci/git-annex-ci-client-jobs/builds/2022/06[master]git
$> tail result-ndoli-715/handle-result.yaml-154-7a381a8a-success/result-ndoli-715/git-annex-tmp.rc
0
$> tail result-ndoli-715/handle-result.yaml-154-7a381a8a-success/result-ndoli-715/git-annex-tmp.log
gpgconf: invalid option "--kill"
gpgconf: invalid option "--kill"
gpgconf: invalid option "--kill"
gpgconf: invalid option "--kill"
gpgconf: invalid option "--kill"
+ echo 'Elapsed time: 3278 seconds'
Elapsed time: 3278 seconds
+ cd /dartfs/rc/lab/D/DBIC/DBIC/archive/tmp
+ chmod -R +w 715
+ rm -rf 715
</code></pre>
comment 5http://git-annex.branchable.com/projects/repronim/bugs-done/gpgconf__58___invalid_option___34__--kill__34_____40__gpg_2.0.22__41___/comment_5_b411b96c73bba30557c2f3aa9d6077e7/joey2023-01-05T17:30:31Z2022-06-03T18:00:16Z
<p>Ok, that is behaving as expected then, it ignores failure to support older
gpgs. Going to close this.</p>