Alternatively if you're using RPMs, you can set PACKAGE_EXCLUDE = "python3-core":
Error: Problem 1: conflicting requests - nothing provides python3-core needed by dnf-2.7.5-r0.corei7_64 Problem 2: conflicting requests - nothing provides python3-core needed by rpm-1:4.14.2-r0.corei7_64 In this case, Python 3 is in my image because I have package-management on, which needs Python 3. Ross On Wed, 17 Oct 2018 at 10:43, Burton, Ross <ross.bur...@intel.com> wrote: > > Easiest way to determine what is pulling it in is to try removing the > package on the target using the package manager. That will tell you > what dependencies are keeping it in. > > Ross > On Wed, 17 Oct 2018 at 08:32, Marwen BRIKCHA <marwen.brik...@gmail.com> wrote: > > > > Yes. I've seen compilation log and it does do_install in final image. > > It's installed in /usr/lib64/python3.5 on RootFS. > > > > Le mer. 17 oct. 2018, à 00 h 48, Burton, Ross <ross.bur...@intel.com> a > > écrit : > >> > >> On Tue, 16 Oct 2018 at 14:06, Marwen BRIKCHA <marwen.brik...@gmail.com> > >> wrote: > >> > > >> > because, when i run : > >> > : > >> > $> bitbake -v opencv > >> > I can see that python3 is fetched, configure, ... etc > >> > So, i think it the responsible for this. > >> > >> Please remember to CC the list. > >> > >> Python being built doesn't lead to Python being installed in the > >> image. Have a look at the image manifest (in deploy/images) or look > >> at what is actually installed inside the image. > >> > >> Ross -- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto