Ping!

Hi, it is the same logic as for all other build types. E.g. you can build also rpm from uploaded srpm but most policies will forbid tagging such build anywhere near to end-product. Such build is not reproducible in a way "re-trigger same task without any additional input". Of course, we store such potentially uploaded kickstart, so it is not unimaginable.

So, it is technically possible, but nobody had a real use-case for that until now. @mikem anything to add?

Pull Request 3271 provides a solution for this request: https://pagure.io/koji/pull-request/3271

Simply cutting out the check is not a workable solution. Other build types that allow this give admins the option to control whether it is possible (e.g. build_from_srpm policy).

Unfortunately we have a lot of different build types with different code paths, so it would be good to give some thought toward the best way to make this consistent.

This case might give us something to think about in #3407

We're still interested in this feature, how can we move forward?

I've added policy checks in #3729. Let's discuss it if it is enough. I don't like it that much but it covers this usecase.

Commit 4ce5fc14 fixes this issue

Commit 0eedf36c relates to this ticket

Commit 721a97e7 fixes this issue

Commit 2ddfd5e9 relates to this ticket

This issue has been migrated to Fedora Forge:
https://forge.fedoraproject.org/koji/koji/issues/3183

Please continue any further discussion there.