Your message dated Tue, 17 Jul 2012 20:33:11 +0200
with message-id <[email protected]>
and subject line Bug#611901: gnupg: Can't create lock on readonly filesystem
has caused the Debian Bug report #611901,
regarding gnupg: Can't create lock on readonly filesystem
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
611901: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=611901
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: gnupg
Version: 1.4.10-4
Severity: normal

I keep some keyrings on a read-only partition, and all gpg is able to
tell me is this:
gpg: failed to create temporary file 
`/some/path/.gnupg/.#lk0x25c6960.jigen.7598': Read-only file system
gpg: fatal: can't create lock for `/some/path/.gnupg/trustdb.gpg'
secmem usage: 0/0 bytes in 0/0 blocks of pool 0/32768

Considering the filesystem is readonly there is no need for a lock file,
especially when all that is asked is --list-keys or --fingerprint.
Considering the error (EROFS) is very distinguishable from other
readonly or failure cases, gpg could detect it and still act without a
lock.

Mike

-- System Information:
Debian Release: 6.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages gnupg depends on:
ii  dpkg                    1.15.8.10        Debian package management system
ii  gpgv                    1.4.10-4         GNU privacy guard - signature veri
ii  install-info            4.13a.dfsg.1-6   Manage installed documentation in 
ii  libbz2-1.0              1.0.5-6          high-quality block-sorting file co
ii  libc6                   2.11.2-10        Embedded GNU C Library: Shared lib
ii  libreadline6            6.1-3            GNU readline and history libraries
ii  libusb-0.1-4            2:0.1.12-16      userspace USB programming library
ii  zlib1g                  1:1.2.3.4.dfsg-3 compression library - runtime

Versions of packages gnupg recommends:
pn  gnupg-curl                    <none>     (no description available)
ii  libldap-2.4-2                 2.4.23-7   OpenLDAP libraries

Versions of packages gnupg suggests:
ii  eog                          2.30.2-1    Eye of GNOME graphics viewer progr
pn  gnupg-doc                    <none>      (no description available)
ii  imagemagick                  8:6.6.0.4-3 image manipulation programs
ii  libpcsclite1                 1.5.5-4     Middleware to access a smart card 

-- no debconf information



--- End Message ---
--- Begin Message ---
Hi,

I'm going to close this report. Upstream made clear, that the behavior
won't change. Further there is the switch --lock-never, which should fix
the issue for your use case.

Please feel free to comment my decision and/or reopen your report, if
you disagree with it.

Regards, Daniel

--- End Message ---

Reply via email to