11928 2017-08-14 14:48:09 +0000 When both cpio.gz and cpio.gz.u-boot are stated in IMAGE_FSTYPES the cpio.gz is finally deleted 2017-08-31 15:12:13 +0000 1 1 7 Build System, Metadata & Runtime OE-Core core 2.2 x86 Multiple RESOLVED FIXED Medium+ normal 2.2.2 1 michal.vokac akuster meta.mr.watcher meta.watcher tom.rini --- --- Don't know oldest_to_newest 75836 0 michal.vokac 2017-08-14 14:48:09 +0000 From my understanding of the documentation it is expected that all image types stated in the IMAGE_FSTYPES variable are produced. Lets imagine I went through these steps. 1. I set up the recipe so that tar.bz2 and cpio.gz images are generated. IMAGE_FSTYPES = "tar.bz2 cpio.gz" inherit core-image The tar is just for development debugging and the cpio.gz is packed into a FIT image that goes into production. 2. After some unspecified time a need arose to produce also the cpio.gz.u-boot image that can be loaded manually in U-Boot during development. I changed the recipe like this: IMAGE_FSTYPES = "tar.bz2 cpio.gz cpio.gz.u-boot" inherit core-image inherit image_types_uboot Now the cpio.gz is deleted and only the tar.bz2 and cpio.gz.u-boot resides in deploy dir. 75846 1 tom.rini 2017-08-14 22:00:16 +0000 This is further fallout from 46bc438374de (which is in morty) and is corrected by 0a7ce0b971a208956cb895ba5a869ec8c5d94703 from master. This change would also be applicable to pyro. The potential downside here is that there may be layers adding in custom IMAGE_CMD types that do a similar "clean" as the u-boot command was doing and would be broken by correcting the problem. 75960 2 akuster 2017-08-17 15:38:23 +0000 backported and pushed to stagging for next build. 76401 3 akuster 2017-08-31 15:12:13 +0000 in morty http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/meta/classes/image.bbclass?h=morty&id=341726ffdba0f7dfa2056b9c501e20ef600a51cb