On 11/20/18 2:39 PM, Frantisek Zatloukal wrote:

Hi,
I am currently trying to build new resultsdb[0] 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 [1]. However, it is failing on
not-available python-flask in koji to epel-7-candidate [2].

Am I overlooking something?

Thanks very much!

[0] https://src.fedoraproject.org/rpms/resultsdb/blob/epel7/f/resultsdb.spec
[1] https://koji.fedoraproject.org/koji/taskinfo?taskID=31025152
[2] 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?

https://pagure.io/releng/issue/7671

V.

and
have it work. If not, you can just resubmit your build until you get a
x86_64 builder.

kevin

_______________________________________________
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-leave@lists.fedoraproject.org
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@lists.fedoraproject.org