Comment 4 for bug 1010642

It appears that for development image installs a lot more packages than the nano images and one of them being the lttng-tools as well and it confirms that it is the culprit package which induces the vmlinuz in it.

With the LB_APT_RECOMMENDS="true" lttng-tools package installation includes linux-image as part of the recommended package and hence the developer image seems to include the vmlinuz in it.

The fix for this problem is to set the LB_APT_RECOMMENDS="false" when building the developer images which will make sure that the recommended packages that includes linux-image will not get included in the images being built.
I built a test developer image successfully with LB_APT_RECOMMENDS="false" and the l-m-c was successful to write the image on the SD successfully.

The inclusion of the vmliuz into the developer image seems to exists probably since the earliest of the precise developer images, because when I checked the http://snapshots.linaro.org/precise/images/developer/70/linaro-precise-developer-20120417-70.build-log.txt ( which appears to be the oldest of the images) it seemed to contain reference to the linux-image.

I wonder if there is any testing being done on these hwpacks by LAVA. If there is not much tests on this then we should plan to include the tests on the developer images as well.