Re: Delay in 14.0-RELEASE cycle and blocking items

Am 2023-05-15 um 22:36 schrieb Yuri:
> Yuri wrote:
>> Michael Osipov wrote:
>>> Am 2023-05-15 um 22:19 schrieb Yuri:
>>>> Michael Osipov wrote:
>>>>> Am 2023-05-15 um 21:37 schrieb Glen Barber:
>>>>>> On Mon, May 15, 2023 at 09:15:52PM +0200, Michael Osipov wrote:
>>>>>>> Glen,
>>>>>>>
>>>>>>> do you see any chance to get this finally merged:
>>>>>>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236204 ?
>>>>>>>
>>>>>>> It seriously affects people (in enterprises) behind a proxy, curl will
>>>>>>> be a problem and py-requests is already a serious problem.
>>>>>>>
>>>>>>
>>>>>> I have bumped the bug, and pinged sef@ and cc'd re@ as a result.
>>>>>>
>>>>>> I do not see a problem with it, as long as it is a proper fix.
>>>>>
>>>>> Thank you! I have verified the patch back then, will happily re-verify
>>>>> if requested to.
>>>>
>>>> I just tried this (without patching):
>>>>
>>>> $ cat ~/.login_conf
>>>> me:setenv=FOO=bar,BAR=baz,BAZ='foo,bar':
>>>> $ env | egrep 'FOO|BAR|BAZ'
>>>> BAZ=foo,bar
>>>> BAR=baz
>>>> FOO=bar
>>>
>>> Not in /etc/login.conf:
>>>> $ grep NO /etc/login.conf
>>>>          :setenv=BLOCKSIZE=K,LSCOLORS=ExGxFxdxCxDxDxhbadExEx,LESS=-x4
>>>> -R,EDITOR=vim,LANG=de_DE.UTF-8,CLICOLOR=YES,NO_PROXY='localhost,*.siemens.net':\
>>>> $ env | grep NO
>>>> NO_PROXY='localhost
>>
>> Weird, works for me running main-n262913-bee3d4bf8ed5:
>>
>> $ grep NO_PROXY /etc/login.conf
>>          :setenv=BLOCKSIZE=K,NO_PROXY='localhost,*.siemens.net':\
>> $ env | grep NO_PROXY
>> NO_PROXY=localhost,*.siemens.net
> 
> Oh, the fix is in there:
> 
> commit f32db406504ece1b28f43dc816736e081fe22826
> Author: Sean Eric Fagan <sef@FreeBSD.org>
> Date:   Sat Jan 14 10:37:31 2023 -0800
> 
>      Allow a comma-separated list in login class capabilities,
>      by adding a version of strcspn that allows quoting.
> 
> So what exactly are we talking about here? :-)

I am on 12-STABLE, and reported on that. Tried back than on 13, it was 
broken as well. You might want to try 14 with double quotes and see if 
it works. If at least one works, docs need to be updated for sure, and 
also make sure that in single quotes escapes like \c for colon still work.

I'll try a VM with a main snapshot as well tomorrow.

M