← Back to index | Original Bugzilla link

Bug 19434 – "Invalid signature" when using install.sh with no ~/.gnupg

Status: RESOLVED
Resolution: FIXED
Severity: normal
Priority: P1
Component: installer
Product: D
Version: D2
Platform: All
OS: Linux
Creation time: 2018-11-25T16:37:58Z
Last change time: 2018-11-27T10:42:45Z
Keywords: pull
Assigned to: No Owner
Creator: Vladimir Panteleev
See also: https://issues.dlang.org/show_bug.cgi?id=19100

Comments

Comment #0 by dlang-bugzilla — 2018-11-25T16:37:58Z

Using install.sh fails with the above message on my server. Un-redirecting gpg's error stream from /dev/null shows: --- gpg: Signature made Wed 07 Nov 2018 21:03:27 UTC using RSA key ID 12BB1939 gpg: failed to create temporary file '/home/user/.gnupg/.#lk0x0000555f88533ca0.k3.1azy.net.30121': No such file or directory gpg: Fatal: can't create lock for '/home/user/.gnupg/trustdb.gpg' Invalid signature https://dlang.org/install.sh.sig --- It looks like it needs ~/.gnupg to exist. Creating the directory allows the installation script to proceed.

Comment #1 by dlang-bugzilla — 2018-11-25T16:54:34Z

https://github.com/dlang/installer/pull/352

Comment #2 by github-bugzilla — 2018-11-27T10:42:45Z

Commits pushed to master at https://github.com/dlang/installer https://github.com/dlang/installer/commit/ce7949408ac279c78ac765773b25b956785c8089 script/install.sh: Initialize GPG directory before invoking it On some (older?) versions, --verify will fail if GNUPGHOME (~/.gnupg) does not exist, even with --no-default-keyring, as that's where it creates its temporary files. Fixes issue 19434. https://github.com/dlang/installer/commit/ce225047968cf9404eeafbf6f2a87975198c7483 Merge pull request #352 from CyberShadow/pull-20181125-164347 Fix Issue 19434 - "Invalid signature" when using install.sh with no ~/.gnupg