Collin Funk wrote: > today I ran into: > > $ git pull > fatal: unable to access > 'https://https.git.savannah.gnu.org/git/gnulib.git/': The requested URL > returned error: 502
I live reasonably well with these git-level replacement rules: git config set --global --append url.git://git.git.savannah.gnu.org/.insteadOf git://git.savannah.gnu.org/ git config set --global --append url.https://https.git.savannah.gnu.org/git/.insteadOf https://git.savannah.gnu.org/git/ git config set --global --append url.https://github.com/coreutils/gnulib.git.insteadOf git://git.savannah.gnu.org/gnulib.git git config set --global --append url.https://github.com/coreutils/gnulib.git.insteadOf https://git.savannah.gnu.org/git/gnulib.git git config set --global --append url.https://github.com/coreutils/coreutils.git.insteadOf git://git.savannah.gnu.org/coreutils.git git config set --global --append url.https://github.com/coreutils/coreutils.git.insteadOf https://git.savannah.gnu.org/git/coreutils.git The github.com mirror is more reliable and has higher bandwidth. This raises two questions: * Pádraig, how are the mirrors of coreutils and gnulib on github set up? Is it some old technique from GitHub, that is no longer available to new repositories? Or is it some script / cron job of yours? * Should we create mirrors of other package repositories at GitLab or GitHub? Re codeberg: If/when codeberg.org gets dDoS'ed by malpeople and LLMs, what will be their protections? An e.V. in Germany typically does not have the financial resources to pay a sysadmin person. Bruno
