Re: TLC needed for PR
On 05/02/2022 6:13 am, Martin Waschbüsch wrote: Hi there, If a committer could have a look at https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263674 That would be awesome! Thanks, Martin Committed, thanks! In the future, feel free to send me a note when you have a PR for any dovecot related ports. -- Larry Rosenman http://people.freebsd.org/~ler Phone: +1 214-642-9640 E-Mail: l...@freebsd.org US Mail: 5708 Sabbia Dr, Round Rock, TX 78665-2106
On what days are the git servers available to obtain the ports tree?
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? What else do I need to obtain the tree? Thanks. l8r, Chris 0xBDE49540.asc Description: application/pgp-keys
FreeBSD ports you maintain which are out of date
Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/po...@freebsd.org.html Port| Current version | New version +-+ games/exult | 1.7.0.20211128 | snapshot-v1.9.0.20220502 +-+ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt Reported by:portscout!
Re: On what days are the git servers available to obtain the ports tree?
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. -- p...@freebsd.org +49 171 3101372 Now what ?
Re: On what days are the git servers available to obtain the ports tree?
On 2022-05-02 10:59, Kurt Jaeger wrote: 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. Thanks for taking the time to reply, Kurt. Just for the record; it took exactly 9 attempts before returning 200. :-( That's roughly 10 minutes, but closer to 15 in real time. But at least it finally worked. :-) It'd be nice to discover *why* this is a problem. Is it just *my* servers IP's... ? Thanks again! --Chris 0xBDE49540.asc Description: application/pgp-keys
Re: On what days are the git servers available to obtain the ports tree?
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! Regards, Janky Jay, III OpenPGP_signature Description: OpenPGP digital signature
Re: On what days are the git servers available to obtain the ports tree?
On 2022-05-02 11:21, Lorenzo Salvadore wrote: --- Original Message --- On Monday, May 2nd, 2022 at 20:12, Chris wrote: On 2022-05-02 10:59, Kurt Jaeger wrote: > 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. Thanks for taking the time to reply, Kurt. Just for the record; it took exactly 9 attempts before returning 200. :-( That's roughly 10 minutes, but closer to 15 in real time. But at least it finally worked. :-) It'd be nice to discover why this is a problem. Is it just my servers IP's... ? I see you are using https://git.freebsd.org/ports.git . Have you tried ssh://g...@gitrepo.freebsd.org/ports.git instead ? Thank you kindly for the reply. Unfortunately, that returns FATAL/REFUSED. If I understand correctly what's written at the end of the https://cgit.freebsd.org/ports/ page, this link is reserved for developers, so it probably has less traffic and you might have more luck. Thank you for the thoughtful reply, Lorenzo! l8r, Chris Cheers, Lorenzo Salvadore 0xBDE49540.asc Description: application/pgp-keys
Re: On what days are the git servers available to obtain the ports tree?
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. Thanks! :-) --Chris Regards, Janky Jay, III 0xBDE49540.asc Description: application/pgp-keys
Re: On what days are the git servers available to obtain the ports tree?
Hi Chris, On 5/2/22 13: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. Just a quick FYI, the 500MB was just the first number I tried when tinkering and trying to resolve the issue I was having. It's very possible that number could be much, much lower and still work for you. Maybe try adding 10MB at a time and give it a shot. Might just work immediately. *shrug* Regards, Janky Jay, III OpenPGP_signature Description: OpenPGP digital signature
Re: On what days are the git servers available to obtain the ports tree?
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. Thanks! :-) --Chris Regards, Janky Jay, III 0xBDE49540.asc Description: application/pgp-keys
Re: On what days are the git servers available to obtain the ports tree?
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.
Re: On what days are the git servers available to obtain the ports tree?
On 2022-05-02 13:14, Jose Quinteiro wrote: 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? Thanks for the reply, Jose. Sure. 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. I can clone the github hosted mirror && make the changes. But that removes the one-true-source factor, adds additional steps to a procedure that should "Just Work". Which is the real question. Why doesn't it Just Work? Clearly there is a problem with the FreeBSD git based system. All of the mailing lists work, I'm on 8 of them. All the dist servers work. I can get the dist images w/o any trouble. The online man pages work. The web pages work. But the git(1) service(s) don't. Why && shouldn't everyone care as to why they don't? Thanks again! :-) Thanks, Jose. Chris 0xBDE49540.asc Description: application/pgp-keys
Re: On what days are the git servers available to obtain the ports tree?
## Chris (portmas...@bsdforge.com): > Which is the real question. Why doesn't it Just Work? Given that there are very few reports of such problems, I'd think that the git mirrors do in fact "Just Work" for a vast majority of people (it sure works for me). And then there's the fact that you didn't provide that much information: e.g. does that fail only in the jail or on the base system itself?; does it work from another system in the same network?; which mirror(s) are failing?; anything special - IPv4, IPv6, tunnels, not-that-excellent connection?; and that's only what springs to mind from the top of my head. Remember, you're asking for mostly volunteer's time here, and for (almost?) all of these volunteers there is no problem. Regards, Christoph -- Spare Space
Re: On what days are the git servers available to obtain the ports tree?
On 2022-05-02 14:07, Christoph Moench-Tegeder wrote: ## Chris (portmas...@bsdforge.com): Which is the real question. Why doesn't it Just Work? Given that there are very few reports of such problems, I'd think that the git mirrors do in fact "Just Work" for a vast majority of people (it sure works for me). And then there's the fact that you didn't provide that much information: e.g. does that fail only in the jail or on the base system itself?; does it work from another system in the same network?; which mirror(s) are failing?; anything special - IPv4, IPv6, tunnels, not-that-excellent connection?; and that's only what springs to mind from the top of my head. Remember, you're asking for mostly volunteer's time here, and for (almost?) all of these volunteers there is no problem. Fair (and good) questions! :-) 8 Systems/12 Jails OS version 12.x | 13.x git version 2.3x The 8 systems involved here are all (static) IPv4 bound. While as I test now. I'm finding there are no problems (as reported) PRIOR: it didn't matter whether jail(8) or the host. The attempts timed out after some 5 minutes with a report of: error: RPC failed; HTTP 504 curl 22 The requested URL returned error: 504 fatal: error reading section header 'shallow-info' That's the best I can offer ATM. Thanks for asking. :-) Regards, Christoph --Chris 0xBDE49540.asc Description: application/pgp-keys
Re: On what days are the git servers available to obtain the ports tree?
Hello. I'm a maintainer too :) Probably, git is difficult for maintainers to keep the following conditions. # git status --show-stash -- On branch main Your branch is up to date with 'origin/main'. nothing to commit, working tree clean To clean it up without cloning, we will have to make full use of the following commands, which are listed here. # git stash push --all -- :/ # git stash pop # git pull --autostash --rebase --prune -- # git reset --soft origin -- # git checkout HEAD -- :/ # git restore --source=HEAD --staged -- :/ # git clean -d --force -X -- :/ I will not give an explanation of what each is :) :/ is not an emoticon :) It is my opinion that if we can maintain a non-clone, it will be less likely to be a 504. Regards.
Re: On what days are the git servers available to obtain the ports tree?
There's no need to CC me. I'm subscribed to the list. On 5/2/22 13:37, Chris wrote: >> Is there a reason why you can't do a git pull to accomplish this? > Thanks for the reply, Jose. > Sure. Still don't understand why you can't just do a "git pull". That will fetch and apply just the changes from upstream, instead of re-downloading 27+ years of history* uselessly and pointlessly. >> >> 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. > I can clone the github hosted mirror && make the changes. But that > removes the one-true-source factor, adds additional steps to a procedure > that should "Just Work". I don't follow the one-true-source thing. If two git repos have the same commit hashes, they are copies of the same repo. That is one of the essential properties of git. A git pull after setting the origin to the Freebsd remote should be a no-op. You can use that to verify if you're worried. > Which is the real question. Why doesn't it Just Work? Clearly there is a > problem > with the FreeBSD git based system. I'm guessing the problem is people downloading the full history of the repo over and over again for no good reason. Github has more bandwidth. Use them. If you insist on doing it this way, at least do a shallow clone. Thanks, Jose * https://cgit.freebsd.org/ports/log/?ofs=582500
