Bug 15581

Summary: dm-verity-image-initramfs rebuilds unconditionally
Product: [Build System, Metadata & Runtime] Other YP Layers Reporter: Woodrow Douglass <wdouglass>
Component: meta-securityAssignee: Scott Murray <scott.murray>
Status: NEW --- QA Contact:
Severity: normal    
Priority: Medium CC: ccasciato, randy.macleod, rybczynska
Version: 4.3   
Target Milestone: 6.1   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: No (bug/feature does not impact docs)

Description Woodrow Douglass 2024-08-22 18:53:23 UTC 
I'm reporting this against 4.3, because that's what i'm running, but it's still true as of the tip of the master branch of the meta-security repository. When dm-verity-image-initramfs is enabled, it is unconditionally rebuilt, due to the
```
do_image[nostamp] = "1"
```
at line 34 of the .bb file. I am building an image that gets embedded inside another image  (using bitbake multiconfig) and the internal image rebuilding causes my build to be much longer. Shouldn't the dependency function (the anonymous python function above the "nostamp" line) cause the .env file to get regenerated when needed, making the "nostamp" flag redundant? i'm building with `unset do_image[nostamp]` in a .bbappend and it seems to do what i expect -- is this a dangerous thing to do?

Thank you for your maintenance of this meta layer, and for considering my questions! If this is not a bug, please excuse my filing it inappropriately!
Comment 1 Randy MacLeod 2025-11-06 15:37:38 UTC 
This may be "normal behaviour" but can it be removed?
Comment 2 Randy MacLeod 2026-06-04 15:09:02 UTC 
Scott, Is this in your plan ? 
If not, unassign.