14846 2022-06-23 05:28:48 +0000 Add possibility of dumping depsig.* from sstate-cache 2026-08-20 15:06:47 +0000 1 1 7 Build System, Metadata & Runtime OE-Core Scripts and Tools unspecified x86 Multiple NEW Low enhancement Future 1 jacob.kroon jacob.kroon randy.macleod ross.burton --- --- Don't know oldest_to_newest 93569 0 jacob.kroon 2022-06-23 05:28:48 +0000 I usually do incremental builds from a wiped tmp/ and sstate cache, after having first updated the Yocto meta layers. In order to identify why certain recipes rebuilds it would help if I could compare old and new depsig.* files. The new depsig.* will be generated by the rebuild itself, but there is no way to extract the old depsig.* from sstate-cache. Would it be possible to add a utility that does this ? 93577 1 randy.macleod 2022-06-23 14:40:08 +0000 Hi Jacob, We don't think that many people have this requirement. Please either send a patch or specify why others should be interested as well as exactly want needs to be done. Thanks! 93599 2 jacob.kroon 2022-06-26 19:38:18 +0000 (In reply to comment #1) > Hi Jacob, > > We don't think that many people have this requirement. > Who are "we" ? > Please either send a patch or specify why others should be interested as > well as exactly want needs to be done. > I tried to explain the reason in the bug description. Which part of it do "you" think is unclear ? I am building with TMPDIR on a tmpfs, so it gets wiped everytime I reboot. Hence the need to extract "current" depsig.* files, in order to compare what changed. 93602 3 randy.macleod 2022-06-27 23:14:10 +0000 Hi Jacob, I should have explained in my comment but the 'we' in that context refers to the people who attend the weekly Yocto bug triage (mentioned here: https://www.yoctoproject.org/public-virtual-meetings/ ). There can be quite a few issues to look at each week so I can be quite rushed when replying. I'll try to remember to add a signature such as '-- YP bug review team', so that people know who 'we' are. You are welcome to join this meeting. I don't recall the conversation now but I suspect that Richard Purdie and Joshua Watt talked about it and I typed. I see that you also brought the topic up here: https://lists.openembedded.org/g/openembedded-architecture/topic/90726763#1532 so for now, I'm not sure what to suggest. Having this enhancement open will mean that the issue gets reviewed at every 2 years if no one picks up the issue because we look at all issues that are >= 2 years old on this list: https://wiki.yoctoproject.org/wiki/Bug_Triage#Future_.26_4.99_Milestones in each meeting. I know that isn't helpful to you right now but without more participants sending patches, the project members are doing all they can to keep recipes current and to fix critical issues. 93604 4 jacob.kroon 2022-06-29 07:12:18 +0000 Ok, thank you for clarifying. If Richard and Joshua agree it is low priority then fine, I'll see if I can get it implemented.