Bug 7368 - first time of executing oe-init-build-env* shows inconsistent console output
Summary: first time of executing oe-init-build-env* shows inconsistent console output
Status: RESOLVED FIXED
Alias: None
Product: BitBake
Classification: Build System, Metadata & Runtime
Component: bitbake (show other bugs)
Version: 1.8
Hardware: x86 Multiple
: Low minor
Target Milestone: 1.8
Assignee: Benjamin Esquivel
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2015-02-25 17:28 UTC by Benjamin Esquivel
Modified: 2015-05-21 15:24 UTC (History)
3 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)

Attachments
first time executed log (1.54 KB, text/x-log)
2015-02-25 17:28 UTC, Benjamin Esquivel 		no flags Details
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 Benjamin Esquivel 2015-02-25 17:28:29 UTC 
Created attachment 2421 [details]
first time executed log

When oe-init-build-env and *-memres are executed for the first time after cloning, it shows an extra output than if executed later times. Log attached.

What drawn my attention specifically was the duplicated output of this message:

-------------
The Yocto Project has extensive documentation about OE including a reference manual
which can be found at:
    http://yoctoproject.org/documentation

For more information about OpenEmbedded see their website:
    http://www.openembedded.org/
-------------
Comment 1 Benjamin Esquivel 2015-05-21 15:24:33 UTC 
Fixed by:

http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=1d43c3c2141ed367dd01d1d9d34df0c96d4fe25b

Fix is to remove the duplicated message.