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 whether this bug is reproducible, though madduck remembers an indicident he could not investigate any further that could be similar to this one. Finally, I can't tell about the severity, so I keep it as grave.
martin f krafft wrote: > 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 *suck*. > Indeed, not all "luck" is "good luck". Sometimes "luck" just *sucks*. -- GPG messages preferred. | .''`. ** Debian GNU/Linux ** Alexander Sack | : :' : The universal [EMAIL PROTECTED] | `. `' Operating System http://www.asoftsite.org | `- http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
