It seems we commited the config to auto sign the tag, but it never got deployed. ;( Thats likely my dropping the ball there, so sorry.

I'm merging it now and will sign everything. Hopefully it won't take too long.

Once the merging is done, usually builds that were built in the meantime in rawhide take precedence. One of them will be kernel (kernel-6.16.0-0.rc1.17.fc43 currently, or newer later). I am not firing a new kernel build to mitigate this (I don't have permissions and I don't want to play Whack-a-Mole). After the merge is done, we need to manually tag in the Python 3.14 build of kernel (kernel-6.16.0-0.rc0.250605gec7714e494790.13.fc43.1) to avoid noninstallable packages from composed media. The next kernel rebuild after the merge will be back on track.

ok, done.

kernel was the only package that was newer in f43 tag.

I retagged the build indicated.

I see https://koji.fedoraproject.org/koji/buildinfo?buildID=2731301 was built after the side tag was merged. I manually tagged it into f43-updates-candidate.

Can we ensure no more builds will follow? Aka disable/delete the tag?

E.g. https://koji.fedoraproject.org/koji/taginfo?tagID=f39-python says No build targets.

But f41-python and f43-python seem to still be buildable in.

Sorry about that. I have removed those targets now.

Thanks.