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.
If there are any packages, which are already orphaned, do not hesitate to
let me know and I will remove them. Also, if you are missing any package
there. Autoconf changes have a huge impact on the whole system, so it needs
to be properly tested and agreed.
Thanks for your cooperation!
Ondrej
On Wed, Feb 24, 2021 at 1:44 AM Jeff Law <law(a)redhat.com> wrote:
On 2/23/21 4:54 PM, Jerry James wrote:
> On Tue, Feb 23, 2021 at 4:52 PM Jeff Law <law(a)redhat.com> wrote:
>> On 2/23/21 4:39 PM, Brian C. Lane wrote:
>>> On Tue, Feb 23, 2021 at 11:37:42AM +0100, Ondrej Dubaj wrote:
>>>> [2]
http://torsion.usersys.redhat.com:8080/job/Fedora-autoconf/
>>> Doesn't work, with or without :8080
>> Not sure what you're referring to, it just worked fine for me.
> As Ondrej said: "Attaching also results from a tester launched by Jeff
> Law [2] (accessible only on Red Hat VPN)". Those of us without access
> to the Red Hat VPN cannot see those results.
But Brian is (or can be) inside the VPN. That's what I was referring to.
jeff
_______________________________________________
devel mailing list -- devel(a)lists.fedoraproject.org
To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure