From owner-freebsd-current@freebsd.org Thu Mar 18 13:46:10 2021 Return-Path: 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 83527575B6A; Thu, 18 Mar 2021 13:46:10 +0000 (UTC) (envelope-from agh@riseup.net) Received: from mx1.riseup.net (mx1.riseup.net [198.252.153.129]) (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-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "*.riseup.net", Issuer "Sectigo RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4F1Swf2fYrz3jSJ; Thu, 18 Mar 2021 13:46:10 +0000 (UTC) (envelope-from agh@riseup.net) Received: from fews1.riseup.net (fews1-pn.riseup.net [10.0.1.83]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.riseup.net", Issuer "Sectigo RSA Domain Validation Secure Server CA" (not verified)) by mx1.riseup.net (Postfix) with ESMTPS id 4F1Swc5f69zDq9H; Thu, 18 Mar 2021 06:46:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak; t=1616075168; bh=r017TePnngc1LL5URoBXVDdFsO9RkkczyyjGCdkVBAw=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=ZjzX5qHUTCj6W912c91DVjxFx6bGW6tcrvgaJU4RJIj+tFi+NKuJ5W2DcSkYrodd3 HVVFcOV1lDKTV2kFABfXkj17rfmBnIMXdC6DS7vumd01XDVlDp+A1nYtvDed4m3aLv NXqKDw8MQFd/kXg46zROQ0yftI+Hk5YoNWbvXiCE= X-Riseup-User-ID: 52DEEA7931687A69FA3658866A2B86BAF3769825C82FF9E40C6886900D15C046 Received: from [127.0.0.1] (localhost [127.0.0.1]) by fews1.riseup.net (Postfix) with ESMTPSA id 4F1Swc3K11z5wHD; Thu, 18 Mar 2021 06:46:08 -0700 (PDT) MIME-Version: 1.0 Date: Thu, 18 Mar 2021 06:46:08 -0700 From: Alastair Hogge To: Jamie Landeg-Jones Cc: o.hartmann@walstatt.org, freebsd-current@freebsd.org, bapt@freebsd.org, imb@protected-networks.net, current@freebsd.org Subject: Re: On 14-CURRENT: no ports options anymore? In-Reply-To: <202103181007.12IA7Vxg094800@donotpassgo.dyslexicfish.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> <20210313220301.28db1d0f@hermann.fritz.box> <202103181007.12IA7Vxg094800@donotpassgo.dyslexicfish.net> Message-ID: Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4F1Swf2fYrz3jSJ X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Mar 2021 13:46:10 -0000 On 2021-03-18 18:07, Jamie Landeg-Jones wrote: > "Hartmann, O." wrote: > >> On Sat, 13 Mar 2021 15:13:15 -0500 >> Michael Butler via freebsd-current 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 wrote: >> > > >> > >> >> > >> I had the same problem in console modeFiippo >> > >> On Saturday, March 13, 2021, 8:33:57 PM GMT+1, Stefan Esser >> > >> 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 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. > > This bit me a few years ago - in my case, the terminal type wasn't > recognised. If dialog4ports > doesn't run successfully, the error is ignored by the ports scripts. > This was on a new > install (hence the reason I hadn't yet installed my termcap), and it > meant that before I > noticed, quite a number of ports got installed without the options I wanted. > > Since then, I've patched bsd.port.mk with: > > --- bsd.port.mk.orig 2017-06-06 17:38:00.000000000 +0100 > +++ bsd.port.mk 2017-06-08 01:31:36.320294000 +0100 > @@ -4729,8 +4729,8 @@ > trap "${RM} $${TMPOPTIONSFILE}; exit 1" 1 2 3 5 10 13 15; \ > ${SETENV} ${D4P_ENV} ${SH} ${SCRIPTSDIR}/dialog4ports.sh > $${TMPOPTIONSFILE} || { \ > ${RM} $${TMPOPTIONSFILE}; \ > - ${ECHO_MSG} "===> Options unchanged"; \ > - exit 0; \ > + ${ECHO_MSG} "===> ERROR: Options unchanged"; \ > + exit 1; \ > }; \ > ${ECHO_CMD}; \ > if [ ! -e $${TMPOPTIONSFILE} ]; then \ > > I never submitted this patch, because the way it was written seemed > intentional. Maybe this should be reviewed? Something like that would be great, please can we get a more informative message? I was bitten by this a few times recently.