Bug#976518: gsound: FTBFS: Unescaped left brace in regex is passed through in regex; marked by <-- HERE in m/^${ <-- HERE abs_top_builddir}/gsound$/ at /usr/bin/automake line 5755.

[Lucas Nussbaum]

Source: gsound
Version: 1.0.2-4
Severity: serious
Justification: FTBFS on arm64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201205 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on arm64 (I don't know if it also fails on amd64).

Relevant part (hopefully):
>  debian/rules build
> dh build
>    dh_update_autotools_config
>    dh_autoreconf
> libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'build-aux'.
> libtoolize: copying file 'build-aux/ltmain.sh'
> libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
> libtoolize: copying file 'm4/libtool.m4'
> libtoolize: copying file 'm4/ltoptions.m4'
> libtoolize: copying file 'm4/ltsugar.m4'
> libtoolize: copying file 'm4/ltversion.m4'
> libtoolize: copying file 'm4/lt~obsolete.m4'
> libtoolize: Consider adding '-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
> configure.ac:14: installing 'build-aux/compile'
> configure.ac:10: installing 'build-aux/missing'
> gsound/Makefile.am: installing 'build-aux/depcomp'
> Unescaped left brace in regex is passed through in regex; marked by <-- HERE in m/^${ <-- HERE abs_top_builddir}/gsound$/ at /usr/bin/automake line 5755.
> autoreconf: automake failed with exit status: 255
> dh_autoreconf: error: autoreconf -f -i returned exit code 1
> make: *** [debian/rules:7: build] Error 25

The full build log is available from:
   http://qa-logs.debian.net/2020/12/05/gsound_1.0.2-4_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with me
so that we can identify if something relevant changed in the meantime.

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.