On Thu, 2015-09-17 at 13:32 -0700, carl hansen wrote: > I "bzr update"ed before I had the problem. I think gpg key should be > checked, especially > since this is crypto software distributed widely. We better make sure it's > right. I'm unclear > on how to make sure or which key is the right one or what. Maybe check with > Werner or something. I am not sure how to otherwise proceed.
Strange. I just pulled your change and I once again get a checksum error as well for libgcrypt-1.6.4.tar.gz.sig. The sha256sum that you get is: cff6eeb44aeaa3bb8fdfb9d8f8e8d1d799131f75e95c4b9b3426bf6f9cabfd39 The one I'm getting is: c8611e97c8a9f306a9a8309fc07f5b46dbae97f238b200c49f7f2aa5f9fcaa2f Could you maybe send me the sig file that you've downloaded? Also, try doing "make clean" first and also try deleting the relevant files in $GSRC/cache/garstow/archives. Thanks, Brandon
signature.asc
Description: This is a digitally signed message part
