Bug 8659

Summary: Loading the openembedded-core toasterconf.json file shows 2 openembedded-core layers
Product: [Build System, Metadata & Runtime] Toaster Reporter: Belen Barros Pena <belen.barros.pena>
Component: toasterAssignee: Michael Wood <michael.g.wood>
Status: RESOLVED NOTABUG QA Contact: Mihail Stanciu <stanciux.mihail>
Severity: normal    
Priority: Undecided CC: belen.barros.pena, jessica.zhang, stanciux.mihail
Version: 2.0   
Target Milestone: 2.1   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: Yes (doc changes required)
Attachments:
Description Flags
two openembedded-core layers none

Description Belen Barros Pena 2015-11-06 11:52:26 UTC
Created attachment 2840 [details]
two openembedded-core layers

If you use the toasterconf.json file in meta/conf/ instead of the one in meta-yocto/conf, the compatible layers table shows 2 openembedded-core layers.

To reproduce:

1. Edit the bitbake/bin/toaster script to set TOASTER_CONF to meta/conf/toasterconf.json 

2. Start a clean Toaster instance (without an existing database)

3. Create a project

4. Go to the compatible layers page

5. Search for openembedded-core

You get 2 entries (see attached screenshot). The one added to the project configuration has no recipe and machine information in the layer details page. The one not added to the project configuration has recipe and machine information.
Comment 1 Michael Wood 2015-11-09 13:46:30 UTC
Are you using poky and and 'upstream' at the same time? The supported configurations are

openembedded-core toasterconf.json with bitbake

meta-yocto toasterconf.json with poky
Comment 2 Belen Barros Pena 2015-11-09 15:41:22 UTC
(In reply to comment #1)
> Are you using poky and and 'upstream' at the same time? The supported
> configurations are
> 
> openembedded-core toasterconf.json with bitbake
> 
> meta-yocto toasterconf.json with poky

mmm, I see: I am using a poky clone using meta/conf/toasterconf.json as my configuration file. It was not clear to me that combination was not supported. Although I think that's probably ok, this is not written anywhere. We should make sure this is documented in the Toaster manual (I've changed the documentation flag). 

The other thing we should do is making sure we cannot reproduce the issue in the "openembedded-core toasterconf.json with bitbake" configuration. If someone can provide a list of steps to set that up, I'll be happy to give it a try.
Comment 3 Belen Barros Pena 2015-11-11 16:24:58 UTC
The configuration this issue refers to is not supported