Bug 10278 - Switching PREFERRED_PROVIDER_virtual/kernel leads to errors
Summary: Switching PREFERRED_PROVIDER_virtual/kernel leads to errors
Status: RESOLVED FIXED
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: core (show other bugs)
Version: 2.2
Hardware: All Multiple
: Medium+ normal
Target Milestone: 2.2 M4
Assignee: Saul Wold
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2016-09-14 21:17 UTC by Paul Eggleton
Modified: 2016-09-28 18:22 UTC (History)
3 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 Paul Eggleton 2016-09-14 21:17:49 UTC 
I changed PREFERRED_PROVIDER_virtual/kernel from linux-yocto to linux-yocto-rt and received the following errors:

------------------ snip ------------------
ERROR: linux-yocto-rt-4.8-rc5+gitAUTOINC+25fb74eaae_9e7ee5155e-r0 do_package_write_rpm: The recipe linux-yocto-rt is trying to install files into a shared area when those files a
lready exist. Those files and their manifest location are:
   /media/large/tmp/deploy/rpm/qemux86_64/kernel-module-ppp-synctty-4.8+rc5+git0+25fb74eaae_9e7ee5155e-r0.qemux86_64.rpm
 Matched in b'manifest-qemux86_64-linux-yocto.package_write_rpm'
 /media/large/tmp/deploy/rpm/qemux86_64/kernel-module-nf-conntrack-sip-4.8+rc5+git0+25fb74eaae_9e7ee5155e-r0.qemux86_64.rpm
 Matched in b'manifest-qemux86_64-linux-yocto.package_write_rpm'
 /media/large/tmp/deploy/rpm/qemux86_64/kernel-module-rfcomm-4.8+rc5+git0+25fb74eaae_9e7ee5155e-r0.qemux86_64.rpm
 Matched in b'manifest-qemux86_64-linux-yocto.package_write_rpm'
...
------------------ snip ------------------

It seems to me that we ought to be able to handle switching to a different kernel in the same sysroot without error, particularly as we now disallow multiple recipes providing the same target building when PREFERRED_PROVIDER is being used. We should have enough information to handle this, we just need to set up the mechanism.
Comment 1 Saul Wold 2016-09-26 22:28:29 UTC 
Patch submitted