From: Mark Hatle <mark.hatle@kernel.crashing.org>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: Yocto Project <yocto@yoctoproject.org>
Subject: Re: [layerindex-web] Enabled zeus, not working...
Date: Mon, 14 Oct 2019 17:54:47 -0500 [thread overview]
Message-ID: <e247be4b-7c6e-83db-e202-edd5ef5a0948@kernel.crashing.org> (raw)
In-Reply-To: <1678166.3Pd2BCF48v@linux.fritz.box>
On 10/14/19 5:08 PM, Paul Eggleton wrote:
> Hi Mark
>
> On Tuesday, 15 October 2019 10:21:29 AM NZDT Mark Hatle wrote:
>> I added the zeus branch on the layers.openembedded.org today and it's not
>> showing up and being indexed. Any idea why?
>
> The bitbake branch wasn't correctly specified - it needed to be set to "1.44"
> (grabbed from https://wiki.yoctoproject.org/wiki/Releases if you don't have it
> in your head - I didn't ;).
>
Great so it's my fault.. much easier to fix then an infrastructure issue.
>> On my own personal layer index I did it and it worked fine. So it may be
>> something related to the configuration.
>
> I guess it worked in your case because (based on your patch of the other day)
> you're picking bitbake out of a repo where zeus is a valid branch.
Yup, exactly.. it -happened- to work.. :)
> FYI on layers.openembedded.org you also need to select the Python environment
> for the branch - python3 in this case.
>
> I've made both of these changes so it should index correctly the next time
> around.
Ahh I thought python3 was now the default, and python2 was for the older
systems. I read it backwards.. I'll try to remember in 6 months. :)
(Part of the reason I included the mailing list here.)
--Mark
> Cheers
> Paul
>
>
prev parent reply other threads:[~2019-10-14 22:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-14 21:21 [layerindex-web] Enabled zeus, not working Mark Hatle
2019-10-14 22:08 ` Paul Eggleton
2019-10-14 22:54 ` Mark Hatle [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=e247be4b-7c6e-83db-e202-edd5ef5a0948@kernel.crashing.org \
--to=mark.hatle@kernel.crashing.org \
--cc=paul.eggleton@linux.intel.com \
--cc=yocto@yoctoproject.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.