Re: Fwd: Bug#992651: sharutils: stores wrong path to bash if built on merged-/usr system

libopts.m4 is not a sharutils source file. It will require a release of 
autogen and that requires re-engineering its configuration. 20 years of 
history in how it got configured finally couldn't be patched anymore. :(

SO: please apply your patch to your variation of the sources and be 
patient. :( Sorry.

P.S. It seems autogen already has this fix:

>   [while :
>   do
>       test -x "$POSIX_SHELL" && break
>       POSIX_SHELL=`which bash`
>       test -x "$POSIX_SHELL" && break
>       POSIX_SHELL=`which dash`
>       test -x "$POSIX_SHELL" && break
>       POSIX_SHELL=/usr/xpg4/bin/sh
>       test -x "$POSIX_SHELL" && break
>       POSIX_SHELL=`/bin/sh -c '
>           exec 2>/dev/null
>           if ! true ; then exit 1 ; fi
>           echo /bin/sh'`
>       test -x "$POSIX_SHELL" && break
>       ]AC_MSG_ERROR([cannot locate a working POSIX shell])[
>   done]

back in 2016: 2016-09-05 09:57:30

On 7/21/22 16:05, Santiago Vila wrote:
> Hello.
> 
> I received the attached patch from the Debian bug system. It was taken 
> from sharutils git repository and it allows to pass a value for 
> POSIX_SHELL in the ./configure call. We need this for the usrmerge 
> transition.
> 
> I plan to apply the patch mostly "as is" to the Debian source package, 
> but as a result, I have to regenerate autoconf files during the package 
> build. Some people do that as a normal thing, but I prefer to do that 
> only when it's really necessary, so it would be more simple if there was 
> a new sharutils release from upstream. Are there any plans for that?
> 
> After all, the last release was made in 2015, and there are even some 
> CVE which are still not part of the last stable release.
> 
> Thanks.