FS#47277 - [gnupg] addgnupghome is broken

Attached to Project: Arch Linux
Opened by Ian Kelling (IanKelling) - Sunday, 06 December 2015, 00:56 GMT
Last edited by Gaetan Bisson (vesath) - Sunday, 06 December 2015, 07:57 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Gaetan Bisson (vesath)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:
addgnupghome is broken due to expecting file in /etc/skel/.gnupg,
which doesn't exist.

Additional info:
* package version(s)
2.1.9-1


Steps to reproduce:
Fresh arch install,
$ addgnupghome $USER
This task depends upon

Closed by  Gaetan Bisson (vesath)
Sunday, 06 December 2015, 07:57 GMT
Reason for closing:  Not a bug
Comment by Ian Kelling (IanKelling) - Sunday, 06 December 2015, 01:02 GMT
Oh, and just doing a normal gpg operation seems to accomplish what addgnupghome does for the current user.
eg. gpg --search --batch any_argument
Comment by Gaetan Bisson (vesath) - Sunday, 06 December 2015, 05:38 GMT
Indeed. GnuPG's defaults are good enough that we do not need to put anything under /etc/skel/.gnupg/. I think we should just remove addgnupghome or simply not do anything.
Comment by Ian Kelling (IanKelling) - Sunday, 06 December 2015, 07:38 GMT
Ya, I agree. Remove it, or just document it in the wiki, or replace it with a shell script that explains it's not enabled on arch. I found gpg -k to be a faster even less effectfull command to generate the ~/.gnupg.
Comment by Gaetan Bisson (vesath) - Sunday, 06 December 2015, 07:57 GMT
Actually some sysadmins might populate /etc/skel/.gnupg and make use of addgnupghome; it's just that the official package does not. Since as you point out everything works well out of the box when using gpg for the first time, I really think we do not need to do anything regarding this.

Loading...