http://bugs.winehq.org/show_bug.cgi?id=31261
--- Comment #7 from Qian Hong fracting@gmail.com 2012-07-20 14:06:41 CDT --- (In reply to comment #6)
Hm... I could report this as a bug on libgcrypt11 (at least on the Sid version), but to be honest, I have absolutely no idea how to do that.
Hi, I think you can try to build the upstream version(s) of libgcrypt11 from ftp://ftp.gnupg.org/gcrypt/libgcrypt/ , confirm that if the bug can reproduce with the same version/latest version from upstream.
If you can reproduce, then might be it is a good idea to ask on gnupg-users before reporting a bug http://www.gnupg.org/documentation/mailing-lists.en.html
If you can't reproduce with the upstream version but can reproduce with the Debian Sid version, then report it to the Debian maintainer of libgcrypt11.
I'm not familiar with libgcrypt11 so I might be misleading you, hopefully the guys in gnupg-users could help you.
Good luck ;-)