Bug 8612

Summary:	Add a locked sigs mode allowing locked task to rerun
Product:	[Build System, Metadata & Runtime] BitBake	Reporter:	Paul Eggleton <bluelightning>
Component:	bitbake	Assignee:	Unassigned <unassigned>
Status:	NEW ---	QA Contact:
Severity:	enhancement
Priority:	Medium	CC:	alex.kanavin, joshuagloe, kergoth, poky.bs.watcher, poky.watcher, randy.macleod, richard.purdie
Version:	1.8
Target Milestone:	6.99
Hardware:	All
OS:	Multiple
Whiteboard:
OS type for building Yocto:	---	Type of Regression:	---
Verified:		Documentation change:	Yes (doc changes required)

Description Paul Eggleton 2015-10-29 13:31:31 UTC

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.

Comment 1 Paul Eggleton 2015-10-29 13:36:34 UTC

(... without having to set a lock for all of those dependent tasks)

Comment 2 Randy MacLeod 2015-10-29 15:05:22 UTC

Richard to review but perhaps assign to another team member.

Comment 3 Randy MacLeod 2023-10-30 15:37:27 UTC

Build move to 5.0 -- ../Randy

Comment 4 Randy MacLeod 2024-04-25 01:13:53 UTC

Bulk move of 5.0 medium importance issues to 5.99.
Move to 5.1 if you want to actively work on an issue.

Comment 5 Randy MacLeod 2024-04-25 01:23:13 UTC

Move to 5.99 since no one is actively working on this issue.
Move to 5.x if you start on a task, please.

Comment 6 Richard Purdie 2026-07-16 15:27:23 UTC

This could be an option to bblock,

Instead of "lock glibc", we'd want a "lock everything that depends on glibc" option.