All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randy Witt <randy.e.witt@linux.intel.com>
To: "Ng, Mei Yeen" <mei.yeen.ng@intel.com>,
	"yocto@yoctoproject.org" <yocto@yoctoproject.org>
Cc: "Hart, Darren" <darren.hart@intel.com>,
	"Witt, Randy E" <randy.e.witt@intel.com>
Subject: Re: Packages in packagegroup are not installed in image
Date: Thu, 23 Jul 2015 10:59:39 -0700	[thread overview]
Message-ID: <55B12B8B.7060509@linux.intel.com> (raw)
In-Reply-To: <62355CE5B24AE3438DF93AF114E1F91B2DBC9045@KMSMSX153.gar.corp.intel.com>

Hi Mei,

On 07/15/2015 10:40 AM, Ng, Mei Yeen wrote:
> Hi,
>
> I need help for issue where packages in packagegroup that compiles perfectly fine with core-images, but when verified in the image, they are not installed for some reason.
> My understanding was that packages listed under RDEPENDS in the packagegroup would get compiled and installed.
>
> Some packages would appear in 1 image and then disappear in the next compiled image.
> I'm seeing this when compiling with core-image-full-cmdline and core-image-sato.
>
> I have attached the following package group created:
>
> -        graphics package group- ldd would not be installed in the image
>
> -        build essentials extended package group - gdb were not install, gcc and mkdosfs will intermittently not install into the image

Could you perhaps provide the recipe that creates the package group and show how 
you are adding the package group to the image?

> Any help to shed some light on this is very much appreciated.
>
> Thanks,
> MY
>
>
>



  reply	other threads:[~2015-07-23 17:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-15 17:40 Packages in packagegroup are not installed in image Ng, Mei Yeen
2015-07-23 17:59 ` Randy Witt [this message]
2015-07-23 18:01   ` Randy Witt
2015-08-25  2:20   ` Ng, Mei Yeen
2015-08-25 20:04     ` Randy Witt
2015-09-30  4:09       ` Ng, Mei Yeen

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=55B12B8B.7060509@linux.intel.com \
    --to=randy.e.witt@linux.intel.com \
    --cc=darren.hart@intel.com \
    --cc=mei.yeen.ng@intel.com \
    --cc=randy.e.witt@intel.com \
    --cc=yocto@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.