Bug 5751 - Hob is not starting anymore when a new layer is added without adding it's master layer
Summary: Hob is not starting anymore when a new layer is added without adding it's mas...
Status: RESOLVED DUPLICATE of bug 5700
Alias: None
Product: Hob
Classification: Build System, Metadata & Runtime
Component: hob (show other bugs)
Version: 1.6
Hardware: x86 Multiple
: Medium normal
Target Milestone: 1.1.2
Assignee: Irina Patru
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2014-01-22 11:20 UTC by Lucian Musat
Modified: 2014-02-12 10:03 UTC (History)
6 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Lucian Musat 2014-01-22 11:20:47 UTC
Hi,

When directly adding meta-emenlow layer without adding meta-intel layer in Hob and saving the configuration, this action causes Hob to throw an error and be unable to start again without manually editing the bblayers.conf file.

Steps to reproduce:

1. Add new meta-emenlow layer and click ok. An error is displayed.
2. Choose the now available "emenlow" from machine list and wait to finnish parsing recipes.
3. Close Hob and try to start it again.

Expected result:
4. Hob starts and eventually displays an error about the layer misconfiguration

Actual result:
4. Hob fails to start with error:

ParseError: ParseError at /home/lucian/work/poky/meta-intel/meta-emenlow/conf/machine/emenlow.conf:15: Could not include required file conf/machine/include/meta-intel-emgd.inc

ERROR: Unable to parse conf/bitbake.conf: ParseError at /home/lucian/work/poky/meta-intel/meta-emenlow/conf/machine/emenlow.conf:15: Could not include required file conf/machine/include/meta-intel-emgd.inc
Comment 1 Belen Barros Pena 2014-01-22 13:39:08 UTC
This might be related to bug 5700
Comment 2 Cristiana Voicu 2014-01-22 14:42:42 UTC
I will assign this to Irina, since this might be related to bug 5700.
Comment 3 Irina Patru 2014-02-12 10:03:20 UTC
Duplicate (5700)

*** This bug has been marked as a duplicate of bug 5700 ***