Brian,

I understand, but as I already said, compat package can lead to unwillingness to move forward to autoconf-2.71. For example, we can have a compat package for f35 to have time to deal with the problems, but certainly not for f36 or f37. After release of autoconf-2.71, I expect most of the upstream packages moving to autoconf-2.71 in one year time, so hopefully no compat package will be needed.

Why are you not thinking of moving parted to autoconf-2.71 ? Are there any special reasons for not doing this?

Thanks.

Ondrej

On Wed, Feb 24, 2021 at 6:36 PM Brian C. Lane <bcl@redhat.com> wrote:
On Wed, Feb 24, 2021 at 08:14:17AM +0100, Ondrej Dubaj wrote:
> Brian,
>
> you are right there are some changes which are now backward compatible.
> That's the reason why we need cross-component cooperation from other
> maintainers to detect these pieces and potentially report them to upstream
> and see if they are willing to fix them. Another option is also to create a
> compat package for autoconf-2.69 for f35, but it can lead to a result,
> where some of the maintainers/upstreams will never use autoconf-2.71.

I think we need to create a 2.69 compat package. I certainly have no
current plans to switch upstream parted to 2.71 and while I now have a
wonderful 1.8M patch that fixes it for Fedora I'd rather just use the
upstream tar release with 2.69 until we're comfortable moving.

Having 2.71 available is valuable, so both should be packaged, but it
should not be a requirement at this point.

Brian

--
Brian C. Lane (PST8PDT) - weldr.io - lorax - parted - pykickstart