Re: git: 0882d238e9b4 - main - Mk/bsd.sites.mk: Update GENTOO entries

Hi,

At least the first 2 were dead and/or didn't connect from different 
locations at time I decided to redo the list based on 
https://www.gentoo.org/downloads/mirrors/. I tried to determine and use 
sites that have as good connectivity and speed for all regions, both 
LeaseWeb and Rackspace services in multiple and from my test locations 
(different regions) they performed overall well. In theory there isn't 
anything wrong with unofficial ones however such hosts may not be as 
actively monitored for health and consistency (being in sync) and from 
what I've seen and looked at feedback in general it's not desirable list 
such hosts unless needed. The rest of the hosts were selected based on 
of peering, speed and regional location.

Regarding your connection I'm a bit confused about your reasoning. 
Looking at the previous list specifically there are two working hosts 
(as far as I can tell) ftp.snt.utwente.nl, ftp.uni-erlangen.de before 
you hit mirrors.163.com. While they may not be ideal for all locations 
they are stable but can be a bit slow depending on your location. 
Irregardless of transfer speed TCP sessions shouldn't just randomly 
drop/timeout which I presume is occurring as the sites are reachable. 
Connectivity issues and not overall transfer speed for "single/few" 
hosts is something that's out of scope for the ports tree and needs to 
be addressed by the user(s). To answer your question regarding 
mirrors.163.com the reason is simply because there are better options 
overall and .cn mirrors are in the majority of times very slow to hosts 
outside of China (Rackspace lists a node in HK fwiw).

Having that in mind I think in your specific case the best solution 
overall would to be using for example cURL instead of fetch which allows 
resuming of transfers or possibly extend 
https://codeberg.org/tobik/parfetch-overlay if your connection is 
unstable. This commit only affects a dozen of ports that probably aren't 
all that frequently used. Most of tree overall have single hosts listed 
and afterwards relies on FreeBSD's infrastructure so I presume that you 
have a lot more issues with the tree overall than just a handful of 
ports.

I think we can safely say that if 8 hosts in different regions, ASNs etc 
fails your host has more issues than the amount of mirrors we provide, 
in fact the vast majority of ports actually provides fewer mirrors than 
that including FreeBSD's infrastructure.

Best regards,
Daniel

On 2023-03-20 04:40, Alexey Dokuchaev wrote:
> On Sun, Mar 19, 2023 at 06:08:51PM +0000, Daniel Engberg wrote:
>> commit 0882d238e9b48a0cccf8517711fef1dd3fc9e064
>> 
>>   Mk/bsd.sites.mk: Update GENTOO entries
>> 
>>   Refresh mirror list and remove dead mirrors or unofficial ones
> 
> Which ones are dead?  What's wrong with "unofficial" ones?  Why
> did you remove mirrors.163.com which is often the only one that
> works for me?
> 
>>   While at it reduce the list to a reasonable amount of mirrors
> 
> Who defines what is a "reasonable" amount of mirrors?  To me, the
> more the better.  My internet connection is quite bad and it often
> takes several rounds of trying every mirror to get the distfile.
> 
> ./danfe