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.
From: Simon McVittie <s...@debian.org> Date: Sat, 21 Aug 2021 19:19:03 +0100 Subject: libopts.m4: accept POSIX_SHELL from the environment during the configure step This lets us set it to the canonical path /bin/bash, even on systems where both /bin/bash and /usr/bin/bash are available, and therefore which(1) might return /usr/bin/bash (depending on PATH order). Both copies of libopts.m4 are marked as generated files, but the files from which they were generated do not seem to be present in the sharutils package. This change is equivalent to part of a 2016 autogen commit <https://git.savannah.gnu.org/cgit/autogen.git/commit/?id=db064b9a>. Origin: https://git.savannah.gnu.org/cgit/autogen.git/commit/?id=db064b9a --- libopts/m4/libopts.m4 | 1 + m4/libopts.m4 | 1 + 2 files changed, 2 insertions(+) --- a/libopts/m4/libopts.m4 +++ b/libopts/m4/libopts.m4 @@ -114,6 +114,7 @@ AC_PROG_SED [while : do + test -x "$POSIX_SHELL" && break POSIX_SHELL=`which bash` test -x "$POSIX_SHELL" && break POSIX_SHELL=`which dash` --- a/m4/libopts.m4 +++ b/m4/libopts.m4 @@ -114,6 +114,7 @@ AC_PROG_SED [while : do + test -x "$POSIX_SHELL" && break POSIX_SHELL=`which bash` test -x "$POSIX_SHELL" && break POSIX_SHELL=`which dash`
