DAve wrote:
<snip>
I ran into one issue but I haven't gotten a chance to look deeper into
it yet. The sha1 file on updates.spamassassin.org is in one format, and
he sha1 file I create is in another. Currently sa-update can't parse my
file so I had to edit it.
SpamAssassin sha1 contents (would all be one line) have the signature
first,
f7c3edde6e9e2330318c3fc6a8e70af68387eaeb
/home/updatesd/tmp/stage/3.2.0/update.tgzSHA1
My sha1 contents (would all be one line) have the signature last,
(/data/data/lastremaining.com/public_html/updates/tls-local/20060810.tar.gz)=
8918d6852caab9e57f645e0ff8510c3026fdedd2
521 # Validate the SHA1 signature before going forward with more
522 # complicated operations.
523 # The SHA1 file may be "signature filename" ala sha1sum, just use
the signature
524 $SHA1 =~ /^([a-fA-F0-9]{40})/;
525 $SHA1 = $1 || 'INVALID';
Line 524 in sa-update is the failure I believe. I suspect anyone
creating a channel on FreeBSD may have the same problem.
Changing line 524 to
$SHA1 =~ /([a-fA-F0-9]{40})/;
solves the problem, though there is likely a better way to ensure you
are really parsing a digest.
DAve
--
Three years now I've asked Google why they don't have a
logo change for Memorial Day. Why do they choose to do logos
for other non-international holidays, but nothing for
Veterans?
Maybe they forgot who made that choice possible.
