| Message ID | 20260917063747.1037155-1-UpStream_IP-SK@bmwtechworks.in |
|---|---|
| State | New |
| Headers | show |
| Series | [master] libgcrypt: Update license for dbg package | expand |
Hi, On Thu Sep 17, 2026 at 8:37 AM CEST, Sana Kazi via lists.openembedded.org wrote: > From: Sana Kazi <Kazi.S@bmwtechworks.in> > > Set LICENSE for libgcrypt-dbg as "LGPL-2.1-or-later" Our recipe for libgcrypt was updated to 1.12.4 on master. Can you rebase and re-send the patch? Thanks, Antonin
Hi, On Thu, 2026-09-17 at 12:07 +0530, Sana Kazi wrote: > From: Sana Kazi <Kazi.S@bmwtechworks.in> > > Set LICENSE for libgcrypt-dbg as "LGPL-2.1-or-later" The commit message here says what you are changing, but not why. Please include a brief explanation of why the -dbg package license is different. Best regards,
diff --git a/meta/recipes-support/libgcrypt/libgcrypt_1.12.3.bb b/meta/recipes-support/libgcrypt/libgcrypt_1.12.3.bb index af5f00dbfa..500033a587 100644 --- a/meta/recipes-support/libgcrypt/libgcrypt_1.12.3.bb +++ b/meta/recipes-support/libgcrypt/libgcrypt_1.12.3.bb @@ -59,6 +59,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 \