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

2021-03-22 Thread John Baldwin 

On 3/13/21 12:58 PM, Guido Falsi via freebsd-current wrote:

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.


There was an ABI breakage for ncurses that broke 12.x dialog4ports binaries.
The shared library versions for everything that depended on ncurses were bumped
for 13 and 14 after the branch of stable/13.0 (commit 6e1fe6d26ea2).  After
that commit, if you upgraded from 12 to 13 you should have been fine, but if
you had updated before that, the 12.x dialog4ports was still going to fail
as the 12.x version of those libraries were already broken.  I haven't checked
to see if the affected libraries have been added to misc/compat12x.

--
John Baldwin
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

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

2021-03-18 Thread Alastair Hogge 
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 + (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.orig2017-06-06 17:38:00.0 +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.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

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

2021-03-18 Thread Jamie Landeg-Jones 
"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 + (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.orig2017-06-06 17:38:00.0 +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?

Cheers,
  Jamie

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

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

2021-03-14 Thread Dan Mahoney (Ports) 
If this isn’t at least in /usr/ports/UPDATING it sure should be.

-Dan

> On Mar 13, 2021, at 12:58 PM, Guido Falsi via freebsd-ports 
>  wrote:
> 
> 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 
> ___
> freebsd-po...@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

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

2021-03-14 Thread Dan Mahoney (Ports) 
You mention release notes.  Slightly off-topic, but I never understood why, if 
there was a beta or RC available, the release-notes of the time weren’t 
available on www.freebsd.org .

Wouldn’t that make sense to see if there were things you wanted to try out and 
test?

Anyway, more on topic, it seems that if one is on -CURRENT (or possibly 
-STABLE), you’re building from source, and should be expected to read UPDATING. 
 That much is on the site.  (But that would be /usr/src, not /usr/ports).

Did this happen mid-line in a stable?  That…shouldn’t.

-Dan

> On Mar 13, 2021, at 3:48 PM, Kevin Oberman  wrote:
> 
> On Sat, Mar 13, 2021 at 2:51 PM Dan Mahoney (Ports) 
> wrote:
> 
>> If this isn’t at least in /usr/ports/UPDATING it sure should be.
>> 
>> -Dan
>> 
> Ditto! While it did not take me long to discover that the ncurses shareable
> had bumped the version, I wasted a lot of time rebuilding ports one by one.
> At least a heads-up would have been nice. The way to do this is unclear,
> though, as it was a base library update. I assume that it only bit those
> running current or 13. Those running 13-STABLE, as I was, had no warning.
> I'm not sure a note in UPDATING would have been appropriate, but a post to
> stable@ and current@ would have been nice. Or, did I miss them?
> 
> This would also be made VERY clear in the 13.0 Release Notes. I suspect
> installing misc/compat12x would have worked.
> --
> Kevin Oberman, Part time kid herder and retired Network Engineer
> E-mail: rkober...@gmail.com
> PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
> ___
> freebsd-po...@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

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

2021-03-13 Thread Nuno Teixeira 
I have same problem days ago when dialog4ports crashed.

just reinstall/install ports-mgmt/dialog4ports/

Hartmann, O.  escreveu no dia sábado, 13/03/2021
à(s) 19:17:

> 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?
>
> Thanks in advance,
>
> O. Hartmann
>
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

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

2021-03-13 Thread Kevin Oberman 
On Sat, Mar 13, 2021 at 2:51 PM Dan Mahoney (Ports) 
wrote:

> If this isn’t at least in /usr/ports/UPDATING it sure should be.
>
> -Dan
>
Ditto! While it did not take me long to discover that the ncurses shareable
had bumped the version, I wasted a lot of time rebuilding ports one by one.
At least a heads-up would have been nice. The way to do this is unclear,
though, as it was a base library update. I assume that it only bit those
running current or 13. Those running 13-STABLE, as I was, had no warning.
I'm not sure a note in UPDATING would have been appropriate, but a post to
stable@ and current@ would have been nice. Or, did I miss them?

This would also be made VERY clear in the 13.0 Release Notes. I suspect
installing misc/compat12x would have worked.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

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

2021-03-13 Thread Hartmann, O. 
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 + (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 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



pgpqPaQfQcE_H.pgp
Description: OpenPGP digital signature

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

2021-03-13 Thread Guido Falsi via freebsd-current 

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 
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

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

2021-03-13 Thread Filippo Moretti via freebsd-current 
 > Rebuilding the port (ports-mgmt/dialog4ports) solved it for me,for me too
Thank youFilippo

On Saturday, March 13, 2021, 9:13:46 PM GMT+1, Michael Butler via 
freebsd-current  wrote:  
 
 On 3/13/21 3:00 PM, Hartmann, O. wrote:
> On Sat, 13 Mar 2021 19:52:47 + (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 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


___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
  
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

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

2021-03-13 Thread Michael Butler via freebsd-current 

On 3/13/21 3:00 PM, Hartmann, O. wrote:

On Sat, 13 Mar 2021 19:52:47 + (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 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


___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

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

2021-03-13 Thread Hartmann, O. 
On Sat, 13 Mar 2021 19:52:47 + (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 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)



pgpXNgfVCDPYU.pgp
Description: OpenPGP digital signature

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

2021-03-13 Thread Filippo Moretti via freebsd-current 
 
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 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

  
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

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

2021-03-13 Thread Stefan Esser 

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



OpenPGP_signature
Description: OpenPGP digital signature

On 14-CURRENT: no ports options anymore?

2021-03-13 Thread 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?

Thanks in advance,

O. Hartmann


pgpKk8C3idJx6.pgp
Description: OpenPGP digital signature