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 reassignment and grave severity. The rest of the thread was not delivered to me.
> One thing that just occurred to me: neither thunderbird nor enigmail > were in woody, and we are talking about a corruption-on-upgrade > here. > > I really don't think this bug is RC. When GPG gets updated to 1.4.1, > Thunderbird cannot be running yet. So there is no corruption. This is really a good point. So this is no RC bug for enigmail. But *if* this is a bug of gnupg it would still be valid and *grave*. > > FWIW, I cannot reproduce the bug: > > - installed gnupg/woody > - installed thunderbird+enigmail from sarge > - started thunderbird > - configured enigmail, tested it > - upgraded gnupg while running thunderbird > - verified operation of thunderbird > I would suggest to verify this with gpg only. Maybe the problem can be isolated and reproduced by invoking a long write operation on the key-store while 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. -- 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]
