Re: When are the git servers available to obtain the ports tree?

On 2022-05-02 18:42, Philip Paeps wrote:
> On 2022-05-03 01:27:39 (+0800), Chris wrote:
>> I'm a maintainer for well over 100 ports. But more often than
>> not, I am not permitted to obtain the ports tree from any of
>> the FreeBSD git servers:
>> 
>> # git clone -o freebsd --config 
>> remote.freebsd.fetch='+refs/notes/*:refs/notes/*' 
>> https://git.freebsd.org/ports.git PORTS-20220502
> 
Thanks for the reply, Philip.
> Which mirror are you hitting?  What does "host git.freebsd.org" say?
# host git.freebsd.org
git.freebsd.org is an alias for gitmir.geo.freebsd.org.
gitmir.geo.freebsd.org has address 149.20.1.203
gitmir.geo.freebsd.org has IPv6 address 2001:4f8:1:11::e6a:1
gitmir.geo.freebsd.org mail is handled by 0

> 
>> returns:
>> error: RPC failed; HTTP 504 curl 22 The requested URL returned error: 504
>> fatal: error reading section header 'shallow-info'
> 
> I can't see how a mirror would give that error.  My gut feeling is that this 
> is a
> middlebox rather than one of our Git mirrors.  I'd need to take a closer 
> look at
> the logs to be sure.  Please let me know what mirror you're hitting so I can
> check.
> 
> Does using anongit@git.freebsd.org:ports.git instead of
> https://git.freebsd.org/ports.git work?  That bypasses any HTTP weirdness.
I'll check. Thanks for the insight.
> 
>> What is the charge for obtaining a current ports tree? Can I purchase an
>> annual subscription?
> 
> It's included in the cost of your FreeBSD support contract.
Sweet! :-)
> 
>> What else do I need to obtain the tree?
> 
> If you're maintaining 100+ ports, a small additional investment of time to
> familiarise yourself with Git will save you from having to download the 
> entire
> ports tree every time.  This is also better use of cluster resources 
> maintained by
> other volunteers.
That's fair to say. But still... ;-)

Thanks again! :-)
> 
> Philip
l8r,
Chris