Bug 12807 - devtool: ERROR: Source tree is not clean
Summary: devtool: ERROR: Source tree is not clean
Status: ACCEPTED
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: devtools / tool chain (show other bugs)
Version: 2.5.1
Hardware: x86 Multiple
: Medium normal
Target Milestone: 5.99
Assignee: Unassigned
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2018-06-21 14:46 UTC by Robert Berger
Modified: 2025-02-14 16:48 UTC (History)
3 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Don't know

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Robert Berger 2018-06-21 14:46:37 UTC 
+ devtool finish nettoe layers/meta-nettoe/
NOTE: Starting bitbake server...
ERROR: Source tree is not clean:

 M INSTALL
 M Makefile.in
 M aclocal.m4
 M build-aux/config.guess
 M build-aux/config.sub
 M build-aux/depcomp
 M build-aux/install-sh
 M build-aux/missing
 M configure
 M desktop/Makefile.in
 M docs/Makefile.in
 M src/Makefile.in
 M test/Makefile.in
?? autom4te.cache/
?? build-aux/compile
?? build-aux/test-driver
?? config.h.in~

Ensure you have committed your changes or use -f/--force if you are sure there's nothing that needs to be committed

-----------

I just built some autotooled code and there are generated files. Is there any other way except for finish -f?

This is a new feature in 2.5+
Comment 1 Paul Eggleton 2018-08-06 14:42:38 UTC 
The issue is devtool does not know how to determine whether or not these files need to be committed (presumably there is no .gitignore in this case), and it's leaving it up to you to figure that out - since it's possible you missed committing some important changes that would otherwise "disappear" at the end of the devtool finish operation. 

Do you have a suggestion on how this could be handled better? I'm not sure I can see a way other than for the code to start making guesses that could turn out to be wrong.
Comment 2 Paul Eggleton 2018-08-23 03:53:08 UTC 
Setting NEEDINFO - Robert can you reply to the above? Thanks.
Comment 3 Robert Berger 2018-09-03 19:00:01 UTC 
I'm fine with this new feature. It would be good to document the new behaviour somewhere, since this happens since Sumo.
Comment 4 Stephen K Jolley 2018-09-07 16:12:24 UTC 
It appears that Robert has answered your question.  If you need more information please place this back into NEEDINFO.
Comment 5 Paul Eggleton 2019-06-20 10:26:57 UTC 
So, we did note this change in the migration guide, however it's true that we do not explicitly note this behaviour in the documentation that covers devtool finish. I will work with Scott to rectify this.
Comment 6 Randy MacLeod 2023-10-30 15:37:30 UTC 
Build move to 5.0 -- ../Randy
Comment 7 Randy MacLeod 2024-04-25 01:13:55 UTC 
Bulk move of 5.0 medium importance issues to 5.99.
Move to 5.1 if you want to actively work on an issue.
Comment 8 Randy MacLeod 2024-04-25 01:23:13 UTC 
Move to 5.99 since no one is actively working on this issue.
Move to 5.x if you start on a task, please.
Comment 9 Randy MacLeod 2025-02-14 16:46:30 UTC 
bulk change to add Saul's non-WR address.
Comment 10 Randy MacLeod 2025-02-14 16:48:14 UTC 
Bulk change: Remove Saul's old WR address.