From: Tom Rini <trini@konsulko.com>
To: akuster808 <akuster808@gmail.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [warrior][v2][PATCH] README: updated Maintainers list for Warrior
Date: Wed, 1 May 2019 12:29:53 -0400 [thread overview]
Message-ID: <20190501162953.GC31207@bill-the-cat> (raw)
In-Reply-To: <de5ac985-9b63-c19a-5c73-71ae0d684c04@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3123 bytes --]
On Wed, May 01, 2019 at 09:24:31AM -0700, akuster808 wrote:
>
>
> On 5/1/19 9:00 AM, Tom Rini wrote:
> > On Wed, May 01, 2019 at 08:41:03AM -0700, Armin Kuster wrote:
> >> Signed-off-by: Armin Kuster <akuster808@gmail.com>
> >>
> >> [v2]
> >> bump bitbake to warrior version
> >> ---
> >> README | 2 +-
> >> meta-filesystems/README | 12 ++++++------
> >> meta-gnome/README | 10 +++++-----
> >> meta-initramfs/README | 8 ++++----
> >> meta-multimedia/README | 10 +++++-----
> >> meta-networking/MAINTAINERS | 32 +++-----------------------------
> >> meta-networking/README | 6 +++---
> >> meta-oe/README | 8 ++++----
> >> meta-perl/README | 10 ++++------
> >> meta-python/README | 12 +++++-------
> >> meta-webserver/README | 8 ++++----
> >> meta-xfce/README | 10 +++++-----
> >> 12 files changed, 49 insertions(+), 79 deletions(-)
> >>
> >> diff --git a/README b/README
> >> index 7318f09..881115e 100644
> >> --- a/README
> >> +++ b/README
> >> @@ -1,6 +1,6 @@
> >> Collection of layers for the OE-core universe
> >>
> >> -Main layer maintainer: Khem Raj <raj.khem@gmail.com>
> >> +Warrior maintainer: Armin Kuster <akuster808@gmail.com>
> >>
> >> This repository is a collection of layers to suppliment OE-Core
> >> with additional packages, Each layer have designated maintainer
> >> diff --git a/meta-filesystems/README b/meta-filesystems/README
> >> index 87cb685..842da13 100644
> >> --- a/meta-filesystems/README
> >> +++ b/meta-filesystems/README
> >> @@ -10,30 +10,30 @@ Dependencies
> >> This layer depends on:
> >>
> >> URI: git://git.openembedded.org/bitbake
> >> - branch: master
> >> + branch: 1.42
> > To be clear, where is 1.42 coming from?
> > $ git checkout warrior
> > Switched to branch 'warrior'
> > Your branch is up-to-date with 'origin/warrior'.
> > $ git grep BB_MIN_VER
> > meta/classes/sanity.bbclass: minversion = d.getVar('BB_MIN_VERSION')
> > meta/conf/sanity.conf:BB_MIN_VERSION = "1.39.1"
> How is this a problem of meta-openembedded?
> its a core and bitbake issue.
>
> http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?h=warrior&id=0c3423aae935c36e59d15d8bb60d7826cebc4e03
> https://git.openembedded.org/bitbake/log/?h=1.42
Yes, correct. Sorry for hijacking the thread, I just saw this patch
which reminded me to follow up about that core issue.
> > To be clear, I'm _not_ a fan of saying we need to go that old
> > (especially since there's no CI done with that version) but I am saying
> > we should be consistent with the code.
>
> You are helping make a case for removing the reference to what bitbake
> version meta-filesystems want as its the only layer that identified it
> needed bitbake.
>
> The other layers in meta-openembedded don't list it.
>
> I will send v3 to remove any reference to bitbake.
That makes the most sense, agreed. No layer should be saying what
bitbake version is requires, that should be handled by the core layer.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2019-05-01 16:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-01 15:41 [warrior][v2][PATCH] README: updated Maintainers list for Warrior Armin Kuster
2019-05-01 16:00 ` Tom Rini
2019-05-01 16:24 ` akuster808
2019-05-01 16:29 ` Tom Rini [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=20190501162953.GC31207@bill-the-cat \
--to=trini@konsulko.com \
--cc=akuster808@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 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.