On Mon, Sep 26, 2011 at 11:06 AM, Pete Houston <[email protected]> wrote:
> Hi Chris,
>
> I've just grabbed the source tarball, but the signature fails. Here are
> the md5s of the two files which I've downloaded from sourceforge.net:
>
> 18fca1d435a5ab1cfd0a9381ff0d584f  ledgersmb-1.3.0_rc3.tar.gz
> d06031c906bea9b48813521e58b8d126  ledgersmb-1.3.0_rc3.tar.gz.asc
>
> When trying to verify the signature, gpg says:
>
> gpg: Signature made Mon 26 Sep 2011 00:15:35 BST using RSA key ID 8DA0AF10
> gpg: BAD signature from "LedgerSMB Core Team (This is the key used for
> package signing.) <[email protected]>"
>
> Could somebody please double-check my findings?
>
> Thanks,
>
> Pete

The other sigs (for the rpms) check out on my system, but that one sig
fails for some reason even though it was one I created with that key.

It is good to know someone's checking though. :-)

Thanks!
Chris Travers

------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
_______________________________________________
Ledger-smb-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ledger-smb-devel

Reply via email to