Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "David Nyström" <david.nystrom@enea.com>
To: "David Nyström" <david.nystrom@enea.com>,
	"Laurentiu Palcu" <laurentiu.palcu@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 00/49] Rootfs/image generation refactoring (cover letter only)
Date: Tue, 4 Feb 2014 15:49:25 +0100	[thread overview]
Message-ID: <52F0FDF5.8000603@enea.com> (raw)
In-Reply-To: <52F0F464.5060107@enea.com>

On 2014-02-04 15:08, David Nyström wrote:
> On 2014-02-03 17:47, Laurentiu Palcu wrote:
>> On Mon, Feb 03, 2014 at 03:32:49PM +0100, David Nyström wrote:
>>> On 2014-02-03 12:38, Laurentiu Palcu wrote:
>>>> Hi all,
>>>>
>>>
>>> Have you tested that BUILD_IMAGES_FROM_FEEDS functionality is not
>>> broken by these commits ?
>> No, I did not test this. I tried to test it on master though and it
>> doesn't seem to work...
>
> Whats in master worked for me not too long ago with IPK at least.
>
>> Anyway, if you have a working environment, can
>> you give it a test? Technically, the feeds are added to the main
>> opkg.conf file in OPKG_PREPROCESS_CMD. And this functionality is
>> supposed to work.
>>
>> laurentiu
>
> $ grep -r FEED conf/local.conf
> BUILD_IMAGES_FROM_FEEDS="1"
> IPK_FEED_URI="file:///media/sdb5/repo/build/tmp/deploy/"
>
> $ bitbake -c rootfs core-image-minimal
>
> DEBUG: Executing python function rootfs_process_ignore
> DEBUG: Python function rootfs_process_ignore finished
> DEBUG: Executing python function rootfs_runtime_mapping
> DEBUG: Python function rootfs_runtime_mapping finished
> DEBUG: Executing python function do_rootfs
> NOTE: ###### Generate rootfs #######
> ERROR: There are no packages in /media/sdb5/bld/tmp/deploy/ipk!
> DEBUG: Python function do_rootfs finished
> ERROR: Function failed: do_rootfs
> /media/sdb5/bld/tmp/work/qemux86-poky-linux/core-image-minimal/1.0-r0/temp/log.do_rootfs.25006
> (END)
>
> $ grep -r "There are no packages in" ../poky-contrib/*
> Binary file ../poky-contrib/meta/lib/oe/package_manager.pyc matches
> ../poky-contrib/meta/lib/oe/package_manager.py: bb.fatal("There are no
> packages in %s" % self.deploy_dir)
> ../poky-contrib/meta/lib/oe/package_manager.py: bb.fatal("There are no
> packages in %s!" % self.deploy_dir)
> ../poky-contrib/meta/lib/oe/package_manager.py: bb.fatal("There are no
> packages in %s" % self.deploy_dir)
> d
>
> Br,
> David
>

Oops, bug on my behalf in above example, but it still fails the same way 
when using a correct IPK_FEED_URI.

IPK_FEED_URIS += " \
            all##file:///media/sdb5/repo/build/tmp/deploy/ipk/all \
	   ${MACHINE}##file:///media/sdb5/repo/build/tmp/deploy/ipk/${MACHINE} \
 
${TARGET_ARCH}##file:///media/sdb5/repo/build/tmp/deploy/ipk/${TARGET_ARCH} 
\
	   "




  reply	other threads:[~2014-02-04 14:49 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-03 11:38 [PATCH 00/49] Rootfs/image generation refactoring (cover letter only) Laurentiu Palcu
2014-02-03 11:54 ` Laurentiu Palcu
2014-02-03 14:32 ` David Nyström
2014-02-03 16:47   ` Laurentiu Palcu
2014-02-04 14:08     ` David Nyström
2014-02-04 14:49       ` David Nyström [this message]
2014-02-04 15:34         ` Laurentiu Palcu
2014-02-04 15:40           ` David Nyström
2014-02-05 10:07 ` [PATCH v2 00/50] " Laurentiu Palcu
2014-02-05 10:58   ` David Nystrom
2014-02-05 12:09     ` David Nyström
2014-02-05 14:43       ` Laurentiu Palcu
2014-02-05 18:00         ` David Nystrom
2014-02-05 15:05 ` [PATCH v3 00/51] " Laurentiu Palcu
2014-02-10  7:53   ` [PATCH v4 00/52] " Laurentiu Palcu
2014-02-10 12:15 ` [PATCH v5 00/53] " Laurentiu Palcu
2014-02-11  8:42   ` David Nyström
2014-02-11  8:50     ` Laurentiu Palcu
2014-02-11  8:56       ` David Nyström
2014-02-11  9:36         ` David Nyström
2014-02-11 14:33   ` David Nyström
2014-02-11 14:50     ` David Nyström

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=52F0FDF5.8000603@enea.com \
    --to=david.nystrom@enea.com \
    --cc=laurentiu.palcu@intel.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