Bug 241659

Summary:	gpgv: fatal: /root/.gnupg: can't create directory: File exists
Product:	Red Hat Enterprise Linux 4	Reporter:	Olaf <o.zaplinski>
Component:	gnupg	Assignee:	Tomas Mraz <tmraz>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.0
Target Milestone:	---
Target Release:	---
Hardware:	ia64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-06-20 13:25:52 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Olaf 2007-05-29 12:56:29 UTC

[root@r2d2-new src]# gpgv linux-2.6.21.tar.bz2.sign linux-2.6.21.tar.bz2
gpgv: /root/.gnupg: directory created
gpgv: new configuration file `/root/.gnupg/gpg.conf' created
gpgv: WARNING: options in `/root/.gnupg/gpg.conf' are not yet active during this run
gpgv: keyblock resource `/root/.gnupg/trustedkeys.gpg': general error
gpgv: Signature made Thu Apr 26 07:13:23 2007 CEST using DSA key ID 517D0F0E
gpgv: Can't check signature: public key not found
[root@r2d2-new src]# gpg --recv-keys 517D0F0E
gpg: keyring `/root/.gnupg/secring.gpg' created
gpg: keyring `/root/.gnupg/pubring.gpg' created
gpg: /root/.gnupg/trustdb.gpg: trustdb created
gpg: key 517D0F0E: public key "Linux Kernel Archives Verification Key
<ftpadmin>" imported
gpg: Total number processed: 1
gpg:               imported: 1
[root@r2d2-new src]# gpgv linux-2.6.21.tar.bz2.sign linux-2.6.21.tar.bz2
gpgv: fatal: /root/.gnupg: can't create directory: File exists
secmem usage: 0/0 bytes in 0/0 blocks of pool 0/0
[root@r2d2-new src]#

Comment 1 Jiri Pallich 2012-06-20 13:25:52 UTC

Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life. 
Please See https://access.redhat.com/support/policy/updates/errata/

If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue.