Huh, well, thats a pdc thing... ;(

@humaton can you look?

https://pagure.io/releng/fedora-scm-requests/issue/51086 is another case, this time on a rpm.

Just to be clear, because this has confused some folks, the lack of a f38 branch for container/fedora-toolbox means that we can't build separate f38 and f39 images.

ok. This should be fixed now, can you resubmit and confirm?

CC: @luya

ok. This should be fixed now, can you resubmit and confirm?

Thanks, @kevin

I submitted https://pagure.io/releng/fedora-scm-requests/issue/51121 and I see the branch in Git now.

Wait a minute -- I see that it created an empty f38 branch. Is that to be expected?

For containers? I am not sure...

Previous container/fedora-toolbox branches were definitely not created empty. They were split out from rawhide just as they are done for RPMs. See:
https://src.fedoraproject.org/container/fedora-toolbox/commits/f37
https://src.fedoraproject.org/container/fedora-toolbox/commits/f36

Perhaps a bug in the scm-processing script? @zlopez ^ can you take a look?

CC: @luya

The issue got resolved. I was able to create a f38 branch for f38-backgrounds.
https://pagure.io/releng/fedora-scm-requests/issue/51133

@kevin We should add to some SOP that the toddlers config need to be updated every time there is a new Fedora version branched.

@luya Was it created empty or from rawhide branch?

@luya Was it created empty or from rawhide branch?

Empty.

@kevin @zlopez do you recommend that we wait for the f38 branch to be re-created from rawhide? Or should we go ahead and populate it, and start pushing builds?

No, I don't think we are going to recreate branches... so I recommend you just merge main back to it (or whatever) and go on.

We can look and fix it going forward for new branches.

Okay!

This should all be fixed. It turned out to be a config in the new scm requests processing toddler that we didn't update at branching. ;(