From: Peter Seebach <peter.seebach@windriver.com>
To: "Openembedded-core@lists.openembedded.org"
<Openembedded-core@lists.openembedded.org>
Subject: [PATCH 0/1] installed but unpackaged... foul lies and calumnies
Date: Thu, 24 Jan 2013 17:51:24 -0600 [thread overview]
Message-ID: <cover.1359071327.git.peter.seebach@windriver.com> (raw)
If a FILES_* variable has an unqualified path in it, this can result in
a file being sucessfully packaged, and yet, still showing up as
installed-but-unpackaged. Note: I had weird build problems with my oe-core
tree, but I tested this in a nearby poky tree and it worked there, anyway.
The following changes since commit 2e2a91025ca9c113365c810ce08b48201fe792b8:
Khem Raj (1):
systemd: Fix build on ppc
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib seebs/unpackaged
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=seebs/unpackaged
Peter Seebach (1):
package.bbclass: Consistency between packaging and unpackaged check
meta/classes/package.bbclass | 2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
next reply other threads:[~2013-01-25 0:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-24 23:51 Peter Seebach [this message]
2013-01-24 23:51 ` [PATCH 1/1] package.bbclass: Consistency between packaging and unpackaged check Peter Seebach
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=cover.1359071327.git.peter.seebach@windriver.com \
--to=peter.seebach@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 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.