Re: Possible regressions with trunk autoconf (vs 2.71)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


For now I track the failures through a "meta-bug" in Fedora [1], and
create individual bugs for each package's maintainer individually as
the analysis progresses [2][3][4][5], and if the issue is assumed to
be on their side. Considering the amount of work, I leave the upstream
discussion to the respective package maintainers.

I have a bit more than 10 remaining failures to analyse. At the
current pace it'll take about 2 work weeks [assuming there is no
change in priorities and that uncovered problems have the same level
of complexity in average].
Anybody that wants to give a hand is welcome, we can use [1] to
distribute the tasks.

[2] krb5:
[3] am-utils:
[4] wine:
[5] anjuta:

On Fri, Nov 18, 2022 at 6:30 PM Sam James <sam@xxxxxxxxxx> wrote:
> > On 18 Nov 2022, at 07:11, Frederic Berat <fberat@xxxxxxxxxx> wrote:
> >
> > Thanks, I'll update the bug I opened for them.
> Could you share the links? Thanks.

[Index of Archives]     [GCC Help]     [Kernel Discussion]     [RPM Discussion]     [Red Hat Development]     [Yosemite News]     [Linux USB]     [Samba]

  Powered by Linux