** when a version is bumped such that the FILESDIR no longer matches it, the first sign of missing patches is during do_patch, when patch complains about missing files, rather than when the patches should have been copied from FILESDIR to the build area - that copy fails silectly ** when a package that an image depends on turns out to be empty, the image creation fails; in the case I saw, libuuid was configured out of e2fsprogs, but a package was declared to contain it - the package was empty and therefore never created, causing a failure during the final creation of the image. In this case, a bug involving configuration wasn't visible until the very last step of the build.
I believe the first point has already been fixed, we see a build error at do_unpack when a file is unavailable. Secondly when empty packages are created we write a note, an error message is not possible as the system generates several empty packages and to "fix" all of those would a)be time consuming and b)increase complexity of requirements to create a recipe. It's possible to point out the possibility of empty packages to the user when a package is missing at rpm rootfs creation but I've not done that as it would be rpm rootfs specific and I'm not sure it helps the reporter much. Marking this bug as WONTFIX for the second issue, as already state I believe the first is already taken care of.
Verify partial fix