On Mon, Sep 26, 2011 at 11:10 AM, Chris Travers <[email protected]> wrote: > 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 >> > That's strange. > double checking. > Ok, the signature is the one I created based on that MD5, and when I run it again, I get a different signature file. I believe I have run into some unintuitive behavior with gpg2. I will get an updated signature up shortly.
Best Wishes, 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
