severity 310328 normal
thanks
Hi,
Unless someone can a) reproduce this and b) provide (the non-secret
parts of) the .gnupg directory and/or diagnose the actual problem,
there's nothing I can do about this and no reason for it to remain
grave.
--
James
--
To UNSUBSCRIBE, email to [EMAIL PROTE
reassign 310328 gnupg
thanks
after some thinking and a short discussion on IRC, I think it is safe to move
this back to gnupg again. enigmail only calls the /usr/bin/gpg binary and in
consequence should not be able to be responsible for a corruption of the .gnupg
directory. It is still unclear whe
also sprach Alexander Sack <[EMAIL PROTECTED]> [2005.05.23.1606 +0200]:
> upgrading the gnupg binary. If we have luck, the gpg operation
> will fail/break/segfault/stall or something and keep a tmp file
> inside the .gnupg directory.
Your definition of "luck" is completely bananas.
This would *su
martin f krafft wrote:
> also sprach Alexander Sack <[EMAIL PROTECTED]> [2005.05.23.1521 +0200]:
>
>>Hey guys, how about adding me to CC when reassigning and
>>escalating a bug to RC on my package?
>
>
> Uh, don't you get BTS mail as the maintainer?
>
I only got a Processed: message of the reas
also sprach Alexander Sack <[EMAIL PROTECTED]> [2005.05.23.1521 +0200]:
> Hey guys, how about adding me to CC when reassigning and
> escalating a bug to RC on my package?
Uh, don't you get BTS mail as the maintainer?
One thing that just occurred to me: neither thunderbird nor enigmail
were in woo
tags 310328 + unreproducible
thanks
Hey guys, how about adding me to CC when reassigning and escalating a bug to RC
on my package?
Anyway, Roberto. Please post ASAP if you can reproduce this bug somehow. I
couldn't reproduce this problem here.
IMHO, if the .gnupg dir got corrupted somehow, then
6 matches
Mail list logo
