Bug 12564 - wic create displays incorrect rootfs location
Summary: wic create displays incorrect rootfs location
Status: RESOLVED FIXED
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: Scripts and Tools (show other bugs)
Version: 2.4
Hardware: x86 Multiple
: Medium normal
Target Milestone: 4.99
Assignee: Amanda Brindle
QA Contact:
URL:
Whiteboard: backport to 2.4
Depends on:
Blocks:
 
Reported: 2018-02-21 23:05 UTC by Stephano Cetola
Modified: 2018-09-26 10:57 UTC (History)
2 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Yes (doc changes required)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Stephano Cetola 2018-02-21 23:05:26 UTC
Back in 2.3 wic create would tell you where the rootfs location was:

http://www.yoctoproject.org/docs/2.3/dev-manual/dev-manual.html#generate-an-image-using-a-provided-kickstart-file

wic create mkefidisk -e core-image-minimal
ROOTFS_DIR: /home.../core-image-minimal/1.0-r0/rootfs

As of 2.4 it outputs the tmp rootfs location instead. This was probably introduced when this feature was turned into a plugin.

http://www.yoctoproject.org/docs/2.4/dev-manual/dev-manual.html#generate-an-image-using-a-provided-kickstart-file

wic create mkefidisk -e core-image-minimal
ROOTFS_DIR: /home/scottrif/poky/build/tmp.wic.r4hkds0b/rootfs_copy

See plugins/imager/direct.py: print_info()
Comment 1 Scott Rifenbark 2018-03-30 18:07:22 UTC
Here is what I have in the docs... Needs updating once we have a resolution.

https://www.yoctoproject.org/docs/2.5/dev-manual/dev-manual.html#generate-an-image-using-a-provided-kickstart-file

Scott
Comment 2 Ross Burton 2018-09-26 10:57:19 UTC
Merged in oe-core a4941af2d3624aecc5dcd7ff54b7ea8c9e9dee8b.