Re: On 14-CURRENT: no ports options anymore?

On Sat, 13 Mar 2021 15:13:15 -0500
Michael Butler via freebsd-current <freebsd-current_at_freebsd.org> wrote:

> On 3/13/21 3:00 PM, Hartmann, O. wrote:
> > On Sat, 13 Mar 2021 19:52:47 +0000 (UTC)
> > Filippo Moretti via freebsd-current <freebsd-current_at_freebsd.org> wrote:
> >   
> >>   
> >> I had the same problem in console modeFiippo
> >>      On Saturday, March 13, 2021, 8:33:57 PM GMT+1, Stefan Esser <se_at_freebsd.org>
> >> wrote:
> >>
> >>   Am 13.03.21 um 20:17 schrieb Hartmann, O.:  
> >>> Since I moved on to 14-CURRENT, I face a very strange behaviour when trying to set
> >>> options via "make config" or via poudriere accordingly. I always get "===> Options
> >>> unchanged" (when options has been already set and I'd expect a dialog menu).
> >>> This misbehaviour is throughout ALL 14-CURRENT systems (the oldest is at FreeBSD
> >>> 14.0-CURRENT #49 main-n245422-cecfaf9bede9: Fri Mar 12 16:08:09 CET 2021 amd64).
> >>>
> >>> I do not see such a behaviour with 13-STABLE, 12-STABLE, 12.2-RELENG.
> >>>
> >>> How to fix this? What happened?  
> >>
> >> Hi Oliver,
> >>
> >> please check your TERM setting and test with a trivial setting
> >> if it is not one of xterm, vt100 or vt320 (for example).
> >>
> >> I had this problem when my TERM variable was xterm-color, which
> >> used to be supported but apparently no longer is.
> >>
> >> Regards, STefan  
> > 
> > [...]
> > 
> > on one of the hosts (non-X11), loged in via ssh, the settings are:
> > 
> > # echo $TERM
> > xterm
> > cd /usr/ports/www/apache24
> > make config  
> > ===> Options unchanged (no menu popping up)  
> >   
> 
> I ran into something similar where dialog4ports would dump core after an 
> upgrade. Rebuilding the port (ports-mgmt/dialog4ports) solved it for me,
> 
> 	imb

Thanks, recompilig ports-mgmt/dialog4ports solved the problem! I was sure that after some
ncurses changes in 14-CURRENT I've rebuilt every single port on all 14-CURRENT systems
after that incident, bad luck.

Thanks.
oh