On 2010-6-24 10:15 , Ryan Schmidt wrote: > > On Jun 18, 2010, at 15:04, Jeremy Lavergne wrote: > >>> The sha256 checksum was broken? >> >> Yes, the function didn't exist (second half of the patch)! >> >> At first I figured it was just that we hadn't applied it yet to debug >> message. When i looked further, running `port -d checksum` without the >> latest patch resulted in port believing that the port's checksum for a file >> didn't even exist. > > My point was there was nothing broken about sha256 in MacPorts, and your > patch did not fix anything. Rather, it added a new functionality: it added a > sha256 line to the debug output from the checksum phase when the checksums > don't match.
What? Having all 4 checksums in the "correct checksums line may be" message may be a little excessive, but sha256 could not be used in portfiles before this patch... > For one thing, this has now caused issues for those running trunk who don't > realize that they now can't just copy and paste that into a port (because it > doesn't work with MacPorts 1.9): > > http://trac.macports.org/ticket/25396 ... as demonstrated by this very ticket. - Josh _______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
