I'm using this gnupg2 version: $ gpg2 --version
gpg (GnuPG) 2.0.17
libgcrypt 1.5.0
Copyright (C) 2011 Free Software Foundation, Inc.
However, many programs, like Evolution, use /usr/bin/gnupg instead of /usr/bin/gnupg2. This caused Evolution to send only part of my messages in upgraded Brigantia. I got around this by renaming gnupg to gnupg.old and linking gnupg to gnupg2: $ sudo mv /usr/bin/gnupg /usr/bin/gnupg.old
$ sudo ln /usr/bin/gnupg2 /usr/bin/gnupg
BUT... see this: $ /usr/bin/gpg.old --version
gpg (GnuPG) 2.0.14
libgcrypt 1.5.0
Copyright (C) 2009 Free Software Foundation, Inc.
Now that I reinstalled gnupg: $ gpg --version
gpg (GnuPG) 1.4.11
Copyright (C) 2010 Free Software Foundation, Inc.
When using Trisquel 5.0 "Dagda" I ln'ed gpg to gpg2, to get Evolution using gnupg2 (had no reason but fun); in the upgrade to Trisquel 5.5 "Brigantia", since gnupg's version remained the same, it was not touched. So, I think this bug is not even a bug -- sorry for taking your time.
Which version of gnupg2 are you using? It says it is fixed in gnupg2 - 2.0.17-2ubuntu2 which is the version in Trisquel 5.5. It should be fixed in 5.5
SirGrant,
I'm using this gnupg2 version:
$ gpg2 --version
gpg (GnuPG) 2.0.17
libgcrypt 1.5.0
Copyright (C) 2011 Free Software Foundation, Inc.
However, many programs, like Evolution, use /usr/bin/gnupg instead of /usr/bin/gnupg2. This caused Evolution to send only part of my messages in upgraded Brigantia. I got around this by renaming gnupg to gnupg.old and linking gnupg to gnupg2:
$ sudo mv /usr/bin/gnupg /usr/bin/gnupg.old
$ sudo ln /usr/bin/gnupg2 /usr/bin/gnupg
BUT... see this:
$ /usr/bin/gpg.old --version
gpg (GnuPG) 2.0.14
libgcrypt 1.5.0
Copyright (C) 2009 Free Software Foundation, Inc.
Now that I reinstalled gnupg:
$ gpg --version
gpg (GnuPG) 1.4.11
Copyright (C) 2010 Free Software Foundation, Inc.
When using Trisquel 5.0 "Dagda" I ln'ed gpg to gpg2, to get Evolution using gnupg2 (had no reason but fun); in the upgrade to Trisquel 5.5 "Brigantia", since gnupg's version remained the same, it was not touched. So, I think this bug is not even a bug -- sorry for taking your time.