1. Considering the code, I suspect it was introduced during the golang rewrite (and it may also have been an issue with previous python version, but I do not really know much about them).
2. I do not think we moved the build of some images from ubuntu-image back to "full" livecd-rootfs. So I do not think any released images are affected. But I agree that would be problematic.
Be careful when checking "what" is building the image, because livecd-rootfs calls ubuntu-image, so both can be used in some cases.
Regarding missing packages, this may not be bug in ubuntu-images but something missing in the image definition (a package not explicitly listed?) or something wrong in the seed.
1. Considering the code, I suspect it was introduced during the golang rewrite (and it may also have been an issue with previous python version, but I do not really know much about them).
2. I do not think we moved the build of some images from ubuntu-image back to "full" livecd-rootfs. So I do not think any released images are affected. But I agree that would be problematic.
Be careful when checking "what" is building the image, because livecd-rootfs calls ubuntu-image, so both can be used in some cases.
Regarding missing packages, this may not be bug in ubuntu-images but something missing in the image definition (a package not explicitly listed?) or something wrong in the seed.