From nobody Mon May 02 17:59:14 2022
X-Original-To: freebsd-git@mlmmj.nyi.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
	by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 953211AB14EE;
	Mon,  2 May 2022 17:59:23 +0000 (UTC)
	(envelope-from pi@freebsd.org)
Received: from fc.opsec.eu (fc.opsec.eu [IPv6:2001:14f8:200:4::4])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
	 key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256)
	(Client did not present a certificate)
	by mx1.freebsd.org (Postfix) with ESMTPS id 4KsW7Z66zSz3hrF;
	Mon,  2 May 2022 17:59:22 +0000 (UTC)
	(envelope-from pi@freebsd.org)
Received: from pi by fc.opsec.eu with local (Exim 4.95 (FreeBSD))
	(envelope-from <pi@freebsd.org>)
	id 1nlaKI-000IVY-8t;
	Mon, 02 May 2022 19:59:14 +0200
Date: Mon, 2 May 2022 19:59:14 +0200
From: Kurt Jaeger <pi@freebsd.org>
To: Chris <portmaster@bsdforge.com>
Cc: freebsd-ports <freebsd-ports@freebsd.org>,
	freebsd-git <freebsd-git@freebsd.org>
Subject: Re: On what days are the git servers available to obtain the ports
 tree?
Message-ID: <YnAb8onJW58W/W2G@fc.opsec.eu>
References: <a258fb0624f53ae9234b192bdd717a02@bsdforge.com>
List-Id: Discussion of git use in the FreeBSD project <freebsd-git.freebsd.org>
List-Archive: https://lists.freebsd.org/archives/freebsd-git
List-Help: <mailto:freebsd-git+help@freebsd.org>
List-Post: <mailto:freebsd-git@freebsd.org>
List-Subscribe: <mailto:freebsd-git+subscribe@freebsd.org>
List-Unsubscribe: <mailto:freebsd-git+unsubscribe@freebsd.org>
Sender: owner-freebsd-git@freebsd.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <a258fb0624f53ae9234b192bdd717a02@bsdforge.com>
X-Rspamd-Queue-Id: 4KsW7Z66zSz3hrF
X-Spamd-Bar: /
Authentication-Results: mx1.freebsd.org;
	dkim=none;
	dmarc=none;
	spf=softfail (mx1.freebsd.org: 2001:14f8:200:4::4 is neither permitted nor denied by domain of pi@freebsd.org) smtp.mailfrom=pi@freebsd.org
X-Spamd-Result: default: False [-0.95 / 15.00];
	 RCVD_TLS_LAST(0.00)[];
	 ARC_NA(0.00)[];
	 FREEFALL_USER(0.00)[pi];
	 FROM_HAS_DN(0.00)[];
	 RCPT_COUNT_THREE(0.00)[3];
	 NEURAL_HAM_MEDIUM(-1.00)[-1.000];
	 NEURAL_HAM_LONG(-1.00)[-1.000];
	 MIME_GOOD(-0.10)[text/plain];
	 DMARC_NA(0.00)[freebsd.org];
	 R_SPF_SOFTFAIL(0.00)[~all];
	 NEURAL_SPAM_SHORT(0.15)[0.150];
	 TO_MATCH_ENVRCPT_SOME(0.00)[];
	 TO_DN_ALL(0.00)[];
	 MLMMJ_DEST(0.00)[freebsd-ports,freebsd-git];
	 FROM_EQ_ENVFROM(0.00)[];
	 R_DKIM_NA(0.00)[];
	 MIME_TRACE(0.00)[0:+];
	 ASN(0.00)[asn:12502, ipnet:2001:14f8::/32, country:DE];
	 SUBJECT_ENDS_QUESTION(1.00)[];
	 RCVD_COUNT_TWO(0.00)[2]
X-ThisMailContainsUnwantedMimeParts: N

Hi!

> 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
> 
> returns:
> error: RPC failed; HTTP 504 curl 22 The requested URL returned error: 504
> fatal: error reading section header 'shallow-info'

That's the command I use as well. To be honest, I do not
need to clone the tree that often, once every few month is enough.

-- 
pi@FreeBSD.org         +49 171 3101372                  Now what ?