Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 3 May 2022 19:54:28 -0700
From:      David Wolfskill <david@catwhisker.org>
To:        Chris <bsd-lists@bsdforge.com>
Cc:        freebsd-git <freebsd-git@freebsd.org>
Subject:   Re: When are the git servers available to obtain the ports tree?
Message-ID:  <YnHq5GLWDOb1lqA7@albert.catwhisker.org>
In-Reply-To: <7dc2545d68f3d4ebbedef4d29c6161f5@bsdforge.com>
References:  <7dc2545d68f3d4ebbedef4d29c6161f5@bsdforge.com>

next in thread | previous in thread | raw e-mail | index | archive | help

--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--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?YnHq5GLWDOb1lqA7>