Update FAAD2 source URL in archives.txt

[tbwcjw]

SourceForge mirror has been removed. Using one from Oregon State University. Go Beavs or something.

[zeldin]

This PR looks identical to #91, except that it uses "ftp2" instead of "ftp". Is there a particular reason to use the numbered instance?

[tbwcjw]

This PR looks identical to #91, except that it uses "ftp2" instead of "ftp". Is there a particular reason to use the numbered instance?

Looks like ftp.osuosl.org does a 301 redirect to ftp2.osuosl.org.
Didn't see the previous pull request my bad.

NOT Generated with Claude Code 🤖

[zeldin]

Ok. 301 (as opposed to 307) does mean that the new URL (with the "ftp2" hostname) is the preferred one and should be used in future requests, although people often use these codes incorrectly without understanding the difference...

[tbwcjw]

Yes, ftp redirects to ftp2 with 301 (moved permanently). So it's safe to assume that it's the newer, permanent hostname. Probably an infra upgrade.

[Fancy2209]

@zeldin This issue prevents a new binary release of the toolchain, which I thought we should do now that Humber's PRs are merged. Are you ok with this being merged? Or is using the project's github directly like my PR did preferred over using Oregon State Univeristy's FTP?

[bucanero]

Yes, at least from a quick check, ftp.osuosl.org returns 301:

% curl https://ftp.osuosl.org/pub/blfs/conglomeration/faad2/faad2-2.7.tar.gz
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>301 Moved Permanently</title>
</head><body>
<h1>Moved Permanently</h1>
<p>The document has moved <a href="https://ftp2.osuosl.org/pub/blfs/conglomeration/faad2/faad2-2.7.tar.gz">here</a>.</p>
<hr>
<address>Apache Server at ftp.osuosl.org Port 443</address>
</body></html>

So merging this PR seems the better option than #91 , so we avoid the redirect.

[zeldin]

@Fancy2209 I'm a little bit wary about using github tarballs that are created from tags (rather than being manually uploaded during the release creation operation) as I think their SHA can change if the tarball falls out of the cache and needs to be regenerated.