Re: Koji / epel-7 - What's going on?

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

 



On 11/26/18 1:59 AM, Mikolaj Izdebski wrote:
> On Sat, Nov 24, 2018 at 8:08 PM Kevin Fenzi <kevin@xxxxxxxxx> wrote:
>>
>> On 11/21/18 3:11 AM, Vít Ondruch wrote:
>>>
>>> Dne 20. 11. 18 v 23:52 Kevin Fenzi napsal(a):
>>> Was this resolved?
>>>
>>> https://pagure.io/releng/issue/7671
>>
>> I thought so, but the builds there have their logs cleaned up and the
>> devel spec no longer has this in it.
>> I tried a test package that I scratch built and it seemed to work fine.
>> (ie, when I had ExclusiveArch: noarch aarc64 it always went to a aarch64
>> builder).
> 
> "ExclusiveArch: aarch64" works while "ExclusiveArch: x86_64" does not.
> The problem is that Koji may try to build packages with
> "ExclusiveArch: x86_64" in i386 chroot. This is not fixed AFAIK. A fix
> would be splitting x86_64/i386 hosts into two distinct groups and
> assigning exactly one arch to each builder.

That seems very odd to me. Do you have an example build of this?

Shouldn't mock pass the right thing here?

kevin


Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx

[Index of Archives]     [Fedora Development]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [KDE Users]

  Powered by Linux