Date: Sat, 13 Mar 2021 22:03:01 +0100 From: "Hartmann, O." <o.hartmann@walstatt.org> To: Michael Butler via freebsd-current <freebsd-current@freebsd.org> Cc: Michael Butler <imb@protected-networks.net>, FreeBSD Current <current@freebsd.org> Subject: Re: On 14-CURRENT: no ports options anymore? Message-ID: <20210313220301.28db1d0f@hermann.fritz.box> In-Reply-To: <52964883-05ce-66cc-4d6f-9797746a9a62@protected-networks.net> References: <20210313201702.5f9dfa9b@hermann.fritz.box> <25cd3ca3-edb6-8b7a-8ad5-f0737d8bd493@freebsd.org> <509410723.637403.1615665167513@mail.yahoo.com> <20210313210002.30ad4345@hermann.fritz.box> <52964883-05ce-66cc-4d6f-9797746a9a62@protected-networks.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--Sig_/pKvg+lh/Uqtr0traoqMY_l_ Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Sat, 13 Mar 2021 15:13:15 -0500 Michael Butler via freebsd-current <freebsd-current@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@freebsd.org> wrote: > > =20 > >> =20 > >> I had the same problem in console modeFiippo > >> On Saturday, March 13, 2021, 8:33:57 PM GMT+1, Stefan Esser <se@f= reebsd.org> > >> wrote: > >> > >> Am 13.03.21 um 20:17 schrieb Hartmann, O.: =20 > >>> 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 = "=3D=3D=3D> 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 2= 021 amd64). > >>> > >>> I do not see such a behaviour with 13-STABLE, 12-STABLE, 12.2-RELENG. > >>> > >>> How to fix this? What happened? =20 > >> > >> 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 =20 > >=20 > > [...] > >=20 > > on one of the hosts (non-X11), loged in via ssh, the settings are: > >=20 > > # echo $TERM > > xterm > > cd /usr/ports/www/apache24 > > make config =20 > > =3D=3D=3D> Options unchanged (no menu popping up) =20 > > =20 >=20 > I ran into something similar where dialog4ports would dump core after an= =20 > upgrade. Rebuilding the port (ports-mgmt/dialog4ports) solved it for me, >=20 > imb Thanks, recompilig ports-mgmt/dialog4ports solved the problem! I was sure t= hat after some ncurses changes in 14-CURRENT I've rebuilt every single port on all 14-CURR= ENT systems after that incident, bad luck. Thanks. oh --Sig_/pKvg+lh/Uqtr0traoqMY_l_ Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iHUEARYIAB0WIQSy8IBxAPDkqVBaTJ44N1ZZPba5RwUCYE0ohQAKCRA4N1ZZPba5 RwslAQDkxGKPpLUvS5gVdEliIEfxCOLDlg/g28IvcorNyfiL5wEA3CS+KLfn1Ivs HSlpLwNUCMATushsHJwPjOnJsryBWwk= =2yOi -----END PGP SIGNATURE----- --Sig_/pKvg+lh/Uqtr0traoqMY_l_--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20210313220301.28db1d0f>