| Summary: | bitbake-layers layerindex-fetch -b fails | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] BitBake | Reporter: | Paul Eggleton <bluelightning> |
| Component: | bitbake | Assignee: | Mark Hatle <mark.hatle> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium+ | CC: | mark.hatle, poky.bs.watcher, poky.watcher, randy.macleod, richard.purdie |
| Version: | 3.0 | ||
| Target Milestone: | 2.8 M3 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
|
Description
Paul Eggleton
2019-07-23 03:51:32 UTC
Does this mean we're missing some kind of test? I'll investigate and see what I can come up with. I've found the cause. There is a circular dependency in the master branch of the layer index: https://layers.openembedded.org/layerindex/branch/master/layer/meta-oe/ https://layers.openembedded.org/layerindex/branch/master/layer/meta-python/ meta-pyhton requires meta-oe, meta-oe requires meta-python. This is fundamentally broken and what is triggering the problem. Obviously I can resolve this in the software and say it's met from a dependency standpoint -but- when constructing things which one comes first? Or is that simply undefined? Fix sent to bitbake-devel. We now detect and abort the dependency processing (with a warning) when we encounter circular dependencies. Hmm, yes - meta-oe should not be depending upon meta-python. I don't know how it came to be there, but I have now removed it. |