[Pkg-gnupg-maint] Bug#611901: gnupg: Can't create lock on readonly filesystem

Mike Hommey mh at glandium.org
Mon Feb 21 16:24:09 UTC 2011

On Mon, Feb 21, 2011 at 05:10:08PM +0100, Werner Koch wrote:
> On Thu,  3 Feb 2011 14:17, mh+reportbug at glandium.org said:
> > 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
> Consider the case that the file system is mount read-only by one system
> but read-write by another one.  Ooops.

How many systems are in this case, *and* using gpg at the same time on
both systems?


More information about the Pkg-gnupg-maint mailing list