Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Alejandro Hernandez <alejandro.hernandez@linux.intel.com>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] insane.bbclass: Enhance file-rdeps QA check
Date: Wed, 25 Feb 2015 15:43:03 -0600	[thread overview]
Message-ID: <54EE41E7.4070106@linux.intel.com> (raw)
In-Reply-To: <CAP9ODKr+kp=+yez1ibVBuwUyuc1V1D0gitaANhgBoGp8=rRXAQ@mail.gmail.com>


On 23/02/15 13:49, Otavio Salvador wrote:
> @@ -34,7 +34,7 @@ WARN_QA ?= "ldflags useless-rpaths rpaths staticdev libdir xorg-driver-abi \
>   ERROR_QA ?= "dev-so debug-deps dev-deps debug-files arch pkgconfig la \
>               perms dep-cmp pkgvarcheck perm-config perm-line perm-link \
>               split-strip packages-list pkgv-undefined var-undefined \
> -            version-going-backwards \
> +            version-going-backwards  symlink-to-sysroot\
> Is this a 'development change' which should be dropped or another
> change which should go in another commit?
Yes, development change, this should go in WARN_QA

>
> Please take a look on the 'sed'  warning when building with ptest. It
> is a 'false-positive' failure.
>
As discussed in the IRC this is related to a different bug, its a 
"build-deps" bug not "file-rdeps", I would gladly fix it, although I am 
not able to reproduce it so far, if anyone can and has some info, I'd 
appreciate it.


  reply	other threads:[~2015-02-25 21:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-23 19:04 [PATCH] insane.bbclass: Enhance file-rdeps QA check Alejandro Hernandez
2015-02-23 19:49 ` Otavio Salvador
2015-02-25 21:43   ` Alejandro Hernandez [this message]
2015-02-24 23:44 ` 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=54EE41E7.4070106@linux.intel.com \
    --to=alejandro.hernandez@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=otavio@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