Thank you khem raj for your input, I have already tried with

INCOMPATIBLE_LICENSE = "GPLv3+ LGPLv3+ AGPLv3+"
 
And this also

INCOMPATIBLE_LICENSE = "GPLv3* LGPLv3* AGPLv3*"

But no luck, still I can see same output


rootfs/usr/share/common-license/package/libgcrypt-lic/recipeinfo

LICENSE: GPLV2+ &LGPLV2.1+ &GPLV3+
PR: r0
 PV : 1.8.4


On Fri 24 May, 2019, 5:25 AM Khem Raj, <raj.khem@gmail.com> wrote:


On 5/23/19 2:42 AM, virendra kumar thakur wrote:
>
>
> Hello team,
>
> I am trying to build yocto image without GPLv3 package, I have added
> below things in local.conf and enable meta-gplv2 layer.
>
> INCOMPATIBLE_LICENSE = "GPL-3.0 LGPL-3.0 AGPL-3. 0" in local.conf.

Can you try adding GPLv3+ to INCOMPATIBLE_LICENSE and see if that helps ?

>
> After verifying from package.manifest and license.manifest file in
> build/tmp/deploy/license/ directory I observe that no GPLv3 package is
> present in rootfs.
>
> But I can see in
> rootfs/usr/share/common-license/package/libgcrypt-lic/recipeinfo
>
> LICENSE: GPLV2+ &LGPLV2.1+ &GPLV3+
> PR: r0
> PV : 1.8.4
>
> Is present..
>
> My doubt is why any GPLv3 is present in common-license directory?
>
> From: "Burton, Ross" <ross.burton@intel.com <mailto:ross.burton@intel.com>>
> To: virendra kumar thakur <coolveer07@gmail.com
> <mailto:coolveer07@gmail.com>>
> Cc: Yocto-mailing-list <yocto@yoctoproject.org
> <mailto:yocto@yoctoproject.org>>
> Subject: Re: [yocto] GPLv3 package present in rootfs
>
> On Wed, 22 May 2019 at 06:26, virendra kumar thakur
> <coolveer07@gmail.com <mailto:coolveer07@gmail.com>> wrote:
>> still some package gnutls, libidn2, libassuan, are added into rootfs.
>
> Randomly picking libassuan:
>
> LICENSE_${PN} = "LGPLv2.1+"
>
> The library itself is LGPL-2.  Have you verified the *package*
> licenses for what is actually going into the image?
>
> Ross
>
>
>
>