Date: Mon, 2 May 2022 10:50:57 -0700 From: Kyle Evans <kevans@freebsd.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: <CACNAnaH6g9%2BPzKeTHGBF=jJYeH_dXyGKAwck_t3GppAM0sWPcQ@mail.gmail.com> In-Reply-To: <7dc2545d68f3d4ebbedef4d29c6161f5@bsdforge.com> References: <7dc2545d68f3d4ebbedef4d29c6161f5@bsdforge.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, May 2, 2022 at 10:27 AM Chris <bsd-lists@bsdforge.com> 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 > > returns: > error: RPC failed; HTTP 504 curl 22 The requested URL returned error: 504 > fatal: error reading section header 'shallow-info' > > What is the charge for obtaining a current ports tree? Can I purchase an > annual subscription? > I understand this is probably an attempt at humor, but it comes off (to me) a little more aggressive/instigative than you might have intended. > What else do I need to obtain the tree? > I find trying to work with ports over HTTP to be a miserable experience, but anongit (see bottom of https://cgit.freebsd.org/ports) typically provides a pretty good experience. Thanks, Kyle Evans
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CACNAnaH6g9%2BPzKeTHGBF=jJYeH_dXyGKAwck_t3GppAM0sWPcQ>