From: "Alexander Kanavin" <alex.kanavin@gmail.com>
To: Kamel Fezzani <kamfezz@gmail.com>
Cc: poky@lists.yoctoproject.org
Subject: Re: [poky] Test dunfell LTS release on UBUNTU LTS 22.04 #yocto
Date: Fri, 17 Feb 2023 13:23:48 +0100 [thread overview]
Message-ID: <CANNYZj8DU7twqWsXKq3F95efV80i3jQHRF1bBnNk8kZR_xR+pA@mail.gmail.com> (raw)
In-Reply-To: <BooD.1676632109346078064.HPtY@lists.yoctoproject.org>
The list of distributions is simply what the yocto CI is using to run
test builds. It doesn't mean that 22.04 will not work, but you may run
into issues, mostly caused by newer ubuntu compiler building an older
set of native recipes in dunfell. If you have compelling reasons to
move to 22.04, you can also install buildtools tarball which will
insulate you from the host tools: scripts/install-buildtools
Alex
On Fri, 17 Feb 2023 at 12:08, Kamel Fezzani <kamfezz@gmail.com> wrote:
>
> Hello,
>
> On one of my Yocto projects, I am using dunfell LTS release, and I'm tracking latest dunfell releases (3.1.22 (January 2023)).
> I am using build machines with native UBUNTU distribution.
>
> Ive seen that dunfell LTS release si not tested on UBUNTU LTS 22.04 (https://git.yoctoproject.org/poky/tree/meta-poky/conf/distro/poky.conf?h=dunfell#n49).
>
> Si there any reason for that ? This test is planned ?
> Or should I keep my build machine on UBUNTU20.04 ?
>
> Thanks for help.
> Regards.
> Kamel FAZZANI.
>
>
>
next parent reply other threads:[~2023-02-17 12:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BooD.1676632109346078064.HPtY@lists.yoctoproject.org>
2023-02-17 12:23 ` Alexander Kanavin [this message]
2023-02-17 14:21 ` [poky] Test dunfell LTS release on UBUNTU LTS 22.04 #yocto Steve Sakoman
2023-02-17 14:24 ` Martin Jansa
2023-02-17 14:33 ` Michael Opdenacker
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=CANNYZj8DU7twqWsXKq3F95efV80i3jQHRF1bBnNk8kZR_xR+pA@mail.gmail.com \
--to=alex.kanavin@gmail.com \
--cc=kamfezz@gmail.com \
--cc=poky@lists.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).