Fedora CI - scratch build on rawhide still builds on Fedora 37.

Yes, this is the case. Should be easier to fix than the opposite problem.

Hi, I have updated the image to latest available rawhide.

Although the image has some troubles: https://pagure.io/fedora-infrastructure/issue/10851

But seems it is not a blocker. Can you retry your testing somehow @churchyard ?

I've poked this rawhide PR:

https://src.fedoraproject.org/rpms/pyproject-rpm-macros/pull-request/310

And opened this f37 PR:

https://src.fedoraproject.org/rpms/pyproject-rpm-macros/pull-request/311

But I cannot test this, considering https://pagure.io/fedora-ci/general/issue/361 and https://pagure.io/fedora-ci/general/issue/362

@churchyard looks to me all resolved now, closing

I'm not quite sure e.g. Zuul even responds to f37 PRs.

ah right zuul, unfinished bussiness ...

Hello,
Right,

• https://pagure.io/fedora-project-config/pull-request/217
• https://pagure.io/fedora-zuul-jobs-config/pull-request/167
• https://pagure.io/fedora-zuul-jobs/pull-request/158

need to be merged. However we need to get cloud-fedora-37 and zuul-worker-f37 labels available before merging changes above. I'll propose the required changes today and manage to get them merged ASAP.

cloud-fedora-37 labels are now available https://fedora.softwarefactory-project.io/zuul/labels

Next step is the container zuul-worker-f37.

Support for zuul-worker-f37 merged this morning and all PRs to support f37 branch have been merged.

Here is a change that have passed CI on the f37 branch: https://src.fedoraproject.org/rpms/python-gear/pull-request/54

Then I think this issue could be closed ?

Thanks @fbo

@churchyard can you pls confirm?

I've opened:

https://src.fedoraproject.org/rpms/pyproject-rpm-macros/pull-request/324
https://src.fedoraproject.org/rpms/pyproject-rpm-macros/pull-request/325

And will report back. I will check how are the scratchbuilds built and where the tests are executed.

• Fedora CI - scratch build run on f38 and f37. Due to Pagure UX limitations, I cannot tell which was run on which but I am pretty sure it was correct.
• Fedora CI - dist-git test run on Fedora Linux 38 and Fedora Linux 38. This is wrong.
• The Zuul's rpm-scratch-build run on rawhide for rawhide and f37 for f37, this is correct.
• The Zuul's rpm-test run on Fedora Linux 38 for rawhide and on Fedora Linux 37 on f37, this is also correct.
• The Zuul's rpm-sti-test run on Fedora Linux 38 for rawhide and on Fedora Linux 37 on f37, this is also correct.

tl;dr Zuul is done (thank you!) but Fedora CI - dist-git test is not.

@churchyard Fedora CI - dist-git test run on Fedora Linux 38 and Fedora Linux 38. This is wrong. ?

can you epxand on this with an example? I got lost. I am in the belief Fedora Linux 38 = Rawhide?

Fedora CI - dist-git test run on Fedora Linux 38 and Fedora Linux 38. This is wrong.

Ouch, this is an oversight on my part. Fixed in https://github.com/fedora-ci/dist-git-pipeline/pull/47. Sorry!

Fedora Linux 38 = Rawhide != Fedora 37

Shall I test again? Or is the fix awaiting some kind of release or deployment?

Shall I test again? Or is the fix awaiting some kind of release or deployment?

The changes took effect once the PR was merged. So you are good to go and test ;)

Thanks @msrb

Seems to work fine, although impossible to see if f38/f37 aren't the other way around due to Pagure bad UX. I consider that unlikely, considering how the fix looks like.

Thanks.

Follow-up: f37 Zuul should not run rpm-scratch-build-armv7hl
https://pagure.io/fedora-ci/general/issue/367