At present diskimage-builder doesn't maintain any stable backport branches and just releases from master, but we should at least tag a 2.5.0 release immediately (not 2.4.1 since there are some new dependency exclusions/minimums in master since 2.4.0).
I'll leave it to the DIB developers to determine whether this bug warrants creating new backport branches (especially from a release that is now nearly 1.5 years old).
At present diskimage-builder doesn't maintain any stable backport branches and just releases from master, but we should at least tag a 2.5.0 release immediately (not 2.4.1 since there are some new dependency exclusions/minimums in master since 2.4.0).
I'll leave it to the DIB developers to determine whether this bug warrants creating new backport branches (especially from a release that is now nearly 1.5 years old).