From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Otavio Salvador <otavio.salvador@ossystems.com.br>,
Jason Wessel <jason.wessel@windriver.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] image.bbclass: Use deltask instead of noexec for package_write_rpm
Date: Sat, 03 Mar 2018 15:50:15 +0000 [thread overview]
Message-ID: <1520092215.3436.54.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAP9ODKrOspi_MOPfaV3bHZyc9iZfOCgyJO4Db8urtpyYUseyMQ@mail.gmail.com>
On Sat, 2018-03-03 at 12:46 -0300, Otavio Salvador wrote:
> On Fri, Mar 2, 2018 at 5:27 PM, Jason Wessel <jason.wessel@windriver.
> com> wrote:
> >
> > If you install an image into another image (this is the case for
> > custom initrd for example), it will fail with a non obvious python
> > backtrace. This patch modifies the package_manager.py print which
> > package causes the failure for the future, if it is missing a
> > manifest.
> >
> > The error you get looks like this:
> >
> > oe-core/meta/lib/oe/package_manager.py', lineno: 534, function:
> > create_packages_dir
> > 0530:
> > 0531: for dep in rpmdeps:
> > 0532: c = taskdepdata[dep][0]
> > 0533: manifest, d2 =
> > oe.sstatesig.find_sstate_manifest(c, taskdepdata[dep][2], taskname,
> > d, multilibs)
> > *** 0534: if not os.path.exists(manifest):
> > 0535: continue
> > 0536: with open(manifest, "r") as f:
> > 0537: for l in f:
> > 0538: l = l.strip()
> > File: '/usr/lib/python3.5/genericpath.py', lineno: 19, function:
> > exists
> > 0015:# This is false for dangling symbolic links on systems
> > that support them.
> > 0016:def exists(path):
> > 0017: """Test whether a path exists. Returns False for
> > broken symbolic links"""
> > 0018: try:
> > *** 0019: os.stat(path)
> > 0020: except OSError:
> > 0021: return False
> > 0022: return True
> > 0023:
> > Exception: TypeError: stat: can't specify None for path argument
> >
> > The root cause of the problem was determined to be the noexec
> > clause
> > in the image.bbclass. When the package_write_rpm task runs it
> > expects
> > that a manifest will be generated. Not running the task eliminates
> > the problem.
> >
> > Signed-off-by: Jason Wessel <jason.wessel@windriver.com>
> What about the other image types?
FWIW I'm testing:
http://git.yoctoproject.org/cgit.cgi/poky/commit/?h=master-next&id=d77755d02f23ba410a2c55596c4538b8c5c2f63a
(but haven't posted it yet, I will shortly, just wanted to check it was
roughly going to work first).
I'd propose taking my patch above along with Jason's patch rewritten to
add the bb.fatal().
Cheers,
Richard
next prev parent reply other threads:[~2018-03-03 15:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-02 20:27 [PATCH] image.bbclass: Use deltask instead of noexec for package_write_rpm Jason Wessel
2018-03-03 15:46 ` Otavio Salvador
2018-03-03 15:50 ` Richard Purdie [this message]
2018-03-05 13:52 ` Jason Wessel
2018-03-05 13:56 ` Jason Wessel
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=1520092215.3436.54.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=jason.wessel@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=otavio.salvador@ossystems.com.br \
/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