Signed-off-by: Fabio Berton <fabio.berton@...> --- conf/layer.conf | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/conf/layer.conf b/conf/layer.conf index

there is that. And looking at the history on the server, most of the existing tags came from the web. But a hashtag is created automatically when using '#' in the email subject. that's how #define was

Thank you all. The new layer did the trick for me also. Regards, Mike

From: Jeremy Puhlman <jpuhlman@...> Signed-off-by: Jeremy A. Puhlman <jpuhlman@...> --- .../recipes-core/initrdscripts/initramfs-cgl-boot_1.0.bb | 3 +-- 1 file changed, 1

I doubt people that actually send emails to the list use #hashtags. But the new list server provides this posting feature for anyone to address the list and requests poster to add #hashtags - very

FYI: I don't know if I missed the memo/tweet about the email archive feature but I just noticed that the new archive site will index emails by hashtag: https://lists.yoctoproject.org/g/yocto

Timm, Did you ever get the gutenprint recipe to work? Are you able to add it to meta-oe or share what you have done so far here? ../Randy -- # Randy MacLeod # Wind River Linux

A new mailing list was recently introduced for documentation related discussions including patches. And the domain for Yocto mailing lists was changed with the migration to groups.io. Change-Id:

It was merged on the basis it was a good starter and followup patches are easy and very welcome. Cheers, Richard

Thanks for pulling this together. I see the review window is down to an hour before merging. Is code review by twitter the next new thing ; ) I responded the patches on the docs

Release notes draft attached, including a dedication to Scott (wasn't sure where to put that so I've just left it at the top) and contributors list. Let me know if you notice anything

FYI, we’re doing the same internally (vendor supplied FIPS supported openssl 1.0.2), and the layer Armin suggests worked for us on zeus with minimal additional tweaking. Good luck! -Sean

Have had a chance to look at this layer? http://git.yoctoproject.org/cgit/cgit.cgi/meta-openssl102-fips/ - armin

I think python2 *recipe* requires openssl 1.1, but python2 itself will work just fine with openssl 1.0. So you only need to adjust the dependency, there are several ways to do that. Alex

I'm working on a set of platforms that have a FIPs certified OpenSSL. We are at version 1.0.2l. I've found that the new version of python in Zeus (2.7.17) requires a newer version of OpenSSL

Thanks for the summary Ajam. ../Randy -- # Randy MacLeod # Wind River Linux

Hello Richard,

Hi Sangeeta/Vineela, Thanks for the QA run! The TSC met today and this was one of the topics discussed. We would have time for another build and QA run but none of the queued changes or open bugs

You replied faster than I could, so I turfed my answer! See below. Everything is good go to go, and I can point out what has been in place for a while: linux-yocto master is tracking mainline

My goal here was to minimize the maintenance required for this BSP layer to get newer kernels. Using the linux-yocto kernel in OE-core is quite simple (as this patch shows) and allows us to piggyback