In the past meta-arm-bsp depended on meta-linux-mainline, but in master this dependency was removed. However, the layer index still lists meta-linux-mainline as a dependency.
Alexandre Belloni also mentioned that meta-rust index data isn't up to date either. I can open a new bug if needed.
We use the layer index at Wind River and it's workingn well. Konrad, Robert, can whowever did that work on the WR clone, fix the problems here? I think it's an important tool that should always provide accurate data.
The layerindex does not remove dependencies automatically. Either the dependency is manually removed using the admin interface or the layer parsed with "fullreload" which deletes all the dependencies before parsing.
Ideally the layer index or the update script should point out the problem and a person should fix the problem.
Bulk move of 64 bugs to 4.3 M3 after a quick review. If a bug is actually fixed, please add a commit link and resolve it. -- Randy for YP bug team.
Moved to M4.
Bulk move to 5.0 M1. -- Randy
One annoying behavior related to this is that dependent layers are not checked out at the same branch as the layer being updated bug #15236. The LayerItem is being queried, but it is not clear if the _branch_ of that layer is being checked out in a deterministic way (or just the state it was last in during an update.py run?) Another aspect is that the conf/layer.conf is parsed when a layer is first added but for updates it requires a human admin to review the logs: https://layers.openembedded.org/layerindex/updates/ and then manually update the dependencies in any LayerBranch objects that have grown stale.
Bulk move of 52 5.0-M1 bugs to M2.
We should not only be respecting LAYERDEPENDS during an update (a layer dependency may have been dropped or added), but we also have issues with parsing dynamic-layers when a class is inherited there that is defined in the dynamic-layer. In this case, we probably also want to dynamically add LAYERRECOMMENDS (a LayerDependency with "required" set to false in the layerindex admin UI) which should be parseable from BBFILES_DYNAMIC? Perhaps a separate UI indication of dynamic layers would be useful too, but that is a different effort.
Bulk move of bugs from 5.0-M3 to 5.99. The bugs in this list are all unassigned and are ones that I consider to be nice to do some time but not essential track from milestone to milestone in 5.0 or 5.1. We agreed on this bug handling approach in the YP bug review on Feb 22, 2024. If you disagree, please move back to a 5.[012...]-M* milestone.
Still valid. Moving to 6.99.