The following message is a courtesy copy of an article
that has been posted to comp.emacs.xemacs as well.
This is a bug, probably of a known species. Please followup to xemacs-beta.
>>>> "BAW" == Barry A Warsaw
<barry(a)zope.com> writes:
BAW> However, when configured with --with-mule, after entering the
BAW> encryption key, the decrypt fails and I'm left with this in
BAW> the buffer:
gpg: fatal: zlib inflate problem: incorrect data check^Msecmem usage: 2272/2432 bytes in
6/7 blocks of pool 2432/16384
(single character ^M replaced for transport)
BAW> Anybody have any ideas? Known bug?
My guess is that the GPG handler code is not being careful enough
about reading/writing the encrypted files as binary. That stuff
changed a couple of years ago.
What's your handler for encrypted files? mailcrypt, crypt++,
jka-compr (note, I know nothing about those packages, just guessing)?
--
Institute of Policy and Planning Sciences
http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Don't ask how you can "do" free software business;
ask what your business can "do for" free software.