From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-ruby][PATCH] v2 bundler: Fix QA new Error
Date: Mon, 13 Apr 2015 13:04:09 +0200 [thread overview]
Message-ID: <20150413110409.GD2330@jama> (raw)
In-Reply-To: <1428685125-20255-1-git-send-email-akuster808@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1380 bytes --]
On Fri, Apr 10, 2015 at 09:58:45AM -0700, Armin Kuster wrote:
> V2: drop version value in file path
I've taken this patch before branching fido, but I had to fix commit
message a bit.
Please notice extra "v2 " in summary line.
"V2: .*" belongs under --- so that it's visible in review on e-mail, but
not part of commit message itself.
> ERROR: QA Issue: bundler: Files/directories were installed but not shipped
> /usr/lib/ruby/gems/2.2.0/build_info
> /usr/lib/ruby/gems/2.2.0/extensions [installed-vs-shipped]
>
> Signed-off-by: Armin Kuster <akuster808@gmail.com>
> ---
> meta-ruby/recipes-devtools/ruby/bundler_git.bb | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/meta-ruby/recipes-devtools/ruby/bundler_git.bb b/meta-ruby/recipes-devtools/ruby/bundler_git.bb
> index 2adde4d..fc73001 100644
> --- a/meta-ruby/recipes-devtools/ruby/bundler_git.bb
> +++ b/meta-ruby/recipes-devtools/ruby/bundler_git.bb
> @@ -26,4 +26,6 @@ SRC_URI = " \
>
> inherit ruby
>
> +FILES_${PN} += "${libdir}/ruby/gems"
> +
> BBCLASSEXTEND = "native"
> --
> 2.3.5
>
> --
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]
prev parent reply other threads:[~2015-04-13 11:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-10 16:58 [meta-ruby][PATCH] v2 bundler: Fix QA new Error Armin Kuster
2015-04-13 11:04 ` Martin Jansa [this message]
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=20150413110409.GD2330@jama \
--to=martin.jansa@gmail.com \
--cc=openembedded-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox