<div dir="ltr"><div class="gmail_default" style="font-size:large">Hi all,</div><div class="gmail_default" style="font-size:large"><br></div><div class="gmail_default" style="font-size:large">I am in the process of adding swupdate to my Ampere openbmc build. </div><div class="gmail_default" style="font-size:large"><br></div><div class="gmail_default" style="font-size:large"><div class="gmail-ptW7te" role="region" aria-labelledby="c620" style="margin:12px 0px;overflow:auto;padding-right:20px;color:rgba(0,0,0,0.87);font-family:Roboto,RobotoDraft,Helvetica,Arial,sans-serif;font-size:14px">I have cloned openbmc:<br><ul><li>git clone <a href="https://github.com/openbmc/openbmc.git" target="_blank" rel="nofollow" style="text-decoration-line:none;color:rgb(26,115,232)">https://github.com/openbmc/openbmc.git</a><br></li></ul>configured yocto:<br><ul><li>. setup mtjade</li></ul>and compiled with no problem.<div><ul><li> bitbake obmc-phosphor-image<br></li></ul>I added libubootenv to the image, in local.conf:</div><div><ul><li>IMAGE_INSTALL:append = "libubootenv"<br></li></ul>However when I build I get the following error:<br><br></div><div><div style="color:rgb(204,204,204);background-color:rgb(31,31,31);font-family:Menlo,Monaco,"Courier New",monospace;font-size:12px;line-height:18px;white-space:pre"><div style="line-height:18px"><div>ERROR: Multiple .bb files are due to be built which each provide u-boot-fw-utils:#####                                                                                <span style="color:rgb(212,212,212)">|</span> ETA:  0:00:01</div><div>  openbmc/meta/recipes-bsp/u-boot/<a href="http://libubootenv_0.3.5.bb">libubootenv_0.3.5.bb</a></div><div>  openbmc/meta-aspeed/recipes-bsp/u-boot/<a href="http://u-boot-fw-utils-aspeed-sdk_2019.04.bb">u-boot-fw-utils-aspeed-sdk_2019.04.bb</a></div><div>A list of tasks depending on these providers is shown and may help explain <span style="color:rgb(86,156,214)">where</span> the dependency comes from.</div><div>openbmc/meta/recipes-bsp/u-boot/<a href="http://libubootenv_0.3.5.bb">libubootenv_0.3.5.bb</a> has unique dependees:</div><div>  openbmc/meta-phosphor/recipes-phosphor/images/obmc-phosphor-image.bb:do_populate_lic_deploy</div><div>  openbmc/meta-phosphor/recipes-phosphor/images/obmc-phosphor-image.bb:do_build</div><div>  openbmc/meta-phosphor/recipes-phosphor/images/obmc-phosphor-image.bb:do_create_runtime_spdx</div><div>openbmc/meta-aspeed/recipes-bsp/u-boot/<a href="http://u-boot-fw-utils-aspeed-sdk_2019.04.bb">u-boot-fw-utils-aspeed-sdk_2019.04.bb</a> has unique dependees:</div><div>  openbmc/meta-phosphor/recipes-phosphor/network/phosphor-network_git.bb:do_create_runtime_spdx</div><div>  openbmc/meta-phosphor/recipes-phosphor/trace-enable/trace-enable.bb:do_create_runtime_spdx</div><div>  openbmc/meta-phosphor/recipes-phosphor/network/phosphor-network_git.bb:do_package_qa</div><div>  openbmc/meta-phosphor/recipes-phosphor/trace-enable/trace-enable.bb:do_package_write_ipk</div><div>  openbmc/meta-phosphor/recipes-phosphor/clear-once/clear-once.bb:do_create_runtime_spdx</div><div>  openbmc/meta-phosphor/recipes-phosphor/network/phosphor-network_git.bb:do_package_write_ipk</div><div>  openbmc/meta-phosphor/recipes-phosphor/clear-once/clear-once.bb:do_package_qa</div><div>  openbmc/meta-phosphor/recipes-phosphor/clear-once/clear-once.bb:do_package_write_ipk</div><div>  openbmc/meta-phosphor/recipes-phosphor/trace-enable/trace-enable.bb:do_package_qa</div><div>It could be that one recipe provides something the other doesn't and should. The following provider and runtime provider differences may be helpful.</div><div>openbmc/meta/recipes-bsp/u-boot/<a href="http://libubootenv_0.3.5.bb">libubootenv_0.3.5.bb</a> has unique provides:</div><div>  libubootenv</div><div>openbmc/meta/recipes-bsp/u-boot/<a href="http://libubootenv_0.3.5.bb">libubootenv_0.3.5.bb</a> has unique rprovides:</div><div>  libubootenv-dev</div><div>  libubootenv-bin</div><div>  libubootenv-doc</div><div>  libubootenv-dbg</div><div>  libubootenv</div><div>  libubootenv-staticdev</div><div>  <span style="color:rgb(215,186,125)">^</span>libubootenv-locale-.*</div><div>  libubootenv-locale</div><div>  libubootenv-src</div><div>openbmc/meta-aspeed/recipes-bsp/u-boot/<a href="http://u-boot-fw-utils-aspeed-sdk_2019.04.bb">u-boot-fw-utils-aspeed-sdk_2019.04.bb</a> has unique provides:</div><div>  u-boot-fw-utils-aspeed-sdk</div><div>openbmc/meta-aspeed/recipes-bsp/u-boot/<a href="http://u-boot-fw-utils-aspeed-sdk_2019.04.bb">u-boot-fw-utils-aspeed-sdk_2019.04.bb</a> has unique rprovides:</div><div>  <span style="color:rgb(215,186,125)">^</span>u-boot-fw-utils-aspeed-sdk-locale-.*</div><div>  u-boot-fw-utils-aspeed-sdk-src</div><div>  u-boot-fw-utils-aspeed-sdk</div><div>  u-boot-fw-utils-aspeed-sdk-doc</div><div>  u-boot-fw-utils-aspeed-sdk-locale</div><div>  u-boot-fw-utils-aspeed-sdk-dbg</div><div>  u-boot-fw-utils-aspeed-sdk-staticdev</div><div>  u-boot-fw-utils-aspeed-sdk-dev</div><br></div></div></div><div><br>I have asked over on the swupdate reflector and Stefano suggested it was an conflict resulting from a change back in Dunfell? </div><div><br></div><div>Any suggestions on how to resolve this error would be appreciated!</div><div><br></div><div>Chuck</div><div> </div></div></div></div>

<br>
<div><span style="color:rgb(34,34,34);font-family:sans-serif;font-size:12.8px;background-color:rgb(255,255,255)"><br></span></div><b style="color:rgb(34,34,34);background-color:rgb(255,255,255);font-family:Calibri,sans-serif;font-size:14.6667px"><span style="font-size:10pt;line-height:14.2667px;font-family:Arial,sans-serif;color:rgb(136,136,136)"><span>Confidentiality</span> Note:</span></b><span style="font-size:7.5pt;line-height:10.7px;font-family:Arial,sans-serif;color:rgb(136,136,136);background-color:white"> We care about protecting our proprietary information, <span>confidential</span> <wbr>material, and trade secrets. </span><span style="font-size:7.5pt;line-height:10.7px;font-family:Arial,sans-serif;color:rgb(136,136,136);background-color:white">This message may contain some or all of those things. Cruise will suffer material harm if anyone other than the intended recipient disseminates or takes any action based on this message. If you have received this message (including any attachments) in error, please delete it immediately and notify the sender promptly.</span>