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

[Frantisek Zatloukal]

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

[Kevin Fenzi]

Post by Frantisek Zatloukal
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" and
have it work. If not, you can just resubmit your build until you get a
x86_64 builder.

kevin

[Frantisek Zatloukal]

Post by Frantisek Zatloukal

Post by Frantisek Zatloukal
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)

Post by Frantisek Zatloukal
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

Post by Frantisek Zatloukal
[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" and
have it work. If not, you can just resubmit your build until you get a
x86_64 builder.
kevin
_______________________________________________
To unsubscribe send an email to
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines

I'll try it, thanks for the quick reply!

[Vít Ondruch]

Post by Kevin Fenzi

Post by Frantisek Zatloukal
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.

Post by Kevin Fenzi
and
have it work. If not, you can just resubmit your build until you get a
x86_64 builder.
kevin
_______________________________________________
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines

[Kevin Fenzi]

Post by Vít Ondruch

Post by Kevin Fenzi

Post by Frantisek Zatloukal
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

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).

Can you try again and let us know if you still hit something?

kevin

[Mikolaj Izdebski]

Post by Kevin Fenzi

Post by Vít Ondruch
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.

[Kevin Fenzi]

Post by Mikolaj Izdebski

Post by Kevin Fenzi

Post by Vít Ondruch
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

[Mikolaj Izdebski]

Post by Kevin Fenzi

Post by Mikolaj Izdebski
"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?

Example task: https://koji.stg.fedoraproject.org/koji/taskinfo?taskID=90003488
Package has "ExclusiveArch: x86_64", buildArch task has correct "Arch
x86_64", yet the build is ran in i386 chroot (see root.log) and fails
with "error: Architecture is not included: i386".

Post by Kevin Fenzi
Shouldn't mock pass the right thing here?

This is a bug in Koji, not mock.

[Adam Williamson]

Post by Kevin Fenzi

Post by Frantisek Zatloukal
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" and
have it work. If not, you can just resubmit your build until you get a
x86_64 builder.

There are several packages like this, I think. It's a real pain. Is
there no better solution we can come up with?
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
_______________________________________________
infrastructure mailing list -- ***@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-***@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