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 IMO this is a problem of gnupg *not* enigmail. Enigmail exclusivly uses the gpg binary to interact with gnupg. So, in consequence you cannot blame enigmail for using standard gpg operations, like verify and decrypt, during upgrade. Thus, I tend to reassign this bug again to gnupg (I wait a bit to hear some comments on this). Further, as long as you cannot verify whether the .gnupg dir was really broken when you accidentially removed it, I think we should assume that this bug does *not* corrupt the .gnupg directory. -- 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]
