weston.ini in shipped images is incorrect

Description

Due to the way that weston-ini-conf generates the weston.ini for the target, bitbake/OpenEmbedded are unable to automatically determine that it needs to mark the resulting package as machine-specific, so does not. This results in the wrong sstate file being found to be valid and we ship an incorrect weston.ini in images.

Environment

None

Activity

Tom Rini 
November 2, 2017 at 3:06 PM

With the code changes merged in dab, this will be fixed with 4.0.3.

Fixed

Details

Assignee

Reporter

Fix versions

Labels

Contract ID

Components

Affects versions

Priority

Created October 17, 2017 at 12:25 AM
Updated February 8, 2018 at 5:36 PM
Resolved January 2, 2018 at 2:29 PM