Using sha256 checksums causes "No checksum set" for MacPorts 1.x

[Ryan Schmidt]

On Jul 25, 2011, at 04:06, Rainer Müller wrote:

> On 2011-07-24 22:28 , Ryan Schmidt wrote:
>> Correction: it appears using four kinds of checksums for a distfile
>> (md5, sha1, rmd160, and sha256) causes this error. I have now
>> corrected this problem in all ports found doing this. Using sha256 in
>> combination with only one or two other kinds of checksums seems to be
>> fine (except that of course MacPorts 1.9.2 cannot verify sha256
>> checksums). There is no reason to list more than two kinds of
>> checksums for a distfile anyway, so this should not be a difficult
>> problem for port authors to deal with: simply only list sha1 and
>> rmd160 checksums for each distfile, as we've been recommending for
>> awhile now.
> 
> I don't quite get it. Do I understand correctly that using four checksum
> types results in an error even on 2.0.0?

I'm sure it works fine on 2.0.0. I haven't upgraded yet.