meta-qt6 on layerindex

meta-qt6 on layerindex

[Martin Jansa]

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,

Re: [OE-core] meta-qt6 on layerindex

[Samuli Piippo]

[-- Attachment #1: Type: text/plain, Size: 3201 bytes --]

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.

-samuli



On Tue, 1 Apr 2025 at 13:07, Martin Jansa via 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 (#214012):
> https://lists.openembedded.org/g/openembedded-core/message/214012
> Mute This Topic: https://lists.openembedded.org/mt/112022134/3617605
> Group Owner: openembedded-core+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [
> samuli.piippo@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
>

[-- Attachment #2: Type: text/html, Size: 4986 bytes --]

Re: [OE-core] meta-qt6 on layerindex

[Khem Raj]

[-- 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 --]

Re: [OE-core] meta-qt6 on layerindex

[Samuli Piippo]

[-- Attachment #1: Type: text/plain, Size: 4253 bytes --]

Layerindex provides only 1:1 mapping. There is no consideration for
branches that support multiple Yocto releases via LAYERSERIES_COMPAT or
otherwise.
The aim with meta-qt6 should be to map LTS releases together.
kirkstone -> Qt 6.5 is already in place, scarthgap -> Qt 6.8 should be
added.
Qt is changing the release cycle of LTS releases to one every two years,
which then matches Yocto release cycle, assuming Wrynose 6.0 is going to be
LTS.

-samuli

On Thu, 3 Apr 2025 at 03:37, Khem Raj <raj.khem@gmail.com> wrote:

>
> 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
> <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: 7971 bytes --]

Re: [OE-core] meta-qt6 on layerindex

[Ross Burton]

On 2 Apr 2025, at 08:37, Samuli Piippo <samuli.piippo@gmail.com> 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.

I’ve just added scarthgap and styhead branches for meta-qt6.  Sorry for the delay in this!

Ross

Re: [OE-core] meta-qt6 on layerindex

[Martin Jansa]

On Tue, Apr 15, 2025 at 2:42 PM Ross Burton <Ross.Burton@arm.com> wrote:
>
> On 2 Apr 2025, at 08:37, Samuli Piippo <samuli.piippo@gmail.com> 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.
>
> I’ve just added scarthgap and styhead branches for meta-qt6.  Sorry for the delay in this!

Thank you!

now when luneos and webosose layers are getting parsed I'll work on
some issues it detected, sending one fix for buildcfg shortly.

If there is someone with permission to delete the invalid layer-branch
mappings, then please delete the backports layers from:
https://layers.openembedded.org/layerindex/updates/42834/

ERROR: Subdirectory for layer meta-luneos-backports-4.3 does not exist
on branch master - if this is legitimate, the layer branch record
should be deleted
ERROR: Failed to get last revision for layer meta-luneos-backports-4.3
on branch master
ERROR: Subdirectory for layer meta-webos-backports-4.2 does not exist
on branch master - if this is legitimate, the layer branch record
should be deleted
ERROR: Subdirectory for layer meta-webos-backports-4.3 does not exist
on branch master - if this is legitimate, the layer branch record
should be deleted
ERROR: Subdirectory for layer meta-luneos-backports-5.1 does not exist
on branch master - if this is legitimate, the layer branch record
should be deleted
ERROR: Failed to get last revision for layer meta-luneos-backports-5.1
on branch master
ERROR: Subdirectory for layer meta-webos-backports-5.0 does not exist
on branch master - if this is legitimate, the layer branch record
should be deleted
ERROR: Subdirectory for layer meta-luneos-backports-5.1 does not exist
on branch kirkstone - if this is legitimate, the layer branch record
should be deleted
ERROR: Failed to get last revision for layer meta-luneos-backports-5.1
on branch kirkstone

These combinations of release/branch are indeed invalid and should be
deleted, but I don't have a permission to do so.
e.g. meta-luneos-backports-5.1 only makes sense for scarthgap and
older, shouldn't be in styhead or master release
I guess it exists in master release, because about a years ago the
layer was introduced in master branch, but later removed once we
upgraded to styhead.

Similarly with meta-webos-backports-{4.2,4.3,4,5.0} which were used
when master branch was used for kirkstone release, but were removed
when master moved to scarthgap.

I've asked meta-satobox maintainer in:
https://github.com/embetrix/meta-satobox/commit/a15d062f1e8e223290f738062c7453807f67aa27
to edit his layer to add integrity dependency, hopefully to fix:

ERROR: Issues found on branch master:
    meta-satobox: Failed to add since LAYERDEPENDS [integrity ...] is
not satisfied
ERROR: Issues found on branch scarthgap:
    meta-satobox: Failed to add since LAYERDEPENDS [integrity ...] is
not satisfied

And I've added scarthgap-rust-mixin dependency for scarthgap release
of meta-chromium to fix:
ERROR: Issues found on branch scarthgap:
    meta-chromium: Failed to add since LAYERDEPENDS
[scarthgap-rust-mixin ...] is not satisfied

I didn't fix meta-chromium for kirkstone, because lts-ruts-mixin
doesn't seem to be on layerindex at all:
ERROR: Issues found on branch kirkstone:
    meta-chromium: Failed to add since LAYERDEPENDS [lts-rust-mixin
...] is not satisfied
    meta-zenoh: Failed to add since LAYERDEPENDS [rust-layer ...] is
not satisfied

Cheers,