<div dir="ltr"><div dir="ltr"><div dir="ltr"><div class="gmail_quote"><div dir="ltr">On Tue, Aug 28, 2018 at 12:23 PM Alexander Kanavin <<a href="mailto:alex.kanavin@gmail.com">alex.kanavin@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">From: Alexander Kanavin <<a href="mailto:alexander.kanavin@linux.intel.com" target="_blank">alexander.kanavin@linux.intel.com</a>><br>
<br>
I believe the time has come to do this: openssl 1.0 upstream support stops at the end<br>
of 2019, and we do not want a situation where a supported YP release contains an<br>
unsupported version of a critical security component.<br>
<br>
Openssl 1.0 can still be utilized by depending on 'openssl10' recipe.<br></blockquote><div><br></div><div>This still isn't true for most recipes, as long as there is something depending on openssl in the dependency tree, it will cause do_prepare_recipe_sysroot failures like last time</div><div><br></div><div>ERROR: The file /usr/lib/libssl.so is installed by both openssl10 and openssl, aborting</div><div>DEBUG: Python function extend_recipe_sysroot finished</div><div>DEBUG: Python function do_prepare_recipe_sysroot finished</div><div>ERROR: Function failed: extend_recipe_sysroot</div><div><br></div><div>From 15 failures caused by openssl-1.1 detected in my builds, just changing DEPENDS from openssl to openssl10 didn't help in any case.</div><div><br></div><div>Regards,</div></div></div></div></div>