Bug 3336

Summary: INCOMPATIBLE_LICENSE = "GPLv3" makes do_rootfs from core-image-basic fail
Product: [Build System, Metadata & Runtime] OE-Core Reporter: Stoicescu Cornel <corneliux.stoicescu>
Component: coreAssignee: Saul Wold <sgw>
Status: VERIFIED INVALID QA Contact:
Severity: normal    
Priority: Medium CC: meta.mr.watcher, meta.watcher
Version: 1.2.1   
Target Milestone: 1.2.2   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: ---

Description Stoicescu Cornel 2012-10-25 15:26:51 UTC 
Steps to reproduce:
1) insert INCOMPATIBLE_LICENSE = "GPLv3" in local.conf
2) build core-image-basic

Result: Notice build process fails: " ERROR: Function failed: do_rootfs  "

NOTE: log.do_rootfs contains: 
"
Processing locale-base-en-us...
Processing locale-base-en-gb...
Processing task-core-boot...
Processing task-core-apps-console...
Processing task-core-ssh-openssh...
Processing task-core-basic...
error: Failed dependencies:
<------>libreadline.so.6 is needed by python-readline-2.7.2-r2.17.i586
"

NOTE: Build succedes without the modifications to local.conf

Branch: Denzil 1.2.1
commit 846b7c388738f382e83576e77b705aa547c1dd9b
Date:   Thu Oct 11 11:43:52 2012 -0700
Comment 1 Saul Wold 2012-10-25 21:35:38 UTC 
This build Green on the AB, do you build this differently than the AB?  At first guess, it looks like you might have built it with ipk instead of RPM, which then begs the question of why is it different.

Can you please confirm your configuration.
Comment 2 Saul Wold 2012-10-25 22:48:19 UTC 
I just built both RPM and IPK based non-gplv3 with no issues.  Please confirm your build env. 

Is it possible that you built the non-gplv3 in a tmp dir that you already had a build? If that's the case then you might encounter this error as the python was with with the newer readline. Otherwise we might have some host contamination issue going on.
Comment 3 Stoicescu Cornel 2012-10-26 09:22:48 UTC 
(In reply to comment #2)
> I just built both RPM and IPK based non-gplv3 with no issues.  Please
> confirm your build env. 
> 
> Is it possible that you built the non-gplv3 in a tmp dir that you already
> had a build? If that's the case then you might encounter this error as the
> python was with with the newer readline. Otherwise we might have some host
> contamination issue going on.

Indeed the build was done with a tmp dir in place that contained 2 or 3 non-gplv3 builds. 

I did a fresh build directory and the build was successful. Should I investigate this further?
Comment 4 Saul Wold 2012-10-26 17:49:19 UTC 
This bug is being closed because building non-gplv3 in build area with a prior build.
Comment 5 Stoicescu Cornel 2012-10-31 13:29:34 UTC 
Tested this, as initial steps describe, with a clean build directory and populated sstate and downloads directory. Issue occurs as described. 

Branch: Denzil 1.2.1
commit 846b7c388738f382e83576e77b705aa547c1dd9b
Date:   Thu Oct 11 11:43:52 2012 -0700

Please note that core-image-minimal works.
Comment 6 Stoicescu Cornel 2012-11-06 10:35:33 UTC 
Tested with clean build directory, clean downloads and sstate directories, the build was successful. It seems this was a sstate contamination issue.