Bug 12879 - Drop DEPLOY_DIR_IMAGE from SSTATE_DUPWHITELIST
Summary: Drop DEPLOY_DIR_IMAGE from SSTATE_DUPWHITELIST
Status: RESOLVED FIXED
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: core (show other bugs)
Version: 2.2
Hardware: x86 Multiple
: Undecided normal
Target Milestone: ---
Assignee: Ross Burton
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2018-08-10 08:53 UTC by Richard Purdie
Modified: 2018-08-14 10:44 UTC (History)
2 users (show)

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

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 2018-08-10 08:53:09 UTC 
Having DEPLOY_DIR_IMAGE in SSTATE_DUPWHITELIST means file overwriting can be masked out a hidden, confusing users as illustrated on IRC recently. There are only a few cases we have file overwriting in the deploy images directory left in OE-Core with the default settings, we should remove them.

In particular there are multilib conflicts between:

{lib64-,}systemd-boot:do_deploy
{lib64-,}grub-efi:do_deploy
{lib64-,}ovmf:do_deploy

and if these are fixed we should be able to remove this safely for OE-Core.