On 02/12/2018 01:08 PM, robert_jos...@selinc.com wrote:
> I'm working with the pyro release, and noticed that it's still using
> openssl 1.0.2k. The latest version in the 1.0.2 series is 1.0.2n, which is
> already available on master. Is there a reason that the newer version
> hasn't made it back to pyro (or rocko, which is on 1.0.2m)?
openssl 1.1 was added and the openssl files got restructured making
simple cherry-picking not an option for older releases.
1.0.2n hit master 7 days ago, sorry for the delay.
1.0.2n is now in stable/rocko-next and will migrate to rocko when
> I know new
> package versions are not normally backported, but looking at the change
> log, I only see one change mentioned that is not a CVE fix (the 1.0.2l
> I can send patches to bring 1.0.2n to rocko and pyro if they will be
Openembedded-core mailing list