8612 2015-10-29 13:31:31 +0000 Add a locked sigs mode allowing locked task to rerun 2026-07-16 15:27:23 +0000 1 1 7 Build System, Metadata & Runtime BitBake bitbake 1.8 All Multiple NEW Medium enhancement 6.99 1 bluelightning unassigned alex.kanavin joshuagloe kergoth poky.bs.watcher poky.watcher randy.macleod richard.purdie --- --- Yes (doc changes required) oldest_to_newest 55991 0 bluelightning 2015-10-29 13:31:31 +0000 It would be useful if we were able to allow a locked task to "freewheel" i.e. the locked task behaves as if it were unlocked, but any dependent tasks that aren't in that mode see the task as having the locked signature value. You could use this for example if you wanted to modify the kernel or glibc with "devtool modify" without having anything else rebuild in response to any of the changes. 55992 1 bluelightning 2015-10-29 13:36:34 +0000 (... without having to set a lock for all of those dependent tasks) 56011 2 randy.macleod 2015-10-29 15:05:22 +0000 Richard to review but perhaps assign to another team member. 97122 3 randy.macleod 2023-10-30 15:37:27 +0000 Build move to 5.0 -- ../Randy 98823 4 randy.macleod 2024-04-25 01:13:53 +0000 Bulk move of 5.0 medium importance issues to 5.99. Move to 5.1 if you want to actively work on an issue. 98870 5 randy.macleod 2024-04-25 01:23:13 +0000 Move to 5.99 since no one is actively working on this issue. Move to 5.x if you start on a task, please. 106197 6 richard.purdie 2026-07-16 15:27:23 +0000 This could be an option to bblock, Instead of "lock glibc", we'd want a "lock everything that depends on glibc" option.