Hello,

debugging pungi can be a bit of pain. I usually end up by commenting pieces of code to be actually able to skip "un-skippable" which might fail in case that you're re-spinning just single phase and e.g. skipped. Writing treeinfo would fail for sure.

My advice here is to simply put phase dependent code from pungi-koji into end of given phase.

The result would be that pungi-koji only processes arguments and launches phases and marks compose as finished. No additional code is expected.

Also checksums could have separate "post" phase.
I'd keep latest-symlink in the code but, create option to skip it with default=False to not change behavior.

This would help with debugging individual phases in a way that you wouldn't have to touch binary at all.

Lubos