Bug 13037

Summary:	devtool finish busybox fails
Product:	[Build System, Metadata & Runtime] OE-Core	Reporter:	chandana kalluri <ckalluri>
Component:	Scripts and Tools	Assignee:	Richard Purdie <richard.purdie>
Status:	RESOLVED NOTABUG	QA Contact:
Severity:	normal
Priority:	Undecided	CC:	alejandr, bluelightning, ross.burton
Version:	2.6
Target Milestone:	---
Hardware:	x86
OS:	Multiple
Whiteboard:
OS type for building Yocto:	---	Type of Regression:	---
Verified:		Documentation change:	No (bug/feature does not impact docs)

Description chandana kalluri 2018-11-22 03:06:20 UTC

When user runs devtool build busybox, the object files built are stored within the devtool workspace for busybox. As a result, when user runs devtool finish the following error is generated:
ERROR: Source tree is not clean:

?? .busybox_unstripped.cmd
?? .config
?? .config.old
?? .kconfig.d
?? .kernelrelease
?? applets/.applet_tables.cmd
?? applets/.applets.o.cmd
?? applets/.built-in.o.cmd
?? applets/.usage.cmd
?? applets/.usage_pod.cmd
?? applets/Kbuild
?? applets/applet_tables
?? applets/applets.o
?? applets/built-in.o
.
.
.
.
Ensure you have committed your changes or use -f/--force if you are sure there's nothing that needs to be committed

Steps to reproduce:
1. devtool modify busybox
2. devtool build busybox
3. devtool finish busybox meta

Comment 1 Paul Eggleton 2018-11-22 19:09:09 UTC

This is expected. devtool does not know whether any of these files are uncommitted changes or not, and so takes the precaution of getting you to check. As the message says, if you look at the list and are sure none of these are files you need to commit, then you can use the -f option to bypass the error.