On 2025-05-22 05:18, Karl Berry wrote:
As an alternative, you could try our experimental, volunteer-run
    read-only mirror:

    https://https.git.savannah.gnu.org/git/libiconv.git
    or
    git://git.git.savannah.gnu.org/git/libiconv.git

Do the new experimental readonly mirrors provide any web browsing of the
repos (cgit, gitweb, ...), or just git access (via https or git as
shown)?

Yes, we do have that, but under different subdomains (Bob decided this):

https://cgit.git.savannah.gnu.org/cgit/
("/" will be redirected to "/cgit/")
https://gitweb.git.savannah.gnu.org/gitweb/
("/" will be redirected to "/gitweb/")

I'm guessing it's only git, since presumably the AI crawler problem
would otherwise repeat on each mirror, but just wanted to ask.(*)

Thanks,
Karl

We'll deal with those when it comes to that. The node I host has 1Gbps (IPv4) and 10Gbps (IPv6) (both residential lines) and more than 800 CPU cores in total and I say "I dare you to abuse it lol". We'll give them hell [1].

[1] https://hell.jing.rocks

P.S. I ask because automake's release process has always included
retrieving various common files (maintained in other repos) from
https://git.savannah.gnu.org, e.g., config.guess from:
https://git.savannah.gnu.org/gitweb/?p=config.git;a=blob_plain;hb=HEAD;f=config.guess

I think I'll change the process to assume a local git checkout of those
other repos. That seems like the path of least resistance.
(I'm getting the expected 502 bad gateways ...)

ya fetching from gitweb (or cgit) sounds like a bad idea...

--
Jing Luo
About me: https://jing.rocks/about/
GPG Fingerprint: 4E09 8D19 00AA 3F72 1899 2614 09B3 316E 13A1 1EFC

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to