[Pkg-gnupg-maint] Bug#771976: Insists upon locking trustdb even for read-only operations

[Elliott Mitchell]

Package: gnupg
Version: 1.4.12-7+deb7u6

Hopefully the subject says it all, but for more detail:

I found this when running the command `apt-key list` on a machine where
the root filesystem is normally mounted read-only.  This results in
running gpg with "--trustdb-name", "/etc/apt//trustdb.gpg",
"--list-keys".  gpg in turn attempts to create
"/etc/apt//trustdb.gpg.lock" in order to lock the trustdb, which fails.

Seeing how --list-keys is an operation which shouldn't require writing
to anything, having it fail in this situation is bad.  I can understand
wanting to lock the trustdb to ensure no one else writes to it, but if
open() returns EROFS, that nicely satisfies the reqirement.


-- 
(\___(\___(\______          --=> 8-) EHM <=--          ______/)___/)___/)
 \BS (    |         EHeM+sigmsg at m5p.com  PGP 87145445         |    )   /
  \_CS\   |  _____  -O #include <stddisclaimer.h> O-   _____  |   /  _/
8A19\___\_|_/58D2 7E3D DDF4 7BA6 <-PGP-> 41D1 B375 37D0 8714\_|_/___/5445