[Pkg-gnupg-maint] Bug#611901: marked as done (gnupg: Can't create lock on readonly filesystem)

Tue Jul 17 18:45:03 UTC 2012

Your message dated Tue, 17 Jul 2012 20:33:11 +0200
with message-id <1342549991.6913.9.camel at haktar.debian.wgdd.de>
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 owner at bugs.debian.org
immediately.)

-- 
611901: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=611901
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: Mike Hommey <mh+reportbug at glandium.org>
Subject: gnupg: Can't create lock on readonly filesystem
Date: Thu, 03 Feb 2011 14:17:00 +0100
Size: 4002
URL: <http://lists.alioth.debian.org/pipermail/pkg-gnupg-maint/attachments/20120717/945ff138/attachment.mht>
-------------- next part --------------
An embedded message was scrubbed...
From: Daniel Leidert <daniel.leidert at wgdd.de>
Subject: Bug#611901: gnupg: Can't create lock on readonly filesystem
Date: Tue, 17 Jul 2012 20:33:11 +0200
Size: 1857
URL: <http://lists.alioth.debian.org/pipermail/pkg-gnupg-maint/attachments/20120717/945ff138/attachment-0001.mht>