6139 2014-04-09 09:53:31 +0000 Mismatching layer version error message isn't clear 2015-02-24 12:01:42 +0000 1 1 7 Build System, Metadata & Runtime OE-Core core 1.6 All Multiple RESOLVED FIXED Medium normal 1.8 M3 1 yi.zhao bluelightning alexandru.c.georgescu bluelightning jessica.zhang ke.zou meta.mr.watcher meta.watcher --- --- No (bug/feature does not impact docs) oldest_to_newest 42439 0 yi.zhao 2014-04-09 09:53:31 +0000 Git rev: master/3e528d3e4bc542ca2f654c54363c56af0fb9f61b Steps: 1. Set an invalid value for DISTRO in local.conf. e.g. DISTRO ?= "foo" 2. Run bitbake core-image-minimal I got the following errors: ########################## ERROR: OE-core's config sanity checker detected a potential misconfiguration. Either fix the cause of this error or at your own risk disable the checker (see sanity.conf). Following is the list of potential problems / advisories: Your version of bblayers.conf has the wrong LCONF_VERSION (has 6, expecting 5). Please compare the your file against bblayers.conf.sample and merge any changes before continuing. "meld conf/bblayers.conf /buildarea3/yzhao1/poky-build/meta*/conf/bblayers.conf.sample" is a good way to visualise the changes. DISTRO 'foo' not found. Please set a valid DISTRO in your local.conf ERROR: Execution of event handler 'check_sanity_eventhandler' failed ERROR: Command execution failed: Exited with 1 ############################ I didn't change the bblayers.conf or LCONF_VERSION. But the message showed there is a wrong LCONF_VERSION. Looks this message is redundant. 42440 1 bluelightning 2014-04-09 10:45:49 +0000 I wouldn't describe it as redundant, just very annoying - this situation comes about because poky's LAYER_CONF_VERSION is out-of-step with OE-Core, and it's set in poky.conf so changing DISTRO means the value changes and then no longer matches the LCONF_VERSION in your bblayers.conf. This is a long-standing problem, and I think we've reached the point where we really need to do something about it (for 1.7). 46988 2 ross.burton 2014-11-13 17:16:53 +0000 As Paul seems to have an idea about how to deal with this, assigning to him. 48390 3 bluelightning 2015-01-29 14:08:36 +0000 I've sent out an RFC patch to the bitbake and OE-Core lists: http://lists.openembedded.org/pipermail/bitbake-devel/2015-January/005370.html 48391 4 bluelightning 2015-01-29 14:08:58 +0000 Argh, wrong bug - ignore the previous message 48576 5 bluelightning 2015-02-05 12:07:09 +0000 OK, I've just sent a couple of patches for this - one to the openembedded-core mailing list and one to the poky list (since both sides need fixing). 49002 6 bluelightning 2015-02-24 12:01:42 +0000 Fixes merged to master (fixes were required on both the OE-Core and Poky side): http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=1bb00223844bfabe1f6d75c8179d4cbbd4fb5466 http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=19e06e6584ab2aa31709bcf8fe7b566cafd297e7