From: Michael Opdenacker <michael.opdenacker@bootlin.com>
To: poky@lists.yoctoproject.org
Subject: Re: [dunfell][PATCH v2] poky.conf: update SANITY_TESTED_DISTROS to match autobuilder
Date: Thu, 21 Dec 2023 15:31:26 +0100 [thread overview]
Message-ID: <0bd0e818-e31c-4ad2-8197-2ffe9cf56941@bootlin.com> (raw)
In-Reply-To: <20231221111536.750434-1-michael.opdenacker@bootlin.com>
On 21.12.23 at 12:15, michael.opdenacker@bootlin.com wrote:
> From: Michael Opdenacker <michael.opdenacker@bootlin.com>
>
> Adding new active workers on
> https://autobuilder.yoctoproject.org/typhoon/#/workers
>
> Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
>
> ---
> Changes in V2:
> - Keep the originally tested distros when the release was first published.
> ---
> meta-poky/conf/distro/poky.conf | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/meta-poky/conf/distro/poky.conf b/meta-poky/conf/distro/poky.conf
> index 5fabf67..2b186fe 100644
> --- a/meta-poky/conf/distro/poky.conf
> +++ b/meta-poky/conf/distro/poky.conf
> @@ -47,6 +47,7 @@ SANITY_TESTED_DISTROS ?= " \
> ubuntu-20.04 \n \
> ubuntu-22.04 \n \
> fedora-37 \n \
> + fedora-38 \n \
> debian-11 \n \
> opensuseleap-15.3 \n \
> almalinux-8.8 \n \
Actually, following our discussion, SANITY_TESTED_DISTROS is still
missing many distro versions which were supported with the initial
Dunfell releases. As explained on
https://docs.yoctoproject.org/ref-manual/variables.html#term-SANITY_TESTED_DISTROS,
people will get an error message if they upgrade Dunfell without
upgrading their distro.
Shall I send a V3 including an extra commit that restores such distros?
I still have the relevant information in the documentation.
Cheers
Michael.
--
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2023-12-21 14:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-21 11:15 [dunfell][PATCH v2] poky.conf: update SANITY_TESTED_DISTROS to match autobuilder michael.opdenacker
2023-12-21 14:31 ` 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=0bd0e818-e31c-4ad2-8197-2ffe9cf56941@bootlin.com \
--to=michael.opdenacker@bootlin.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).