Il giorno ven 13 lug 2018 alle 12:39, Igor Gnatenko
<ignatenkobrain@fedoraproject.org> ha scritto:
> On Fri, Jul 13, 2018, 11:19 Miro Hrončok <mhroncok@redhat.com> wrote:
>> On 8.7.2018 20:46, Igor Gnatenko wrote:
>> > As per Changes/Remove GCC from BuildRoot
>> >
>> <https://fedoraproject.org/wiki/Changes/Remove_GCC_from_BuildRoot>,
>> I'm
>> > going to automatically add BuildRequires: gcc and/or BuildRequires:
>> > gcc-c++ to packages which fail to build with common messages (like
>> gcc:
>> > command not found, also autotools/cmake/meson are supported).
>> >
>> > I'm going to do this tomorrow.
>> >
>> > After which, I'm going to ask rel-eng to finally remove it from
>> > buildroot. This will happen before mass rebuild. Stay tuned.
>> > --
>>
>> I've clicked randomly trough failures during the mass rebuild at [1].
>>
>> I see quite a lot of commands not founds for gcc, cc, c++...
>>
>> I think the maintainers should add them and that's fine, but it
>> seemed
>> that during this change you said you will add those. Did it happen?
>
> Yes, I've pushed over 2k commits adding those, however regexp might
> have not catched all possible cases. Would appreciate if you would
> link such packages so that I can fix them. Or maintainers can do it
> themselves.
>

I've just added  and pushed the needed BuildRequires for my package
(extractpdfmark).
I didn't bump the release version. Will you do it when you make a new
mass rebuild?

I see that on 3rd of July the build was successful (despite the missing
gcc-c++ requirement):
https://koji.fedoraproject.org/koji/buildinfo?buildID=1102851

Does it mean that the change in koji was implemented only recently?