From: Darren Hart <dvhart@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: init-ifupdown: do_package_ipk failing
Date: Mon, 13 May 2013 13:57:44 -0700 [thread overview]
Message-ID: <519153C8.6060708@linux.intel.com> (raw)
After removing a bbappend for init-ifupdown I am seeing failures in
do_package_ipk:
Build Configuration:
BB_VERSION = "1.19.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "Ubuntu-11.10"
TARGET_SYS = "i586-poky-linux"
MACHINE = "minnow"
DISTRO = "poky"
DISTRO_VERSION = "1.3+snapshot-20130513"
TUNE_FEATURES = "m32 core2"
TARGET_FPU = ""
meta-yocto = "master:94d31b0b36be389710bfb1c5d7aeacda92efad5b"
meta-minnow = "master:d474c4304dc1c9e9703fce0cd6a4329289681f92"
meta-intel = "master:624aada76d2de84bd0263065b112ed4e94798b6b"
meta = "master:94d31b0b36be389710bfb1c5d7aeacda92efad5b"
...
ERROR: Error executing a python function in
/build/yocto/master/minnow_201302231109
41/poky/meta/recipes-core/init-ifupdown/init-ifupdown_1.0.bb:
OSError: [Errno 2] No such file or directory:
'/build/yocto/master/minnow_201302231
10941/build/tmp/work/core2-poky-linux/init-ifupdown/1.0-r2/packages-split/init-ifup
down-dbg'
ERROR: Error executing a python function in
/build/yocto/master/minnow_201302231109
41/poky/meta/recipes-core/init-ifupdown/init-ifupdown_1.0.bb:
OSError: [Errno 2] No such file or directory:
'/build/yocto/master/minnow_201302231
10941/build/tmp/work/core2-poky-linux/init-ifupdown/1.0-r2/packages-split/init-ifup
down-dbg'
ERROR: The stack trace of python calls that resulted in this
exception/failure was:
ERROR: File "do_package_ipk", line 194, in <module>
ERROR:
ERROR: File "do_package_ipk", line 45, in do_package_ipk
ERROR:
ERROR: The code that was being executed was:
ERROR: 0190: bb.utils.unlockfile(lf)
ERROR: 0191:
ERROR: 0192:
ERROR: 0193:
ERROR: *** 0194:do_package_ipk(d)
ERROR: 0195:
ERROR: [From file: 'do_package_ipk', lineno: 194, function: <module>]
ERROR: 0041: basedir = os.path.join(os.path.dirname(root))
ERROR: 0042: arch = localdata.getVar('PACKAGE_ARCH', True)
ERROR: 0043: pkgoutdir = "%s/%s" % (outdir, arch)
ERROR: 0044: bb.mkdirhier(pkgoutdir)
ERROR: *** 0045: os.chdir(root)
ERROR: 0046: from glob import glob
ERROR: 0047: g = glob('*')
ERROR: 0048: try:
ERROR: 0049: del g[g.index('CONTROL')]
ERROR: [From file: 'do_package_ipk', lineno: 45, function: do_package_ipk]
ERROR: Function failed: do_package_ipk
ERROR: Logfile of failure stored in:
/build/yocto/master/minnow_20130223110941/build/tmp/work/core2-poky-linux/init-ifupdown/1.0-r0/temp/log.do_package_write_ipk.16210
ERROR: Task 1399
(/build/yocto/master/minnow_20130223110941/poky/meta/recipes-core/init-ifupdown/init-ifupdown_1.0.bb,
do_package_write_ipk) failed with exit code '1'
I have done cleansstate and cleanall, but the error is repeatable.
Is anyone else experiencing this with init-ifupdown and ipk packaging?
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Technical Lead - Linux Kernel
next reply other threads:[~2013-05-13 21:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-13 20:57 Darren Hart [this message]
2013-05-13 21:33 ` init-ifupdown: do_package_ipk failing Martin Jansa
2013-05-14 15:16 ` Darren Hart
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=519153C8.6060708@linux.intel.com \
--to=dvhart@linux.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