Yocto Project Discussions
 help / color / mirror / Atom feed
From: "Yocto" <yocto@optimcloud.com>
To: yocto@lists.yoctoproject.org
Subject: Re: [yocto] dnf error coming while compiling core-image-sato image.
Date: Wed, 21 Oct 2020 12:00:23 +0700	[thread overview]
Message-ID: <2946109b-fe92-243c-87fb-296c406c1569@optimcloud.com> (raw)
In-Reply-To: <CAJw=dJ_QWnF3bnKCWEuW8PrX32c2nXOdbnA1rBD=Ah55QvpjEg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 3048 bytes --]


On 10/20/20 8:06 PM, NIKHIL PATIL wrote:
> I changed in local.conf (ostree related stuffs ), and put it for 
> compilation , that time i got these error
>
> On Tue, Oct 20, 2020 at 6:49 AM Randy MacLeod 
> <randy.macleod@windriver.com <mailto:randy.macleod@windriver.com>> wrote:
>
>     On 2020-10-18 6:41 a.m., NIKHIL PATIL wrote:
>     > Hi team ,
>     >        I am getting continuously dnf error, How we can
>     resolve these .
>
>     Hi Nikhil,
>
>     What exact steps did you take before getting this error and
>     what build host are you using?
>
>     Are you able to build core-image-minimal using oe-core/master
>     and the default local.conf for qemux86-64?
>
>     ../Randy
>
I can confirm that Ive also seen this trying to build in the Yocto build 
appliance I downloaded yesterday....



>     >
>     > core-image-sato-1.0-r0 do_rootfs: Could not invoke dnf. Command
>     >
>     '/data/pradeep/inti_dmsv/yocto_build/build/tmp/work/intel_corei7_64-poky-linux/core-image-sato/1.0-r0/recipe-sysroot-native/usr/bin/dnf
>
>     > -y -c
>     >
>     /data/pradeep/inti_dmsv/yocto_build/build/tmp/work/intel_corei7_64-poky-linux/core-image-sato/1.0-r0/rootfs/etc/dnf/dnf.conf
>
>     >
>     --setopt=reposdir=/data/pradeep/inti_dmsv/yocto_build/build/tmp/work/intel_corei7_64-poky-linux/core-image-sato/1.0-r0/rootfs/etc/yum.repos.d
>
>     >
>     --repofrompath=oe-repo,/data/pradeep/inti_dmsv/yocto_build/build/tmp/work/intel_corei7_64-poky-linux/core-image-sato/1.0-r0/oe-rootfs-repo
>
>     >
>     --installroot=/data/pradeep/inti_dmsv/yocto_build/build/tmp/work/intel_corei7_64-poky-linux/core-image-sato/1.0-r0/rootfs
>
>     >
>     --setopt=logdir=/data/pradeep/inti_dmsv/yocto_build/build/tmp/work/intel_corei7_64-poky-linux/core-image-sato/1.0-r0/temp
>
>     > -x packagegroup-core-apl-extra --nogpgcheck install
>     autoconf-archive dnf
>     > gstreamer1.0-vaapi iqvlinux jhi kernel-modules libtcti-device0
>     > libtcti-device-dev libtcti-device-staticdev libtcti-socket0
>     > libtcti-socket-dev libtcti-socket-staticdev libsapi0 libsapi-dev
>     > libsapi-staticdev libva mesa-glxinfo libmraa1 nodejs
>     > packagegroup-base-extended packagegroup-core-audio-essential
>     > packagegroup-core-boot packagegroup-core-buildessential-extended
>     > packagegroup-core-graphics-essential packagegroup-core-ssh-dropbear
>     > packagegroup-core-tools-testapps packagegroup-core-x11-base
>     > packagegroup-core-x11-sato psplash rpm run-postinsts swig
>     tpm2-abrmd
>     > usb-modeswitch usb-modeswitch-data va-intel wayland weston
>     > weston-examples xinit-env xserver-xorg locale-base-en-us
>     > locale-base-en-gb' returned 1:
>     > Added oe-repo repo from
>     >
>     /data/pradeep/inti_dmsv/yocto_build/build/tmp/work/intel_corei7_64-poky-linux/core-image-sato/1.0-r0/oe-rootfs-repo
>     >
>     >
>     >
>     >
>     >
>
>
>     -- 
>     # Randy MacLeod
>     # Wind River Linux
>
>
> 
>

[-- Attachment #2: Type: text/html, Size: 5039 bytes --]

  parent reply	other threads:[~2020-10-21  5:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-18 10:41 dnf error coming while compiling core-image-sato image NIKHIL PATIL
2020-10-20  1:19 ` [yocto] " Randy MacLeod
2020-10-20 13:06   ` NIKHIL PATIL
2020-10-20 14:20     ` Randy MacLeod
2020-10-21  4:53       ` NIKHIL PATIL
2020-10-21  5:00     ` Yocto [this message]
2020-10-21 10:38       ` NIKHIL PATIL
2020-10-21 11:28         ` Yocto

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=2946109b-fe92-243c-87fb-296c406c1569@optimcloud.com \
    --to=yocto@optimcloud.com \
    --cc=yocto@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