Re: New mutt GPGME error

2017-06-02 Thread Ben McGinnes
On Fri, Jun 02, 2017 at 09:10:01AM -0400, Mark H. Wood wrote: > > I'm another Gentoo user. I unmasked Mutt 1.8.2-r2 to see if it > would help a problem I was having with some S/MIME signed messages, > and that pulled in gpgme 1.8.0-r3. I have fewer problems now with > S/MIME and no new issues. E

Re: New mutt GPGME error

2017-06-02 Thread Mark H. Wood
I'm another Gentoo user. I unmasked Mutt 1.8.2-r2 to see if it would help a problem I was having with some S/MIME signed messages, and that pulled in gpgme 1.8.0-r3. I have fewer problems now with S/MIME and no new issues. -- Mark H. Wood Lead Technology Analyst University Library Indiana Univ

Re: New mutt GPGME error

2017-06-01 Thread Ben McGinnes
On Thu, Jun 01, 2017 at 02:58:56PM -0700, Ian Zimmerman wrote: > On 2017-06-02 04:51, Ben McGinnes wrote: > >> There shouldn't be. While new functions are periodically added to >> GPGME as features are added to GPG and its related projects, >> efforts are made not to change existing functions. >

Re: New mutt GPGME error

2017-06-01 Thread Ian Zimmerman
On 2017-06-02 04:51, Ben McGinnes wrote: > There shouldn't be. While new functions are periodically added to > GPGME as features are added to GPG and its related projects, efforts > are made not to change existing functions. I think I found it: https://bugs.gentoo.org/show_bug.cgi?id=600600 Mo

Re: New mutt GPGME error

2017-06-01 Thread Ben McGinnes
On Thu, Jun 01, 2017 at 12:28:07PM -0700, Kevin J. McCarthy wrote: > On Thu, Jun 01, 2017 at 11:09:40AM -0700, Ian Zimmerman wrote: >> Is there a good reason for this restriction, i.e. a known >> incompatibility with gpgme-1.8 and later? > > I'm compiling against gpgme 1.8.0, and am not aware of a

Re: New mutt GPGME error

2017-06-01 Thread Kevin J. McCarthy
On Thu, Jun 01, 2017 at 11:09:40AM -0700, Ian Zimmerman wrote: > Is there a good reason for this restriction, i.e. a known > incompatibility with gpgme-1.8 and later? I'm compiling against gpgme 1.8.0, and am not aware of any issues. I haven't tested against 1.9.0 yet, but haven't received any re

Re: New mutt GPGME error

2017-06-01 Thread Ben McGinnes
On Thu, Jun 01, 2017 at 11:09:40AM -0700, Ian Zimmerman wrote: > > Somewhat related: > > The latest (in fact, the only) mutt version in gentoo stable is > 1.5.24. When I roll my weekly gentoo upgrade I am warned that a new > version of gpgme, namely 1.8.0, is available, but is not being > instal

Re: New mutt GPGME error

2017-06-01 Thread Ian Zimmerman
On 2017-05-30 10:00, Kevin J. McCarthy wrote: > > I just upgraded to Ubuntu 17.04 and got a new version of mutt: 1.7.2.1 > > > > I now frequently get the following error message for delivered mail: > > > > "GPGME: CMS protocol not available" > Alternatively, you can install the gpgsm packag

Re: New mutt GPGME error

2017-05-30 Thread Kevin J. McCarthy
On Tue, May 30, 2017 at 06:57:00AM -0700, Jeffery Small wrote: > > I just upgraded to Ubuntu 17.04 and got a new version of mutt: 1.7.2.1 > > I now frequently get the following error message for delivered mail: > > "GPGME: CMS protocol not available" > > I'm not using gpg and would like t

New mutt GPGME error

2017-05-30 Thread Jeffery Small
I just upgraded to Ubuntu 17.04 and got a new version of mutt: 1.7.2.1 I now frequently get the following error message for delivered mail: "GPGME: CMS protocol not available" I'm not using gpg and would like to stop the continual generation of these messages. I'm hoping that there is