Your package fails to build with the newest upcoming autoconf-2.71, which is part of a wide Fedora change. Please see the attached copr: https://copr.fedorainfracloud.org/coprs/odubaj/autoconf-2.70/packages/. More information about testing your package when building with autoconf available here: https://fedoraproject.org/wiki/Changes/Autoconf_271#How_To_Test
I have opened a MR at [0] to test something. However, that doesn't seem to be picked up in the rebuilds, as far as I can tell. Besides that, this is the among worst testing workflows I have seen: Do something. Commit. Open MR. Wait random amount of time (days to weeks) for rebuild to kick in. Is there some way to test this in mock/container? Otherwise I am afraid I will not have this fixed in time for F36, and certainly not in time for when you intend to land this in rawhide. Especially as autotools are hard to debug, I often need hundreds of tries, which means years of work with this workflow ... Another option would be preview package for F33, which would allow for fast testing ...
Forgot the links: [0] https://src.fedoraproject.org/rpms/bout++/pull-request/2 Rebuilds: [1] https://copr.fedorainfracloud.org/coprs/odubaj/autoconf-2.70/package/bout%2B%2B/ Log: [2] https://download.copr.fedorainfracloud.org/results/odubaj/autoconf-2.70/fedora-rawhide-x86_64/02095120-bout++/build.log.gz
We do not have the tooling to make this testing easy for package maintainers. We are providing copr repository, where you can check your builds and also download appropriate mock-config for local builds: copr mock-config odubaj/autoconf-2.70 fedora-rawhide-x86_64
I have pushed the necessary changes: https://src.fedoraproject.org/rpms/bout++/commits/rawhide