Comment 5 for bug 1977888

We did drop this, some comments in [1]. I was a little concerned that we'd hit something like this, we did hold off on merging similar some time ago, but with the Zed release it seemed more like something we could take on.

Due to our branchless nature, we don't really have a way to keep this going separately. However I can understand that running from master dib is also important because sometimes upstream things change that we fix -- so often fixes aren't really new features in dib, but just keeping what is going working.

I don't know what the answer is ... we *can* keep the 3.6 jobs and revert the removal (and keep the 3.10) -- it's not like we use a ton of python features. But also it's an obsolete python ... I haven't released dib yet, and won't until we come to some sort resolution.

Can train pin to the prior dib release?

[1] https://review.opendev.org/c/openstack/diskimage-builder/+/836229