CC: @adamwill

I think this is an unintended outcome of https://pagure.io/pungi/pull-request/1790 which reordered the phases so that there's less waiting. But apparently some of the waiting was actually needed there.

This obviously needs to be fixed, but ideally in a way that does not introduce the original slowdown.

I have a proof-of-concept for fixing this in #1817. However, it adds a completely new concept to Pungi: until now, any dependencies were handled on a phase level.

An alternative approach more in line with the existing code base would be to split the ostree related parts of osbuild into a separate phase and order that as needed. This might even work with no changes to the configuration.

An alternative approach more in line with the existing code base would be to split the ostree related parts of osbuild into a separate phase and order that as needed. This might even work with no changes to the configuration.

Is it acceptable that just reorder ostree and ostree installer phases?
https://pagure.io/fork/hlin/pungi/blob/ostree/f/doc/_static/phases.png

Yeah, that should have all of the dependencies set correctly. It may introduce some slowdown, but that may be the required price to pay for now.

I had one more idea on a solution: split OSBuild into two phases, one handling the images consuming some ostrees, and one for images with no ostree, and then ordering that. But it isn't simple either and looked very convoluted.

Yeah, that should have all of the dependencies set correctly. It may introduce some slowdown, but that may be the required price to pay for now.

Agree and let's try this way first.

I had one more idea on a solution: split OSBuild into two phases, one handling the images consuming some ostrees, and one for images with no ostree, and then ordering that. But it isn't simple either and looked very convoluted.

Commit b3e0b6d7 fixes this issue

Commit b3e0b6d7 fixes this issue

Sorry for the late reply, thanks kindly for fixing this.

Will it be built for F41 (iot compose host is on F41).

Here's an update: https://bodhi.fedoraproject.org/updates/FEDORA-2025-690c75a93a

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

Please continue any further discussion there.