On Thu, Jul 19, 2018 at 6:13 PM Hans de Goede <hdegoede@redhat.com> wrote:
Hi,

On 19-07-18 17:42, Igor Gnatenko wrote:
> On Thu, Jul 19, 2018 at 5:33 PM Hans de Goede <hdegoede@redhat.com <mailto:hdegoede@redhat.com>> wrote:
>
>     Hi All,
>
>     I've just got 20 bugs auto-filed against packages which I co-maintain
>     and that is just for packages starting with the letter 'a'.
>
>     A quick check shows that these are all caused by a missing
>     BuildRequires on gcc / g++ related to:
>
>     https://fedoraproject.org/wiki/Changes/Remove_GCC_from_BuildRoot
>
>     I'm not sure if this means that the FTBFS script has been run before
>     all the automatic fixing which was planned for this was in place;
>     or if this means that the automatic fixing missed many many
>     packages, but either way something needs to happen here, the amount
>     of work now being pushed onto packagers caused by:
>
>     https://fedoraproject.org/wiki/Changes/Remove_GCC_from_BuildRoot
>
>     Is unacceptable IMHO.
>
>     If the FTBFS script has ran too early, all the FTBFS bugs need to be
>     closed and the FTBFS script has to be run again later.
>
>     If the automatic BuildRequires fixing script missed all these, then
>     I suggest that:
>
>     https://fedoraproject.org/wiki/Changes/Remove_GCC_from_BuildRoot
>
>     Gets reverted for now and we again close all the FTBFS bugs and
>     rerun the script for them after doing a fresh build with the
>     buildroot restored as it was.
>
>
> No one promised that I'm going to fix 100% of packages, I've fixed around 2k packages. What my regex couldn't catch -- please send me list of packages, I will analyze them and try to fix as much as possible.

Ok, thank you for offering to take a look at this. Here are the
FTBFS bugs which I've received so far, it seems that the bot
has stopped filing bugs after getting through all packages
starting with a-b? Or no packages which I co-maintain have
failed starting with c-z??

Anyways here is the list so far. Note I've not yet analyzed
these, so some might have a different cause, feel free to
leave those as is and I will get around to them eventually.

https://bugzilla.redhat.com/show_bug.cgi?id=1603260
https://bugzilla.redhat.com/show_bug.cgi?id=1603263
https://bugzilla.redhat.com/show_bug.cgi?id=1603266
https://bugzilla.redhat.com/show_bug.cgi?id=1603267
https://bugzilla.redhat.com/show_bug.cgi?id=1603274
https://bugzilla.redhat.com/show_bug.cgi?id=1603319
https://bugzilla.redhat.com/show_bug.cgi?id=1603321
https://bugzilla.redhat.com/show_bug.cgi?id=1603348
https://bugzilla.redhat.com/show_bug.cgi?id=1603351
https://bugzilla.redhat.com/show_bug.cgi?id=1603365
https://bugzilla.redhat.com/show_bug.cgi?id=1603366
https://bugzilla.redhat.com/show_bug.cgi?id=1603369
https://bugzilla.redhat.com/show_bug.cgi?id=1603383
https://bugzilla.redhat.com/show_bug.cgi?id=1603398
https://bugzilla.redhat.com/show_bug.cgi?id=1603410
https://bugzilla.redhat.com/show_bug.cgi?id=1603431
https://bugzilla.redhat.com/show_bug.cgi?id=1603456
https://bugzilla.redhat.com/show_bug.cgi?id=1603457
https://bugzilla.redhat.com/show_bug.cgi?id=1603503
https://bugzilla.redhat.com/show_bug.cgi?id=1603506

I've fixed regex a bit and fixed ~150 more packages.

I believe that the rest could be done by maintainers.
--

-Igor Gnatenko