<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">> Last night, sourceforge was returning an html file saying that SF was<br>
> in "disaster recovery mode". The checksum check baled out at this<br>
> point.<br>
><br>
> This morning, something a bit different is happening, but there's<br>
> still a checksum issue.<br>
<br>
That's <a href="https://trac.macports.org/ticket/51019" rel="noreferrer" target="_blank">https://trac.macports.org/ticket/51019</a>. Upstream re-packaged the<br>
files we downloaded, but they forgot to update the SHA1SUMS file, so I<br>
did hold off accepting the change until they confirmed.<br>
<br>
> I wonder whether there might be some way for macports to avoid the use<br>
> of SF? Googling around, SF seems to have a pretty grubby reputation<br>
> nowadays.<br>
<br>
I agree, but we're not upstream developers. Please convince the people<br>
that still use SF to move somewhere else.<br></blockquote><div><br></div><div>Maybe I can convince MacPorts developers to change where they fetch their own sources?</div><div>I'm not sure if it indeed is so -- but the last sentence seems to suggest to me that MacPorts still fetches GS source tarball from SourceForge.</div><div>The primary source is listed here: <a href="http://downloads.ghostscript.com/public/">http://downloads.ghostscript.com/public/</a></div><div>Which points to: <a href="https://github.com/ArtifexSoftware/ghostpdl-downloads/releases/">https://github.com/ArtifexSoftware/ghostpdl-downloads/releases/</a></div><div><br></div><div>Cheers, Kurt</div><div> </div></div><br></div></div>