Portsnap metadata is correctly signed, but contains at least one line which appears bogus.

[Eitan Adler]

Woops - I missed this email

> Eitan Adler <eitanadlerlist at gmail.com> wrote:
>
>> I've been getting the following message a lot lately.
>>
>> Portsnap metadata is correctly signed, but contains
>> at least one line which appears bogus.
>>

I'm still getting this error even after a complete removal of /var/db/portsnap

> If the metadata is correctly signed then it sounds like it should be a
> server-side problem. OTOH  no-one else is mentioning it, are you
> running portsnap from a reasonably recent release?

Yeah - I'm running from 8-RELEASE

>
> It might be instructive to edit portsnap, look for the places where
> fetch_metadata_freakout is called and have it make a copy of the
> offending file.

I added some echo lines to help

    if grep -qvE "^[0-9A-Z.]+\|[0-9a-f]{64}$" tINDEX.new; then
        fetch_metadata_freakout
        return 1
    fi
appears to be the part which goes nuts.