Your message dated Thu, 10 Jul 2008 10:42:28 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Re: Hurd: gnupg 1.4.2 error on start
has caused the Debian Bug report #349241,
regarding Hurd: gnupg 1.4.2 error on start
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.)
--
349241: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=349241
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: gnupg
Version: 1.4.2 (GNU/Hurd)
When starting gnupg without parameters,
the programs terminates with the error message "gpg: can't lock memory:
(os/kern) failure".
--- End Message ---
--- Begin Message ---
Hello,
Thijs Kinkhorst, le Thu 10 Jul 2008 11:24:15 +0200, a écrit :
> > When starting gnupg without parameters,
> >
> > the programs terminates with the error message "gpg: can't lock memory:
> > (os/kern) failure".
>
> Since this has been reported quite some time ago, I would appreciate if a
> hurd user could verify the presence of this bug in current combinations of
> gnupg (1.4.9) and current hurd kernels
Oops, sorry I didn't realize there was a debian bug about that. Fixed
since quite some time in glibc.
Thanks for the reminder,
Samuel
--- End Message ---
