From nobody Wed May 04 02:54:28 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 49C1E1ABCD6D for ; Wed, 4 May 2022 02:54:49 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from mx.catwhisker.org (mx.catwhisker.org [107.204.234.170]) (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 4KtLyw2M1Fz4h8q for ; Wed, 4 May 2022 02:54:48 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from albert.catwhisker.org (localhost [127.0.0.1]) by albert.catwhisker.org (8.16.1/8.15.2) with ESMTP id 2442sSbc076614; Wed, 4 May 2022 02:54:28 GMT (envelope-from david@albert.catwhisker.org) Received: (from david@localhost) by albert.catwhisker.org (8.16.1/8.16.1/Submit) id 2442sSCK076613; Tue, 3 May 2022 19:54:28 -0700 (PDT) (envelope-from david) Date: Tue, 3 May 2022 19:54:28 -0700 From: David Wolfskill To: Chris Cc: freebsd-git Subject: Re: When are the git servers available to obtain the ports tree? Message-ID: Reply-To: freebsd-git References: <7dc2545d68f3d4ebbedef4d29c6161f5@bsdforge.com> List-Id: Discussion of git use in the FreeBSD project List-Archive: https://lists.freebsd.org/archives/freebsd-git List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-git@freebsd.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="Zfcy76YmnHl3KPcj" Content-Disposition: inline In-Reply-To: <7dc2545d68f3d4ebbedef4d29c6161f5@bsdforge.com> X-Rspamd-Queue-Id: 4KtLyw2M1Fz4h8q X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of david@catwhisker.org designates 107.204.234.170 as permitted sender) smtp.mailfrom=david@catwhisker.org X-Spamd-Result: default: False [-3.33 / 15.00]; HAS_REPLYTO(0.00)[freebsd-git@freebsd.org]; ARC_NA(0.00)[]; FREEFALL_USER(0.00)[david]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:107.204.234.170]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.20)[multipart/signed,text/plain]; REPLYTO_DOM_NEQ_FROM_DOM(0.00)[]; DMARC_NA(0.00)[catwhisker.org]; NEURAL_SPAM_SHORT(0.07)[0.068]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; MID_RHS_MATCH_FROMTLD(0.00)[]; MLMMJ_DEST(0.00)[freebsd-git]; SIGNED_PGP(-2.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; ASN(0.00)[asn:7018, ipnet:107.192.0.0/12, country:US]; SUBJECT_ENDS_QUESTION(1.00)[]; RCVD_TLS_LAST(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-ThisMailContainsUnwantedMimeParts: N --Zfcy76YmnHl3KPcj Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, May 02, 2022 at 10:27:39AM -0700, 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: >=20 > # git clone -o freebsd --config=20 > remote.freebsd.fetch=3D'+refs/notes/*:refs/notes/*'=20 > https://git.freebsd.org/ports.git PORTS-20220502 >=20 > returns: > error: RPC failed; HTTP 504 curl 22 The requested URL returned error: 504 > fatal: error reading section header 'shallow-info' >=20 > What is the charge for obtaining a current ports tree? Can I purchase an > annual subscription? >=20 > What else do I need to obtain the tree? > ..... FWIW, I maintain (what are referred to later in the thread as) "personal mirrors" (as I had with SVN, and CVS before that). And after having done so with git for a couple of years (? or so), I suddenly started getting some errors -- I don't recall whether they were what you report or not (I'm just back home after a couple of weeks 9 hours east of home, so my brain is less functional than ususal), but I had received a recommendation to run git maintenance run and git gc on my repos. Doing that appeared to prevent a recurrence of the issue, so I set up a cron task to do that on each repo every week. (Since the most critical time for me is the weekend, I do this in the "wee small hours" of Thursday morning -- which should allow me time to take evasive action (e.g., on Thursday or Friday) should something Go Wrong.) Looks as if I set this up back near the end of January; no issues with it so far since then. I scribbled some notes on how I do that at https://www.catwhisker.org/~david/FreeBSD/repo-sync.html -- in case that might be of interest or use. Peace, david --=20 David H. Wolfskill david@catwhisker.org V. Putin does not need "negotiations" to stop his own senseless war. See https://www.catwhisker.org/~david/publickey.gpg for my public key. --Zfcy76YmnHl3KPcj Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iNUEARYKAH0WIQSr0Kzv+UJRY3wfOii0+6PfV4Ix1AUCYnHq5F8UgAAAAAAuAChp c3N1ZXItZnByQG5vdGF0aW9ucy5vcGVucGdwLmZpZnRoaG9yc2VtYW4ubmV0QUJE MEFDRUZGOTQyNTE2MzdDMUYzQTI4QjRGQkEzREY1NzgyMzFENAAKCRC0+6PfV4Ix 1KooAQDJmYJVUsfdbXVXQ887jWQ2rV+nvu/XhngUvELgtxsKywD/YUiAKfPxTOji RVdSQHTqrOpFePZFf4riw4AmpwFNYwA= =O9Rr -----END PGP SIGNATURE----- --Zfcy76YmnHl3KPcj--