checksum errors and non accessible wiki

Ryan Schmidt ryandesign at
Thu Oct 22 11:18:11 PDT 2015

On Oct 22, 2015, at 1:17 PM, Ryan Schmidt wrote:
> On Oct 22, 2015, at 1:14 PM, Mihai Moldovan wrote:
>> On 22.10.2015 10:17 AM, Dominik Reichardt wrote:
>>> Thanks - gonna be patient and stopping myself from selfupdates whenever the "bad checksum reports" arrive here ;)
>> FWIW, these "bad checksum reports" seem to have been caused by SourceForge, in
>> the sense that their mirrors sent out 404 not found error messages instead of
>> the actual files, c.f.
>> MacPorts should currently be operating fine when it comes to distfiles.
> If SourceForge was sending a 404 Not Found HTTP status code, that would not be a problem for MacPorts. It's only a problem if SourceForge was sending a 200 OK HTTP status code but delivering an HTML file instead of the distfile we requested, and in that case, MacPorts would print a message stating that the file it got was an HTML file. That was not stated in the error shown above.

Oh sorry, I was thinking of a different thread. That *was* stated in the error above.  But we haven't seen what the HTML file says...

More information about the macports-users mailing list