From: "Yoann Congal" <yoann.congal@smile.fr>
To: <navinreddy23@gmail.com>, <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] How to backport latest go version?
Date: Thu, 19 Feb 2026 16:49:48 +0100 [thread overview]
Message-ID: <DGJ22TW6NQ7J.26KZXIRN87D9B@smile.fr> (raw)
In-Reply-To: <nOYT.1771515503207887946.99kd@lists.openembedded.org>
On Thu Feb 19, 2026 at 4:38 PM CET, navinreddy23 via lists.openembedded.org wrote:
> Hello all,
>
> I am currently using scarthgap branch and was not able to successfully backport latest go version 1.26.0.
> I have created a custom layer (meta-dummy) and added all the files from recipes-devtools/go of Whinlatter branch. Yet, when I invoke bitbake recipe-name, I get the old version which is present as
>
> ❯ tmp/sysroots-components/x86_64/go-cross-armv8a/usr/lib/aarch64-tdx-linux/go/bin/go version
> go version go1.22.12 linux/amd64
>
> I am able to set the preferred version in local.conf and it builds fine and I am able toverify the binary version for the host.
> PREFERRED_VERSION_go="1.26.0"
> PREFERRED_VERSION_go-native="1.26.0"
> PREFERRED_VERSION_go-cross="1.26.0"
>
> Am I missing something here? Is it the right way to backport?
The usual solution is to use the mixin-layer for scarthgap/go:
https://git.yoctoproject.org/meta-lts-mixins/log/?h=scarthgap/go
See the note in https://docs.yoctoproject.org/dev/ref-manual/release-process.html#long-term-support-releases
Regards,
--
Yoann Congal
Smile ECS
next prev parent reply other threads:[~2026-02-19 15:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-19 15:38 How to backport latest go version? navinreddy23
2026-02-19 15:49 ` Yoann Congal [this message]
[not found] ` <48326.1771577023423291484@lists.openembedded.org>
2026-02-20 9:00 ` Private: Re: [OE-core] " Yoann Congal
[not found] ` <CACNOY6JqR97WvxzCxPcp_BMrcB3xr-MKUHGyDuH0OWcF3L=gzg@mail.gmail.com>
[not found] ` <DGJOKQ7XZ0AN.1UKSUPQOVW00S@smile.fr>
2026-02-20 14:15 ` Navin R
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=DGJ22TW6NQ7J.26KZXIRN87D9B@smile.fr \
--to=yoann.congal@smile.fr \
--cc=navinreddy23@gmail.com \
--cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox