From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-core@lists.openembedded.org,
Christopher Larson <chris_larson@mentor.com>
Cc: openembedded-commits@lists.openembedded.org
Subject: Re: [oe-commits] Christopher Larson : packagegroup-base-vfat: include dosfsprogs
Date: Tue, 11 Jun 2013 19:07:04 +0200 [thread overview]
Message-ID: <20130611170704.GK3233@jama> (raw)
In-Reply-To: <20130611144932.08F545048D@opal>
[-- Attachment #1: Type: text/plain, Size: 2590 bytes --]
On Tue, Jun 11, 2013 at 02:49:32PM +0000, git@git.openembedded.org wrote:
> Module: openembedded-core.git
> Branch: master
> Commit: 4ec66dc5f38913056942e1288c0b01a00ea0551f
> URL: http://git.openembedded.org/?p=openembedded-core.git&a=commit;h=4ec66dc5f38913056942e1288c0b01a00ea0551f
>
> Author: Christopher Larson <chris_larson@mentor.com>
> Date: Mon Jun 10 13:47:06 2013 -0700
>
> packagegroup-base-vfat: include dosfsprogs
>
> The ext2 group includes e2fsprogs, so this is consistent and should be
> appropriate, I think.
>
> Signed-off-by: Christopher Larson <chris_larson@mentor.com>
> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Isn't it called dosfstools?
$ find openembedded-core/ -name dos\*
openembedded-core/meta/recipes-devtools/dosfstools
openembedded-core/meta/recipes-devtools/dosfstools/dosfstools_2.11.bb
openembedded-core/meta/recipes-devtools/dosfstools/dosfstools
openembedded-core/meta/recipes-devtools/dosfstools/dosfstools/dosfstools-msdos_fs-types.patch
and no RPROVIDES in dosfstools recipe ->
ERROR: Nothing RPROVIDES 'dosfsprogs' (but /OE/shr-core/openembedded-core/meta/recipes-core/packagegroups/packagegroup-base.bb RDEPENDS on or otherwise requires it)
NOTE: Runtime target 'dosfsprogs' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['dosfsprogs']
NOTE: Runtime target 'packagegroup-base-extended' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['packagegroup-base-extended', 'dosfsprogs']
>
> ---
>
> .../packagegroups/packagegroup-base.bb | 3 ++-
> 1 files changed, 2 insertions(+), 1 deletions(-)
>
> diff --git a/meta/recipes-core/packagegroups/packagegroup-base.bb b/meta/recipes-core/packagegroups/packagegroup-base.bb
> index 799e12a..061c1a7 100644
> --- a/meta/recipes-core/packagegroups/packagegroup-base.bb
> +++ b/meta/recipes-core/packagegroups/packagegroup-base.bb
> @@ -179,7 +179,8 @@ RRECOMMENDS_packagegroup-base-vfat = "\
> kernel-module-msdos \
> kernel-module-vfat \
> kernel-module-nls-iso8859-1 \
> - kernel-module-nls-cp437"
> + kernel-module-nls-cp437 \
> + dosfsprogs"
>
> SUMMARY_packagegroup-base-alsa = "ALSA sound support"
> RDEPENDS_packagegroup-base-alsa = "\
>
> _______________________________________________
> Openembedded-commits mailing list
> Openembedded-commits@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-commits
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
next parent reply other threads:[~2013-06-11 17:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20130611144932.08F545048D@opal>
2013-06-11 17:07 ` Martin Jansa [this message]
2013-06-11 17:08 ` [oe-commits] Christopher Larson : packagegroup-base-vfat: include dosfsprogs Christopher Larson
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=20130611170704.GK3233@jama \
--to=martin.jansa@gmail.com \
--cc=chris_larson@mentor.com \
--cc=openembedded-commits@lists.openembedded.org \
--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.