Bug 1938 - Detect Host system changes when using sstate
Summary: Detect Host system changes when using sstate
Status: VERIFIED FIXED
Alias: None
Product: Meta-yocto
Classification: Build System, Metadata & Runtime
Component: meta-yocto (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Medium enhancement
Target Milestone: 1.3 M3
Assignee: Richard Purdie
QA Contact:
URL:
Whiteboard: (P1)(Scheduled) Patches out for review
Depends on:
Blocks:
 
Reported: 2012-01-27 02:25 UTC by Richard Purdie
Modified: 2012-10-05 11:04 UTC (History)
4 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: ---

Attachments
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 Richard Purdie 2012-01-27 02:25:59 UTC 
If sstate packages are build on a system with a specific glibc version, there should be some way to detect when they're installed on an older system and at least flag the packages as invalid.

Running against newer glibc shouldn't be an issues, its just a question on detecting and invalidating running on older glibc than the package was built for.
Comment 1 Richard Purdie 2012-07-26 13:20:56 UTC 
For now, the best approach is going to be to mark sstate packages as being built against a given lsb_release name/version.

There are patches our for review which do this.
Comment 3 Stoicescu Cornel 2012-10-05 11:04:23 UTC 
Verified in master, commit: ef5dcad3e3e3c004112cfc00843727a7fda75cd2

Changing distros will cause bitbake to make a new directory in sstate-chache with distro name and version in which to store its native and cross packages.

Example: 
/build/sstate-cache/Ubuntu-12.04/*/sstate-*-native-*.tgz
/build/sstate-cache/Ubuntu-12.04/*/sstate-*-cross-*.tgz