| Summary: | license.manifest does not include u-boot | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | Jonathan Liu <net147> |
| Component: | deployment | Assignee: | Mariano Lopez <mariano.lopez> |
| Status: | VERIFIED FIXED | QA Contact: | Bogdan Alexandru Voiculescu <bogdanx.a.voiculescu> |
| Severity: | major | ||
| Priority: | Medium | CC: | benjamin.esquivel, bluelightning, bogdanx.a.voiculescu, sgw |
| Version: | 1.6.2 | ||
| Target Milestone: | 2.1 M1 | ||
| Hardware: | All | ||
| OS: | arm | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
|
Description
Jonathan Liu
2014-09-29 06:27:39 UTC
Isn't this expected since u-boot isn't actually contained in the image? For Raspberry Pi SD card images, the image contains u-boot: https://github.com/djwillis/meta-raspberrypi/blob/master/classes/sdcard_image-rpi.bbclass So Beth and I have discussed bootloaders not showing up in the manifest before, but perhaps what sdcard_image-rpi.bbclass does is a "new" wrinkle (although it might be generalised to any image where a certain IMAGE_FSTYPES type might cause the final image file to contain files produced by an additional recipe - syslinux within hddimg image files springs to mind). I do agree we need to address this; but I also think it needs to be done in a way that isn't simply adding all recipes in EXTRA_IMAGEDEPENDS to the end of the manifest; there needs to be some kind of marking that indicates what has actually happened. Sent patch for review Every BSP layer has its own methods to build the bootloader or other packages that are deployed in the image. For example, rpi uses IMAGE_DEPENDS, qemux86 uses the dependencies in bootimage class, fsl uses a custom class to add u-boot. So discussing this with Paul, he recommended to check for the dependencies in rootfs and bootimage and check what packages are deployed (using SSTATE_MANIFESTS) and include those in the manifest for the image file Change to 2.0 milestone This bug has been solved with: http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=1a210e6374b2e8140373fcb715b19d1d8c6b4b3e http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=8b1e7bcef2126b0b7f8070c277d04e3b22c5b961 http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=d45e10e1cf872e86925df33731fc5b03cf97064c http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=cc0d0441094115debe823a81c7c0bca3184f0551 http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=efdab526245e512d9163758fadb971e0aee86710 http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=d95df11131b60933ce82b7ac96fd2dc2ebc5e1f6 Verified on master: Build Configuration: BB_VERSION = "1.29.0" BUILD_SYS = "x86_64-linux" NATIVELSBSTRING = "Ubuntu-14.04" TARGET_SYS = "arm-poky-linux-gnueabi" MACHINE = "raspberrypi2" DISTRO = "poky" DISTRO_VERSION = "2.0+snapshot-20160222" TUNE_FEATURES = "arm armv7ve vfp thumb neon vfpv4 callconvention-hard cortexa7" TARGET_FPU = "hard" meta meta-yocto meta-yocto-bsp = "master:36b43b233c841b3c09fc17e04686b4b758780963" meta-raspberrypi = "master:6314f668fa14473463bb777ffaf778333fea16eb" This isn't solved because the manifest files in /usr/share/common-licenses on the rootfs still don't include u-boot. (In reply to comment #9) > This isn't solved because the manifest files in /usr/share/common-licenses > on the rootfs still don't include u-boot. It was solved but is not working because of a change. You can check the new bug 10733, why is not working. |