Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: RPM packaging issue?
Date: Fri, 1 Jun 2012 10:10:55 -0500	[thread overview]
Message-ID: <4FC8DB7F.3070506@windriver.com> (raw)
In-Reply-To: <4FC81BF9.5050405@intel.com>

On 5/31/12 8:33 PM, Laurentiu Palcu wrote:
> Hi list,
>
> I was trying to build core-image-gtk-directfb and ended up with this error:
>
> Log data follows:
> | DEBUG: Executing shell function do_rootfs
> | ERROR: Function failed: do_rootfs (see
> /home/lau/yocto/build/tmp/work/qemux86-poky-linux/core-image-minimal-1.0-r0/temp/log.do_rootfs.4857
> for further information)
> | Generating solve db for /home/lau/yocto/build/tmp/deploy/rpm/qemux86...
> | Generating solve db for /home/lau/yocto/build/tmp/deploy/rpm/i586...
> | Generating solve db for /home/lau/yocto/build/tmp/deploy/rpm/all...
> | Generating solve db for /home/lau/yocto/build/tmp/deploy/rpm/all...
> | Processing task-core-boot...
> | Processing module-init-tools...
> | Unable to find package module-init-tools (module-init-tools)!
> NOTE: package core-image-minimal-1.0-r0: task do_rootfs: Failed
>
> module-init-tools is provided by kmod package and is in the RDEPENDS of
> task_base recipe.
>
> Then I tried to add module_init_tools to CORE_IMAGE_EXTRA_INSTALL and
> build core-image-minimal (just for testing), the same result.
>
> The interesting thing is that this didn't happen if the packaging format
> is ipk.
>
> Anybody know anything about this issue?

The IMAGE_INSTALL list has module-init-tools in it.  This list is based on 
package name and not "dependency" or "provide" name.  The package 
module-init-tools no longer exists in the system, there is only a runtime 
provide from the kmod package.

This ensures that any package that requires module-init-tools will work 
properly, but anyone adding module-init-tools to the IMAGE_INSTALL it will fail 
as you've seen above.

--Mark

> Thanks,
> Laurentiu
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core




  reply	other threads:[~2012-06-01 15:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-30  9:08 [PATCH 0/1] Fix browser crash on PPC edwin.zhai
2012-05-30  9:08 ` [PATCH 1/1] webkit-gtk: Use glib as unicode backend to avoid browser crash edwin.zhai
2012-05-30 16:40   ` Richard Purdie
2012-05-30 18:56     ` Gary Thomas
2012-06-01  0:56       ` Zhai, Edwin
2012-06-01  8:22       ` Richard Purdie
2012-06-01  1:33   ` RPM packaging issue? Laurentiu Palcu
2012-06-01 15:10     ` Mark Hatle [this message]
2012-05-30 11:05 ` [PATCH 0/1] Fix browser crash on PPC Gary Thomas
2012-05-30 12:05 ` Koen Kooi

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=4FC8DB7F.3070506@windriver.com \
    --to=mark.hatle@windriver.com \
    --cc=openembedded-core@lists.openembedded.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