12922 2018-09-13 02:19:38 +0000 Remove layerbranch automatically when conf/layer.conf is gone ? 2026-02-17 19:05:57 +0000 1 1 6 Yocto Project Subprojects Layer Index Layer Index unspecified x86 Multiple NEW Medium enhancement 6.99 1 liezhi.yang unassigned bluelightning brian.avery randy.macleod tim.orling william.lyu apoorvsangal --- --- Don't know oldest_to_newest 81540 0 liezhi.yang 2018-09-13 02:19:38 +0000 Can we make update.py remove layerbranch automatically when conf/layer.conf is gone ? It would make the workflow simple, otherwise, the layer owner has to notify layerindex administer to remove it manually. Maybe we ca add a conf like: AUTO_REMOVE_LAYERBRANCH = True/False 96656 1 tim.orling 2023-10-07 17:31:32 +0000 Related to this, we need an ability to turn off updates for a LayerBranch. Currently we can only turn off ALL updates for a Layer or a Branch. Heavy hammers. 96658 2 tim.orling 2023-10-07 17:43:05 +0000 UI for LayerBranch is in https://bugzilla.yoctoproject.org/show_bug.cgi?id=8008 96669 3 randy.macleod 2023-10-10 18:43:01 +0000 Set target to 5.99. It was set to 0.0 from 4.99 when last changed. 98136 4 tim.orling 2024-02-06 02:34:21 +0000 What do we really mean by "remove the layer"? We now have at least two contexts, more likely three, for this: (1) LayerItem is marked as "No Update" so no branch will ever be attempted to be updated ever again (2) LayerBranch is marked as False for "Enable Updates", so this particular branch will never be attempted to be updated (3) The layer is no longer displayed For 3 we really do not have a way to implement that. We can DELETE the LayerItem or the LayerBranch objects. More likely there are cases where we want a layer to still be displayed for older stable branches, but no longer be displayed for "master" branch. Currently we can only create a LayerNote if the "master" branch still exists. We probably want to be able to create a LayerBranchNote which has LayerBranch specific information (such as "This layer is no longer being updated"). We might also want a "simple" 'do not display this layer anymore' setting for "master" for the layers that are ONLY applicable to prior releases. If we DELETE the "master" LayerBranch for a layer, it will simply be created again as long as the LayerItem exists and a "master" branch exists on the git repository. Once we implement enforced LAYERSERIES_COMPAT for layers, we will absolutely need to indicate when a layer is not compatible with e.g. scarthgap/nanbield, but is marked as compatible with mickledore. Layers have a lag in updates (and some only support the LTS releases, even on "master" such as meta-agl*) 104335 5 tim.orling 2026-02-17 19:05:57 +0000 Still valid.