Re: pax(1) looping infinitely

2024-06-21 Thread Warner Losh
The last core team announced one. But you can add Approved by: imp Warner On Sat, Jun 22, 2024, 12:16 AM Ganael Laplanche < ganael.laplan...@martymac.org> wrote: > > > On 6/21/24 23:41, Yuri Pankov wrote: > > > .mailmap > > Thanks Yuri! > > I cannot see any blanket approval for a ports committ

Re: pax(1) looping infinitely

2024-06-21 Thread Ganael Laplanche
On 6/21/24 23:41, Yuri Pankov wrote: .mailmap Thanks Yuri! I cannot see any blanket approval for a ports committer modifying that file within the src repo. Can a src committer approve (or commit) the following change please ? : diff --git a/.mailmap b/.mailmap index 0d0231a3da68..3d33a

Re: pax(1) looping infinitely

2024-06-21 Thread Yuri Pankov
Ganael Laplanche wrote: > > > Le 21/06/2024 à 18:58, Warner Losh a écrit : > >> My apologies...  I didn't check, but. it's in your sig so I should >> have. > > Hey, no pb :) > >> There's a mapping file that can be updated for cases like this. > > Hmmm, I could add my address there. Can you p

Re: pax(1) looping infinitely

2024-06-21 Thread Ganael Laplanche
Le 21/06/2024 à 18:58, Warner Losh a écrit : My apologies...  I didn't check, but. it's in your sig so I should have. Hey, no pb :) There's a mapping file that can be updated for cases like this. Hmmm, I could add my address there. Can you point me to that file, I can't find it in the

Re: pax(1) looping infinitely

2024-06-21 Thread Warner Losh
On Fri, Jun 21, 2024 at 10:55 AM Ganael Laplanche < ganael.laplan...@martymac.org> wrote: > On 6/21/24 18:44, Warner Losh wrote: > > Hi Warner, > > > Fixed. > > > > commit 681fd2bed8eaba88693867ba928a1c03a5b152cc (HEAD -> main) > > Author: Ganael Laplanche > Thanks! > > > Wrote the commit messag

Re: pax(1) looping infinitely

2024-06-21 Thread Ganael Laplanche
On 6/21/24 18:44, Warner Losh wrote: Hi Warner, Fixed. > commit 681fd2bed8eaba88693867ba928a1c03a5b152cc (HEAD -> main) Author: Ganael Laplanche Thanks! Wrote the commit message and had to guess at the right email to use. But it looked like bz and the mail here were the same. You could

Re: pax(1) looping infinitely

2024-06-21 Thread Warner Losh
Fixed. commit 681fd2bed8eaba88693867ba928a1c03a5b152cc (HEAD -> main) Author: Ganael Laplanche Date: Fri Jun 21 10:39:09 2024 -0600 pax: Terminate loop for empty directory names .. Wrote the commit message and had to guess at the right email to use. But it looked like bz and the mail here

Re: ncurses message spam

2024-06-21 Thread Baptiste Daroussin
On Fri 21 Jun 15:23, Shawn Webb wrote: > Hey all, > > With the recent changes to ncurses in base, I'm getting a bunch of > messages (snippet below) on every single new PTY. Every time I open a > new window in tmux or login via ssh, I'm getting spammed with a flood > of messages like below. > > ==

ncurses message spam

2024-06-21 Thread Shawn Webb
Hey all, With the recent changes to ncurses in base, I'm getting a bunch of messages (snippet below) on every single new PTY. Every time I open a new window in tmux or login via ssh, I'm getting spammed with a flood of messages like below. BEGIN LOG Name collision 'tvi950-b' between

pax(1) looping infinitely

2024-06-21 Thread Ganael Laplanche
Hello, Our pax(1) implementation has a small bug triggered when it is fed with a directory containing a trailing slash. Could a src committer have a look at: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277060 ? I've submitted a small patch that fixes the problem. Thanks! Cheers, --