Bug 9806 - sstate doesn't detect when the recipe filename changes
Summary: sstate doesn't detect when the recipe filename changes
Status: RESOLVED FIXED
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: core (show other bugs)
Version: 2.2
Hardware: x86 Multiple
: Medium+ normal
Target Milestone: 2.2 M2
Assignee: Ed Bartosh
QA Contact: Francisco Pedraza
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2016-06-21 13:42 UTC by Joshua Lock
Modified: 2016-07-29 15:59 UTC (History)
4 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)

Attachments
fix (439 bytes, text/plain)
2016-07-07 12:59 UTC, Ed Bartosh 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Joshua Lock 2016-06-21 13:42:19 UTC 
The e2fsprogs recipe was erroneously updated with an extra . in the filename (e2fsprogs_1.4.3..bb) resulting in the PV including a . "1.43.".

When the recipe was updated to fix the extra . the sstate code didn't detect that the recipe had been renamed and the PV changed.

The problem is that the PV is determined from the filename but at no time is the determined PV stored and thus it's not included in the checksum. As the summed variables hadn't changed in the fixed recipe the previous sstate object, with an incorrect PV, was reused.
Comment 1 Ed Bartosh 2016-07-07 12:59:55 UTC 
Created attachment 3274 [details]
fix

Joshua, can you check if this fix solves the issue?
Comment 2 Ed Bartosh 2016-07-11 09:55:29 UTC 
The fix has been sent for review: http://lists.openembedded.org/pipermail/openembedded-core/2016-July/123708.html
Comment 3 Ross Burton 2016-07-20 13:44:44 UTC 
Fixed in oe-core 918646ca803d56004fb0ab7c21e86cc9cb14513d.