From: Saul Wold <sgw@linux.intel.com>
To: Mark Hatle <mark.hatle@windriver.com>
Cc: 'Patches and discussions about the oe-core layer'
<openembedded-core@lists.openembedded.org>
Subject: RPM and libmagic
Date: Mon, 26 Sep 2011 16:05:13 -0700 [thread overview]
Message-ID: <4E810529.2000708@linux.intel.com> (raw)
Mark,
I recently found a problem with RPM and libmagic, specificly the rpmdeps
command as it's used in package.bbclass. The issue being that it was not
finding the correct magic.mgc file. I notice that we wrap the other RPM
commands, but not rpmdeps.
Additionally, as I have discovered the wrappers that we have in place
currently does not define a MAGIC environment variable to correct the
location.
I know rpm and friends are an important part of OE packaging, so I
wanted to check with you first about the correct location to set this,
if we should use the MAGIC or pass a --define '%_rpmfc_magic_path ...'
on the command line.
Please advise, I know you are traveling, and I can implement the change
once we figure out the correct approach.
Thanks
--
Sau!
Saul Wold
Yocto Component Wrangler @ Intel
Yocto Project / Poky Build System
next reply other threads:[~2011-09-26 23:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-26 23:05 Saul Wold [this message]
2011-09-26 23:36 ` RPM and libmagic Mark Hatle
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=4E810529.2000708@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=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 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.