Hi Sergei,

On Thu, Feb 27, 2025 at 11:23:54AM +0000, Sergei Trofimovich wrote:

Aha, I wonder if it's also related to the escaping behaviour of `sh` and `bash.

sh(1) shouldn't matter, because the I explicitly request bash(1) in the
makefiles.

	$ grep -rn SHELL GNUmakefile 
	5:SHELL       := bash
	6:.SHELLFLAGS := -Eeuo pipefail -c

Here are my tool versions:

    $ sh --version
        GNU bash, version 5.2.37(1)-release (x86_64-pc-linux-gnu)
        Copyright (C) 2022 Free Software Foundation, Inc.
        License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
        
        This is free software; you are free to change and redistribute it.
        There is NO WARRANTY, to the extent permitted by law.

	alx@debian:~$ which sh
	/usr/bin/sh
	alx@debian:~$ which sh | xargs dpkg -S
	dash: /usr/bin/sh
	alx@debian:~$ which sh | xargs dpkg -S | cut -f1 -d: | xargs dpkg -l | tail -n1
	ii  dash           0.5.12-12    amd64        POSIX-compliant shell

(But as said, this shouldn't matter.)

    $ bash --version
        GNU bash, version 5.2.37(1)-release (x86_64-pc-linux-gnu)
        Copyright (C) 2022 Free Software Foundation, Inc.
        License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
        
        This is free software; you are free to change and redistribute it.
        There is NO WARRANTY, to the extent permitted by law.

	$ bash --version
	GNU bash, version 5.2.37(1)-release (x86_64-pc-linux-gnu)
	Copyright (C) 2022 Free Software Foundation, Inc.
	License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>

	This is free software; you are free to change and redistribute it.
	There is NO WARRANTY, to the extent permitted by law.

Could you please try to find out the cause of the actual problem?  Maybe
there's a fix that doesn't involve reverting that patch.  Or maybe
there's a bug in some tool, and we can report it.


Cheers,
Alex

-- 
<https://www.alejandro-colomar.es/>