Hi Alexandre,

builds do on the AB. This is how things map out:

AB master -> meta-agl next
AB langdale -> meta-agl next # our -next branch is of 'master'
AB kirkstone -> meta-agl master # our master tracks the LTS of
YP AB dunfell -> meta-agl lamprey

So thats our decoder ring.

Essentially our master will track LTS till the next LTS is out.
We do a -next to enable upstream testing in the AB for anything thats
newer
than the LTS. Now upstream 'master' makes sense as we can help fix things
right away. We could question if langdale makes sense as we would never
switch to it. Might safe the cycles.

Let me know what you think.

Well, I think this goes against the principle of least astonishment and
is quite convoluted. I don't feel this is normal that the only three
commits after introducing langdale on the autobuilders are to fix the
meat-agl branches.

Sorry to hear that that, but we did not intent to be troublemakers ;) for
sure. This is a learning curve I suppose on both sides as we do uprev's on
different timelines while we track the LTS branches.

Best,
Jan-Simon

Hello,

On 08/12/2022 01:28:54+0100, Jan-Simon Moeller wrote:

Hi Alexandre,

hmm, I think there's some confusion. Let me try to clarify:

For https://autobuilder.yoctoproject.org/typhoon/#/builders/121/builds/1049
-> Build Properties
branch (yocto) -> "langdale"
branch_meta-agl -> "master" ## that is wrong, it should be meta-agl-next

https://autobuilder.yoctoproject.org/typhoon/#/builders/121/builds/1047
-> Build Properties
branch (yocto) -> "dunfell"
branch_meta-agl -> "next" ## that is (meanwhile) no longer true

I think we just point to the wrong branches meanwhile.

We sorted that out with Steve 3 weeks ago and came up with this::

I'm guessing that means the langdale AB test builds are using meta-agl's
master branch? They should be using the "next" branch like the master
builds do on the AB. This is how things map out:

AB master -> meta-agl next
AB langdale -> meta-agl next # our -next branch is of 'master'
AB kirkstone -> meta-agl master # our master tracks the LTS of YP
AB dunfell -> meta-agl lamprey

So thats our decoder ring.

Essentially our master will track LTS till the next LTS is out.
We do a -next to enable upstream testing in the AB for anything thats newer
than the LTS. Now upstream 'master' makes sense as we can help fix things right
away. We could question if langdale makes sense as we would never switch to
it. Might safe the cycles.

Let me know what you think.

Well, I think this goes against the principle of least astonishment and
is quite convoluted. I don't feel this is normal that the only three
commits after introducing langdale on the autobuilders are to fix the
meat-agl branches.

Anyway, I've sent a patch to fix it.


--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

Hi Alexandre,

hmm, I think there's some confusion. Let me try to clarify:

For https://autobuilder.yoctoproject.org/typhoon/#/builders/121/builds/1049
-> Build Properties
branch (yocto) -> "langdale"
branch_meta-agl -> "master" ## that is wrong, it should be meta-agl-next

https://autobuilder.yoctoproject.org/typhoon/#/builders/121/builds/1047
-> Build Properties
branch (yocto) -> "dunfell"
branch_meta-agl -> "next" ## that is (meanwhile) no longer true

I think we just point to the wrong branches meanwhile.

We sorted that out with Steve 3 weeks ago and came up with this::

I'm guessing that means the langdale AB test builds are using meta-agl's
master branch? They should be using the "next" branch like the master
builds do on the AB. This is how things map out:

AB master -> meta-agl next
AB langdale -> meta-agl next # our -next branch is of 'master'
AB kirkstone -> meta-agl master # our master tracks the LTS of YP
AB dunfell -> meta-agl lamprey

So thats our decoder ring.

Essentially our master will track LTS till the next LTS is out.
We do a -next to enable upstream testing in the AB for anything thats newer
than the LTS. Now upstream 'master' makes sense as we can help fix things right
away. We could question if langdale makes sense as we would never switch to
it. Might safe the cycles.

Let me know what you think.

Best regards,
Jan-Simon

Am Mittwoch, 7. Dezember 2022, 23:53:59 CET schrieb Scott Murray:

Our next branch seems to have been rebased/pushed to an old version last
night, Jan-Simon and I will try to figure out what happened. I can push
the previous state that I have, but I want to make sure it's not going to
get clobbered again if there's something automated involved.
'
Scott


On Thu, Dec 8, 2022 at 1:47 AM Alexandre Belloni <

alexandre.belloni@...> wrote:

Hello,

meta-agl is still failing check-layer-nightly on langdale builds because
of meta-pipewire:

ERROR: Layer meta-pipewire is not compatible with the core layer which
only supports these series: langdale (layer is compatible with kirkstone)


https://autobuilder.yoctoproject.org/typhoon/#/builders/121/builds/1049/st
eps/12/logs/stdio


--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

On Thu, Dec 08, 2022 at 08:14:38AM +0900, Scott Murray wrote:

Okay, Jan-Simon is more awake than I am, and points out that our next
branch is where it should be. We do have a commit that adds langdale to
LAYERSERIES_COMPAT for all the layers in meta-agl, so we'll have to
investigate why yocto-check-layer thinks otherwise and get back to you.

As Scott points out, meta-agl uses "next" branch to track upstream master
development, i.e. langdale and later. As meta-agl "master" branch is kept
compatible with the latest LTS, namely kirkstone.

--
Denys

On Thu, Dec 8, 2022 at 7:53 AM Scott Murray <scott.murray@...>
wrote:

Our next branch seems to have been rebased/pushed to an old version last
night, Jan-Simon and I will try to figure out what happened. I can push
the previous state that I have, but I want to make sure it's not going to
get clobbered again if there's something automated involved.

Scott


On Thu, Dec 8, 2022 at 1:47 AM Alexandre Belloni <
alexandre.belloni@...> wrote:

Hello,

meta-agl is still failing check-layer-nightly on langdale builds because
of meta-pipewire:

ERROR: Layer meta-pipewire is not compatible with the core layer which
only supports these series: langdale (layer is compatible with kirkstone)


https://autobuilder.yoctoproject.org/typhoon/#/builders/121/builds/1049/steps/12/logs/stdio

Hello,

meta-agl is still failing check-layer-nightly on langdale builds because
of meta-pipewire:

ERROR: Layer meta-pipewire is not compatible with the core layer which only supports these series: langdale (layer is compatible with kirkstone)

https://autobuilder.yoctoproject.org/typhoon/#/builders/121/builds/1049/steps/12/logs/stdio


--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com