Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Phil Blundell <philb@gnu.org>
To: Saul Wold <sgw@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] sstate: Add detail to shared area warning
Date: Tue, 02 Oct 2012 23:00:53 +0100	[thread overview]
Message-ID: <1349215253.4422.79.camel@x121e.pbcl.net> (raw)
In-Reply-To: <1349215201-30117-1-git-send-email-sgw@linux.intel.com>

On Tue, 2012-10-02 at 15:00 -0700, Saul Wold wrote:
> -        bb.warn("The recipe is trying to install files into a shared area when those files already exist. Those files are:\n   %s" % "\n   ".join(match))
> +        bb.warn("The %s recipe is trying to install files into a shared area when those files already exist (please fix %s). Those files are:\n   %s" % (d.getVar('PN', True), d.getVar('FILE', True), "\n   ".join(match)))

That seems potentially misleading: the file that needs fixing isn't
necessarily the one that triggers this warning.  What would be ideal
would be to have it output the names of all recipes that have tried to
stage the files in question so that the user can make an informed
decision about which one ought to be putting them there.

p.





  reply	other threads:[~2012-10-02 22:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-02 22:00 [PATCH] sstate: Add detail to shared area warning Saul Wold
2012-10-02 22:00 ` Phil Blundell [this message]
2012-10-02 22:06   ` Saul Wold
2012-10-02 22:05     ` Phil Blundell
2012-10-02 22:11   ` Martin Jansa
2012-10-02 22:22     ` Richard Purdie
2012-10-03  1:00       ` McClintock Matthew-B29882
2012-10-02 22:20   ` Richard Purdie

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=1349215253.4422.79.camel@x121e.pbcl.net \
    --to=philb@gnu.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=sgw@linux.intel.com \
    /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