Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Sana Kazi <UpStream_IP-SK@bmwtechworks.in>
To: openembedded-core@lists.openembedded.org
Cc: Sana Kazi <Kazi.S@bmwtechworks.in>
Subject: [oe-core][master][PATCH] libgcrypt: Update license for dbg package
Date: Thu, 17 Sep 2026 13:36:32 +0530	[thread overview]
Message-ID: <20260917080632.1039202-1-UpStream_IP-SK@bmwtechworks.in> (raw)

From: Sana Kazi <Kazi.S@bmwtechworks.in>

Set LICENSE for libgcrypt-dbg as "LGPL-2.1-or-later"
as the files used in dbg package use LGPL-2.1-or-later.

Signed-off-by: Sana Kazi <Kazi.S@bmwtechworks.in>
---
 meta/recipes-support/libgcrypt/libgcrypt_1.12.4.bb | 1 +
 1 file changed, 1 insertion(+)

diff --git a/meta/recipes-support/libgcrypt/libgcrypt_1.12.4.bb b/meta/recipes-support/libgcrypt/libgcrypt_1.12.4.bb
index 1b2b1dc13b..27b9d7fa15 100644
--- a/meta/recipes-support/libgcrypt/libgcrypt_1.12.4.bb
+++ b/meta/recipes-support/libgcrypt/libgcrypt_1.12.4.bb
@@ -9,6 +9,7 @@ SECTION = "libs"
 LICENSE = "BSD-3-Clause AND GPL-2.0-or-later AND LGPL-2.1-or-later"
 LICENSE:${PN} = "BSD-3-Clause AND LGPL-2.1-or-later"
 LICENSE:${PN}-dev = "GPL-2.0-or-later AND LGPL-2.1-or-later"
+LICENSE:${PN}-dbg = "LGPL-2.1-or-later"
 
 LIC_FILES_CHKSUM = "file://COPYING;md5=570a9b3749dd0463a1778803b12a6dce \
                     file://COPYING.LIB;md5=4bf661c1e3793e55c8d1051bc5e0ae21 \
-- 
2.43.0



             reply	other threads:[~2026-09-17 12:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-17  8:06 Sana Kazi [this message]
2026-09-21 20:27 ` [oe-core][master][PATCH] libgcrypt: Update license for dbg package Richard Purdie
  -- strict thread matches above, loose matches on Subject: below --
2026-09-17  6:37 Sana Kazi
2026-09-17  7:11 ` Antonin Godard
2026-09-17  7:52 ` Paul Barker

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=20260917080632.1039202-1-UpStream_IP-SK@bmwtechworks.in \
    --to=upstream_ip-sk@bmwtechworks.in \
    --cc=Kazi.S@bmwtechworks.in \
    --cc=openembedded-core@lists.openembedded.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