On Tue, 2018-11-20 at 14:52 -0800, Kevin Fenzi wrote:
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" and
have it work. If not, you can just resubmit your build until you get a
There are several packages like this, I think. It's a real pain. Is
there no better solution we can come up with?
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net