Gentle ping.

(In reply to Ondrej Dubaj from comment #0)
> 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'm not seeing this problem... 

https://koji.fedoraproject.org/koji/taskinfo?taskID=66671882

The new autoconf-2.71 is available only in the mentioned copr repository, as we are currently only preparing for a rebase in fedora rawhide. Please see the change proposal and the logs [1] for more information about the failure.

[1] https://copr.fedorainfracloud.org/coprs/odubaj/autoconf-2.70/package/nfs4-acl-tools/

Hi, any updates here?

Thanks.

(In reply to Ondrej Dubaj from comment #4)
> Hi, any updates here?
> 

Doing the autoupdate does seem to correct
configure.ac file.. but since there is 
no Makefile.am automake fails.

There is what I'm trying

aclocal 
libtoolize --force --copy
autoheader
automake --add-missing --copy --gnu
autoconf # -Wall

Though the automake fails, I am still able to 
a build in the upstream tree... but because 
the automake fails build an fedora rpm fails.

Hello, this issue does not seem to be resolved, can you please check it one more time ? Soonly we are planning to move to autoconf-2.71, so there will be FTBFS on this component.

Thank you.

This bug appears to have been reported against 'rawhide' during the Fedora 35 development cycle.
Changing version to 35.

Autoconf-2.71 Fedora Change is completed. According to this, I am closing this tracker and if any FTBFS will appear in Fedora Rawhide, new F36FTBFS tracker will be created for this purposes, thank you for cooperation.