On 07/10/2018 03:36 AM, Igor Gnatenko wrote:
> On Tue, Jul 10, 2018 at 12:22 PM Vít Ondruch <vondruch(a)redhat.com> wrote:
>
>> Thank you for pushing this forward!
>>
>>
>> One question though. I see that this works in Koji, but trying to test
>> this locally it does not work.
>>
>> 1) $ mock -r fedora-rawhide-x86_64 rubygem-abrt-0.3.0-3.fc29.src.rpm
>> --enablerepo=local
>>
>> This still installs gcc.
>>
>> 2) $ mock -r fedora-rawhide-x86_64 rubygem-abrt-0.3.0-3.fc29.src.rpm
>> --disablerepo=* --enablerepo=local
>>
>> This fails:
>>
>> ~~~
>>
>> Warning: Module or Group 'buildsys-build' does not exist.
>> Error: Nothing to do.
>>
>> ~~~
>>
>> Trying to get the latest comps from local repository:
>>
>> ~~~
>>
>>
>>
https://kojipkgs.fedoraproject.org/repos/rawhide/latest/x86_64/repodata/d...
>>
>> ~~~
>>
>> This has "build" group which references gcc/gcc-c++ and does not
reference
>> any buildsys-build group. So where is this file coming from? Why does it
>> differ from regular Fedora repos?
>>
> This is interesting question. I've sent PR to update comps
> <
https://pagure.io/fedora-comps/c/0138de79f5f508784a0be01e57ff28eb293f022c>,
> but I don't know how it is being pushed through… We should ask rel-eng to
> help with this.
>
> Mohan, Kevin?
Looks like Mohan merged it a while back now...
The question is not about Fedora comps, but about comps from the Koji
repository:
Where are these coming from? How to fix them? I'd love to see the
examples above to behave correctly, i.e. to not install gcc.
I opened releng ticket to track this: