Date: Mon, 2 May 2022 13:14:23 -0700 From: Jose Quinteiro <freebsd@quinteiro.org> To: ports@freebsd.org Subject: Re: On what days are the git servers available to obtain the ports tree? Message-ID: <eefdb695-ecc6-ec13-fe39-087bb1278ef0@quinteiro.org> In-Reply-To: <13df051029243432f82b50a815926517@bsdforge.com> References: <a258fb0624f53ae9234b192bdd717a02@bsdforge.com> <d73f8e45-3bc5-d01c-5d9b-a79ae3444abf@unfs.us> <71bb8213381565858ab36e680b9634de@bsdforge.com> <13df051029243432f82b50a815926517@bsdforge.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 5/2/22 12:55, Chris wrote: > On 2022-05-02 12:04, Chris wrote: >> On 2022-05-02 11:21, Janky Jay, III wrote: >>> Hi Chris, >>> >>> On 5/2/22 11:09, 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 >>>> >>>> returns: >>>> error: RPC failed; HTTP 504 curl 22 The requested URL returned >>>> error: 504 >>>> fatal: error reading section header 'shallow-info' >>> >>> I've run into this issue in the past with older versions of git. I >>> found that >>> updating my version of git to anything equal or newer than 2.35.1 >>> resolved it. >>> >>> If you can't update your git version because you can't update your >>> ports tree, I >>> found that adjusting the size of the global config for git's >>> "http.postBuffer" to >>> 500MB fixed the issue for older git versions: >>> >>> # git config --global http.postBuffer 524288000 >>> >>> Hope that helps! >> I think you may have provided me with both the problem && solution. >> I'm performing >> all of this within a jail(8) && my copy of git is not the newest; the >> resources are >> also less than those of the host. So I would venture a guess that at >> *least* one of >> your proposed solution gets it for me. > OK I tried > #git config --global http.postBuffer 524288000 > but the results were the same. :-( > > So I upgraded git to git-2.36.0 in that jail and again, the results were > the same. :-( > > Thanks for your suggestions, Jay. > Looks like I'll have to cobble up a script and add it to cron. To > attempt to get a copy > of the ports tree once a day. Not stopping attempts until successful> Is there a reason why you can't do a git pull to accomplish this? What I've done in the past when I had trouble cloning the Freebsd-hosted repo is to clone the Github-hosted mirror, and then set the origin to the Freebsd repo. Thanks, Jose.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?eefdb695-ecc6-ec13-fe39-087bb1278ef0>