Patches for Yocto layers and components that do not have their own list
 help / color / mirror / Atom feed
From: Scott Murray <scott.murray@konsulko.com>
To: yocto-patches@lists.yoctoproject.org
Subject: [meta-security][blacksail][PATCH 0/5] Branch initialization (cover letter only)
Date: Thu, 29 Oct 2026 14:34:19 -0400	[thread overview]
Message-ID: <cover.1793298086.git.scott.murray@konsulko.com> (raw)

My apologies for the delay, this got hung up by travel and a few
issues cropping up in CI.  I have gone ahead and pushed this to
unblock folks since the glome and ding-libs changes are required
build break fixes, and should not be contentious.

I have a master branch update cooking that fixes another new build
breakage, it should be out later today or early tomorrow, and then
I plan to get on scarthgap update out for early next week.

Scott


Changes:

Khem Raj (1):
  layer: Add blacksail YP 6.1 to compatible releases

Scott Murray (4):
  meta-parsec: prune LAYERSERIES_COMPAT
  glome: update branch name
  kas: Switch to blacksail branch
  ding-libs: update to 0.7.0

 conf/layer.conf                               |  2 +-
 kas/kas-security-base.yml                     |  8 ++++----
 meta-hardening/conf/layer.conf                |  2 +-
 meta-integrity/conf/layer.conf                |  2 +-
 meta-parsec/conf/layer.conf                   |  2 +-
 meta-tpm/conf/layer.conf                      |  2 +-
 recipes-security/ding-libs/ding-libs_0.7.0.bb | 11 +++++++++++
 recipes-security/glome/glome_git.bb           |  2 +-
 recipes-security/libdhash/ding-libs_0.6.1.bb  | 12 ------------
 9 files changed, 21 insertions(+), 22 deletions(-)
 create mode 100644 recipes-security/ding-libs/ding-libs_0.7.0.bb
 delete mode 100644 recipes-security/libdhash/ding-libs_0.6.1.bb

-- 
2.56.0


                 reply	other threads:[~2026-10-29 18:34 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=cover.1793298086.git.scott.murray@konsulko.com \
    --to=scott.murray@konsulko.com \
    --cc=yocto-patches@lists.yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox