On Fri, Apr 25 2014, Joey Hess <jo...@debian.org> wrote: > Jameson Graef Rollins wrote: >> This is a known issue and will be fixed in the next release. I'm >> curious that you about your "broken by upgrade" subject, though. Was >> this error prompted by an assword upgrade, or by an upgrade of something >> else? > > I think it was an upgrade of python modules that assword uses.
Hey, Joey. None of the assword modules have been updated recently. The only thing that has been updated recently that might trigger this issue is python-gpgme. The exception that we're seeing in this case is a by-product of a gpg signature validation error. It appears that maybe the validity of the key that signed your assword database has changed. It's possible that a python-gpgme or gnupg update could have "caused" this, but my guess is that it more likely has to do with the key validity itself. Do you know if that has changed at all recently? jamie.
pgpos2ZyfxcDB.pgp
Description: PGP signature
