Re: r358062(ncurses) breaks installed ports, howto check?

2020-02-27 Thread Mark Millard
Andreas Ott andreas at naund.org wrote on Thu Feb 27 20:20:13 UTC 2020 : > > # find /usr/local/*bin* /usr/local/lib* -type f \ > > | xargs ldd -f '%p %A\n' 2>&1 | grep "^/lib/libncurses[^ ]*\.so\.8" | cut > > -w -f2 \ > > | xargs pkg which -q | sort -u | more > > after pkp update && pkg upgrade

Re: r358062(ncurses) breaks installed ports, howto check?

2020-02-27 Thread O. Hartmann
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Am Tue, 25 Feb 2020 05:02:54 -0500 Thomas Dickey schrieb: > On Tue, Feb 25, 2020 at 10:27:37AM +0100, Baptiste Daroussin wrote: > > On Tue, Feb 25, 2020 at 04:19:56AM -0500, Thomas Dickey wrote: > > > On Mon, Feb 24, 2020 at 08:28:03PM -0500, Tho

Re: r358062(ncurses) breaks installed ports, howto check?

2020-02-27 Thread Andreas Ott
Hi, coming late to this game. On Mon, Feb 24, 2020 at 11:43:15AM -0800, Mark Millard wrote: > > After r358062, many installed ports do not work anymore on several running > > systems (CURRENT). > > /usr/src/UPDATING states one should reinstall all ncurses depending ports, > > but no hint is > >

Re: lame reverse DNS?

2020-02-27 Thread Chris
On Thu, 27 Feb 2020 16:56:55 +0100 Herbert J. Skuhra herb...@gojira.at said On Thu, Feb 27, 2020 at 10:31:59AM +0100, Kurt Jaeger wrote: > Hi! > > > The problem has been resolved but I still sometimes see "connect from > > unknown[2610:1c1:1:606c::19:2]" in the maillog (today: 6 of 131 > > con

Re: lame reverse DNS?

2020-02-27 Thread Herbert J. Skuhra
On Thu, Feb 27, 2020 at 10:31:59AM +0100, Kurt Jaeger wrote: > Hi! > > > The problem has been resolved but I still sometimes see "connect from > > unknown[2610:1c1:1:606c::19:2]" in the maillog (today: 6 of 131 > > connections). Local unbound issue? > > That IPv6 has a valid reverse DNS record, s

Re: lame reverse DNS?

2020-02-27 Thread Mark Martinec
The problem has been resolved but I still sometimes see "connect from unknown[2610:1c1:1:606c::19:2]" in the maillog (today: 6 of 131 connections). Local unbound issue? That IPv6 has a valid reverse DNS record, so please try to investigate. Looks like an intermittent problem. Tried the followin

Re: lame reverse DNS?

2020-02-27 Thread Kurt Jaeger
Hi! > The problem has been resolved but I still sometimes see "connect from > unknown[2610:1c1:1:606c::19:2]" in the maillog (today: 6 of 131 > connections). Local unbound issue? That IPv6 has a valid reverse DNS record, so please try to investigate. Something like the output from: dig +trace -