Date: Sat, 13 Mar 2021 20:27:23 +0000 (UTC) From: Filippo Moretti <filippomore@yahoo.com> To: FreeBSD Current <current@freebsd.org> Subject: Re: On 14-CURRENT: no ports options anymore? Message-ID: <522683978.652277.1615667243487@mail.yahoo.com> 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
> Rebuilding the port (ports-mgmt/dialog4ports) solved it for me,for me to=
o
Thank youFilippo
On Saturday, March 13, 2021, 9:13:46 PM GMT+1, Michael Butler via freeb=
sd-current <freebsd-current@freebsd.org> wrote: =20
=20
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
>>=C2=A0=20
>> I had the same problem in console modeFiippo
>>=C2=A0 =C2=A0 =C2=A0 On Saturday, March 13, 2021, 8:33:57 PM GMT+1, Stefa=
n Esser <se@freebsd.org> wrote:
>>
>>=C2=A0 Am 13.03.21 um 20:17 schrieb Hartmann, O.:
>>> Since I moved on to 14-CURRENT, I face a very strange behaviour when tr=
ying 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 m=
enu).
>>> This misbehaviour is throughout ALL 14-CURRENT systems (the oldest is a=
t FreeBSD
>>> 14.0-CURRENT #49 main-n245422-cecfaf9bede9: Fri Mar 12 16:08:09 CET 202=
1 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
>=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
> =3D=3D=3D> Options unchanged (no menu popping up)
>=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,
=C2=A0=C2=A0=C2=A0 imb
_______________________________________________
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
=20
From owner-freebsd-current@freebsd.org Sat Mar 13 20:58:34 2021
Return-Path: <owner-freebsd-current@freebsd.org>
Delivered-To: freebsd-current@mailman.nyi.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
by mailman.nyi.freebsd.org (Postfix) with ESMTP id 56B935AB4D4;
Sat, 13 Mar 2021 20:58:34 +0000 (UTC)
(envelope-from mad@madpilot.net)
Received: from mail.madpilot.net (vogon.madpilot.net [159.69.1.99])
(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256)
(Client did not present a certificate)
by mx1.freebsd.org (Postfix) with ESMTPS id 4DyZls3DD4z3PqC;
Sat, 13 Mar 2021 20:58:33 +0000 (UTC)
(envelope-from mad@madpilot.net)
Received: from mail (mail [192.168.254.3])
by mail.madpilot.net (Postfix) with ESMTP id 4DyZlk0DQ3z6dPY;
Sat, 13 Mar 2021 21:58:26 +0100 (CET)
Received: from mail.madpilot.net ([192.168.254.3])
by mail (mail.madpilot.net [192.168.254.3]) (amavisd-new, port 10026)
with ESMTP id fMdlHw3GC5J2; Sat, 13 Mar 2021 21:58:24 +0100 (CET)
Subject: Re: On 14-CURRENT: no ports options anymore?
To: "Hartmann, O." <ohartmann@walstatt.org>,
FreeBSD Ports <freebsd-ports@freebsd.org>
Cc: FreeBSD CURRENT <freebsd-current@freebsd.org>
References: <20210313201702.5f9dfa9b@hermann.fritz.box>
From: Guido Falsi <mad@madpilot.net>
Message-ID: <8a39cc8f-df2b-8a43-54c4-44eebb4b12de@madpilot.net>
Date: Sat, 13 Mar 2021 21:58:23 +0100
In-Reply-To: <20210313201702.5f9dfa9b@hermann.fritz.box>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-Rspamd-Queue-Id: 4DyZls3DD4z3PqC
X-Spamd-Bar: /
X-Spamd-Result: default: False [-0.76 / 15.00]; MID_RHS_MATCH_FROM(0.00)[];
RBL_DBL_DONT_QUERY_IPS(0.00)[159.69.1.99:from];
R_DKIM_ALLOW(-0.20)[madpilot.net:s=bjowvop61wgh];
ARC_NA(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3];
MISSING_MIME_VERSION(2.00)[]; R_SPF_ALLOW(-0.20)[+mx];
MIME_GOOD(-0.10)[text/plain]; NEURAL_HAM_LONG(-1.00)[-1.000];
SPAMHAUS_ZRD(0.00)[159.69.1.99:from:127.0.2.255];
RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[];
TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[madpilot.net:+];
DMARC_POLICY_ALLOW(-0.50)[madpilot.net,quarantine];
NEURAL_HAM_SHORT(-0.76)[-0.763];
NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_EQ_ENVFROM(0.00)[];
MIME_TRACE(0.00)[0:+]; SUBJECT_ENDS_QUESTION(1.00)[];
ASN(0.00)[asn:24940, ipnet:159.69.0.0/16, country:DE];
RCVD_TLS_LAST(0.00)[];
MAILMAN_DEST(0.00)[freebsd-current,freebsd-ports]
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.34
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
<freebsd-current.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>;
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>,
<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 13 Mar 2021 20:58:34 -0000
On 13/03/21 20:17, Hartmann, O. wrote:
> 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?
I encountered something similar, some base shared library has changed,
guess this is related with the ncurses changes in base.
If I remember correctly force reinstalling dialog4ports package fixed
it. Make sure you reinstall a freshly rebuilt one.
Most probably anything using ncurses will require rebuild/reinstall.
The cause is dialog4ports failing to start and the system sees no option
changed.
If that's not enough try
# ldd -v /usr/local/bin/dialog4ports
And see if it reports some useful information.
--
Guido Falsi <mad@madpilot.net>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?522683978.652277.1615667243487>