From: Khem Raj <raj.khem@gmail.com>
To: samuli.piippo@gmail.com, martin.jansa@gmail.com
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>,
Samuli Piippo <samuli.piippo@qt.io>,
Tim Orling <ticotimo@gmail.com>,
Ross Burton <ross.burton@arm.com>
Subject: Re: [OE-core] meta-qt6 on layerindex
Date: Wed, 2 Apr 2025 17:37:44 -0700 [thread overview]
Message-ID: <78779584-17f7-484f-b4d5-b41cb37c777d@gmail.com> (raw)
In-Reply-To: <CABXoSoVs_O7At3c+=nM6w=fwgULniKACzu_8AwhZR9iat59UYQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3744 bytes --]
On 4/2/25 12:37 AM, Samuli Piippo via lists.openembedded.org wrote:
> It would be great if I were able to, as the layer maintainer, add the
> needed branch mappings to the layerindex.
> So far, Tim has been the one to update those.
>
> scarthgap -> 6.8
> styhead -> 6.9
>
> If Tim or other admin could add these branch mappings, that would be
> great.
> The mapping can be added from admin view: Layer branches › Add layer
> branch
> AFAIK, only Branch and Actual Branch values need to be set up.
> Once there is a layer branch set up, it appears, I also have access
> rights to modify it.
What do the mappings look like, in any release there are multiple QT
releases that are supported. LTS releases might make less combinations
to map, how do these maps look when these branches become old but yocto
release branch it is pointing to is LTS. There are many permutations and
combinations.
>
> -samuli
>
>
>
> On Tue, 1 Apr 2025 at 13:07, Martin Jansa via lists.openembedded.org
> <http://lists.openembedded.org>
> <martin.jansa=gmail.com@lists.openembedded.org> wrote:
>
> Hi,
>
> some layers on layerindex cannot be correctly parsed because they
> depend on meta-qt6 (qt6-layer) and there is no record of scarthgap or
> styhead compatible release of meta-qt6 on layerindex.
>
> There are:
> https://layers.openembedded.org/layerindex/branch/kirkstone/layer/meta-qt6/
> - actual branch 6.5
> https://layers.openembedded.org/layerindex/branch/master/layer/meta-qt6/
> - actual branch dev
>
> but no
> https://layers.openembedded.org/layerindex/branch/styhead/layer/meta-qt6/
> https://layers.openembedded.org/layerindex/branch/scarthgap/layer/meta-qt6/
>
> which causes e.g.:
>
> ERROR: Issues found on branch styhead:
> meta-luneos: Failed to add since LAYERDEPENDS [meta-luneui ...] is
> not satisfied
> meta-luneui: Failed to add since LAYERDEPENDS [qt6-layer ...] is
> not satisfied
> ERROR: Issues found on branch scarthgap:
> meta-luneos: Failed to add since LAYERDEPENDS [meta-luneui ...] is
> not satisfied
> meta-luneui: Failed to add since LAYERDEPENDS [qt6-layer ...] is
> not satisfied
>
> and there will be more once meta-webosose parsing is fixed.
>
> Is Tim the only person who can help with some admin changes on
> layerindex? RP suggested to ask Ross as well.
>
> I have admin rights to publish new layers (and edit all existing
> layers), but cannot delete wrongly created ones (or their mapping) and
> I'm not sure how to add a new mapping (e.g. add scarthgap and styhead
> release for meta-qt6 by using actual branch 'dev' or '6.8').
>
> meta-qt6 dev, 6.9 and 6.8 branches have:
> LAYERSERIES_COMPAT_qt6-layer = "kirkstone langdale mickledore nanbield
> scarthgap styhead walnascar"
> 6.7 doesn't have walnascar
> 6.6 and 6.5 (currently used for kirkstone) have:
> LAYERSERIES_COMPAT_qt6-layer = "dunfell gatesgarth hardknott honister
> kirkstone langdale mickledore nanbield scarthgap"
>
> maybe even
> https://layers.openembedded.org/layerindex/branch/kirkstone/layer/meta-qt6/
> which is currently using actual branch 6.5 should be bumped to 6.8 as
> well.
>
> Cheers,
>
>
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#214227):https://lists.openembedded.org/g/openembedded-core/message/214227
> Mute This Topic:https://lists.openembedded.org/mt/112022134/1997914
> Group Owner:openembedded-core+owner@lists.openembedded.org
> Unsubscribe:https://lists.openembedded.org/g/openembedded-core/unsub [raj.khem@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
--
-Khem
[-- Attachment #2: Type: text/html, Size: 7830 bytes --]
next prev parent reply other threads:[~2025-04-03 0:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-01 10:07 meta-qt6 on layerindex Martin Jansa
2025-04-02 7:37 ` [OE-core] " Samuli Piippo
2025-04-03 0:37 ` Khem Raj [this message]
2025-04-03 6:38 ` Samuli Piippo
2025-04-15 12:41 ` Ross Burton
2025-04-15 19:22 ` Martin Jansa
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=78779584-17f7-484f-b4d5-b41cb37c777d@gmail.com \
--to=raj.khem@gmail.com \
--cc=martin.jansa@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@arm.com \
--cc=samuli.piippo@gmail.com \
--cc=samuli.piippo@qt.io \
--cc=ticotimo@gmail.com \
/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