HEADS-UP:
autoconf-2.71 is merged and built in Fedora rawhide together with the rest of autotools: automake-1.16-4.1 and libtool-2.4.6-43.
In the next few days, scratch-build for each dependent package will be executed and failed packages F36FTBFS trackers will be created.
Thank you all for your cooperation! Hopefully we will manage to bring this change to the end.
Ondrej
On Mon, Aug 30, 2021 at 10:45 AM Ian Kent <raven@xxxxxxxxxx> wrote:
On Mon, 2021-08-30 at 07:55 +0200, Ondrej Dubaj wrote:
> Hi,
>
> Thank you for the update Ian. It was not meant the way every packager
> is ignoring the opened issues, we appreciate your work on this
> autoconf-2.71 issue. Sorry for generalizing this.
And my comment was not meant to sound negative, getting an update
like this done is very challenging, to say the least, hopefully
everything will go well, ;)
Truth is I would have liked to get it done earlier but was unable
to, at least I have managed to get it done now.
>
> Glad to hear that it will build OK today.
>
> HEADS-UP:
>
> Starting with merging autoconf-2.71 changes. This week a scratch-
> build for all dependent packages will be executed. If you want to
> test your packages by yourself, you can execute your own scratch-
> build and see if it works properly. I will write here when autoconf-
> 2.71 will be stable.
>
> Thanks for your cooperation and hope to see very few failures this
> week :)
>
> Regards,
> Ondrej
>
> On Fri, Aug 27, 2021 at 2:36 PM Ian Kent <raven@xxxxxxxxxx> wrote:
> > On Tue, 2021-08-24 at 10:53 +0200, Ondrej Dubaj wrote:
> > > Hello,
> > >
> > > In the near future, there is a plan to merge autoconf-2.71 to
> > > rawhide. Due to the size of the change and possible breakage of
> > > multiple packages going FTBFS. The number of these packages
> > > should
> > > not be many, currently we have ~32 opened FTBFS trackers
> > > according
> > to
> > > autoconf-2.71, where the majority of them are just ignored by
> > > maintainers [1]. This can also be a possibility to remove
> > unnecessary
> > > packages from Fedora. After merging the change, there should be a
> > > mechanism for validating. From my perspective, it is effective to
> > > rebuild dependent packages (~1700 packages). After the rebuild,
> > there
> > > should not be many FTBFS packages, but according to the change
> > there
> > > will be some. There was enough time (~6 months) for the
> > > maintainers
> > > to prepare for this change.
> >
> > Not everyone is ignoring the bugs I have been working on the am-
> > utils
> > package for this.
> >
> > The package is very old and it utilizes autoconf very heavily.
> > Most of the autoconf noise is use of obsolete macros and I have
> > updated
> > this were I can but there are some things I simply can't fix and
> > some
> > things that shouldn't be changed.
> >
> > I'll keep coming back to it over time since the changes I have made
> > or
> > (rather will be committing over the weekend) do allow the package
> > to
> > build and function on F33 and build in the Copr updated autoconf
> > environment.
> >
> > I expect it will build ok on Monday.
> >
> > >
> > > If there are any concerns or other opinions about the steps after
> > > merging the change, please share your thoughts and we can discuss
> > > them here.
> > >
> > > Thanks very much!
> > >
> > > Regards,
> > > Ondrej
> > >
> > > [1] https://bugzilla.redhat.com/show_bug.cgi?id=1942967
> > >
> > > On Mon, Aug 16, 2021 at 7:52 AM Ondrej Dubaj <odubaj@xxxxxxxxxx>
> > > wrote:
> > > > Hello, according to the size of this change and the possible
> > > > breakage of multiple packages before f35 mass rebuild, we
> > > > decided
> > > > (team working on this change) to postpone this change to early
> > > > lifecycle of f36, where we will have enough time to resolve any
> > > > problems until f36 mass rebuild.
> > > >
> > > > On Mon, Aug 2, 2021 at 5:18 PM Kevin Fenzi <kevin@xxxxxxxxx>
> > wrote:
> > > > > On Thu, Mar 25, 2021 at 05:28:07PM +0100, Ondrej Dubaj wrote:
> > > > > > Currently, we are trying to stay away from the compat
> > > > > > package
> > > > > > and
> > > > > with the
> > > > > > help of other package maintainers trying to fix the
> > > > > > failures.
> > > > > > We
> > > > > will give
> > > > > > time to react accordingly and see other possible steps in a
> > few
> > > > > weeks time.
> > > > > >
> > > > > > Currently multiple FTBFS bugs in bugzilla were created
> > > > > > according
> > > > > to
> > > > > > autoconf-2.71. More information available here:
> > > > > >
> > > > > > https://fedoraproject.org/wiki/Changes/Autoconf_271
> > > > >
> > > > > Whats the current status of this Change?
> > > > >
> > > > > It didn't land before mass rebuild. Is it still planned for
> > f35?
> > > > >
> > > > > kevin
> > > > > _______________________________________________
> > > > > devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
> > > > > To unsubscribe send an email to
> > > > > devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
> > > > > 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@xxxxxxxxxxxxxxxxxxxxxxx
> > > > > Do not reply to spam on the list, report it:
> > > > > https://pagure.io/fedora-infrastructure
> > > _______________________________________________
> > > devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
> > > To unsubscribe send an email to
> > > devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
> > > 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@xxxxxxxxxxxxxxxxxxxxxxx
> > > Do not reply to spam on the list, report it:
> > > https://pagure.io/fedora-infrastructure
> >
> > _______________________________________________
> > devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
> > To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
> > 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@xxxxxxxxxxxxxxxxxxxxxxx
> > Do not reply to spam on the list, report it:
> > https://pagure.io/fedora-infrastructure
> _______________________________________________
> devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
> To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
> 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@xxxxxxxxxxxxxxxxxxxxxxx
> Do not reply to spam on the list, report it:
> https://pagure.io/fedora-infrastructure
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx 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@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
