On 11/21/18 3:11 AM, Vít Ondruch wrote:
Dne 20. 11. 18 v 23:52 Kevin Fenzi napsal(a):
> On 11/20/18 2:39 PM, Frantisek Zatloukal wrote:
>> I am currently trying to build new resultsdb into epel7-candidate.
>> However, I am facing some (weird?) behavior around python-flask,
>> I am able to do a successful build of resultsdb (depending on python-flask)
>> in mock epel-7 and koji scratch epel-7 . However, it is failing on
>> not-available python-flask in koji to epel-7-candidate .
>> Am I overlooking something?
>> Thanks very much!
>>  https://src.fedoraproject.org/rpms/resultsdb/blob/epel7/f/resultsdb.spec
>>  https://koji.fedoraproject.org/koji/taskinfo?taskID=31025152
>>  https://koji.fedoraproject.org/koji/taskinfo?taskID=31025187
> flask was pulled into rhel-extras (for docker distribution I think) and
> when it was, it was only published for x86_64.
> Your package is noarch, but flask is not.
> So, you happened to get a x86_64 builder with your scratch build, but
> your real build got a ppc builder where flask is not available. ;(
> I think you should be able to pass "Exclusivearch: noarch x86_64"
Was this resolved?
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
Can you try again and let us know if you still hit something?