From: "Michael Opdenacker" <michael.opdenacker@bootlin.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 #poky
Date: Fri, 17 Feb 2023 15:21:13 +0100 [thread overview]
Message-ID: <4d70f231-afe0-fb28-4d49-ea5192b120e6@bootlin.com> (raw)
In-Reply-To: <Groupsio.1.Ns4R.1676632334791492919.c94a@lists.yoctoproject.org>
Hello Kamel
On 17.02.23 at 12:12, Kamel Fezzani wrote:
>
> [Edited Message Follows]
>
> 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.
> I've seen that dunfell LTS release is not tested on UBUNTU LTS 22.04
> (https://git.yoctoproject.org/poky/tree/meta-poky/conf/distro/poky.conf?h=dunfell#n49
> <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 ?
I guess that the main reason is that Ubuntu 22.04 wasn't released when
Dunfell 3.1 was initially published. Supporting a new version of the
host distro requires running (and passing) extra tests.
I also have a question about our autobuilders... On
https://autobuilder.yoctoproject.org/, how to see the Dunfell builds (if
any)?
Back to your question... Why would you want to stick to Dunfell 3.1, but
not to Ubuntu 20.04? Ubuntu 20.04 will still be supported when Dunfell
reaches its end of life (April 2024).
Cheers
Michael.
--
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2023-02-17 14:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-17 11:12 [poky] Test dunfell LTS release on UBUNTU LTS 22.04 #yocto #poky Kamel Fezzani
[not found] ` <Groupsio.1.Ns4R.1676632334791492919.c94a@lists.yoctoproject.org>
2023-02-17 14:21 ` Michael Opdenacker [this message]
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=4d70f231-afe0-fb28-4d49-ea5192b120e6@bootlin.com \
--to=michael.opdenacker@bootlin.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).