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 On Sun, Sep 25, 2011 at 04:21:56PM -0700, Chris Travers wrote: > > Tarballs and RPMs are on Sourceforge. The spec file for the RPM's > corrects a number of oversights there too. > -- Openstrike - improving business through open source http://www.openstrike.co.uk/ or call 01722 770036 / 07092 020107
pgphlCiHbFath.pgp
Description: PGP signature
------------------------------------------------------------------------------ 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
