From: "Antonin Godard" <antonin.godard@bootlin.com>
To: <paulg@kernel.org>, <docs@lists.yoctoproject.org>
Subject: Re: [docs] [PATCH] requirements: move Ubuntu-20.04 into unsupported category due to python
Date: Mon, 24 Mar 2025 09:11:23 +0100 [thread overview]
Message-ID: <D8OCEZ6BIJBN.36VNEE4M3EGL5@bootlin.com> (raw)
In-Reply-To: <20250321192711.3061486-1-paulg@kernel.org>
Hi,
On Fri Mar 21, 2025 at 8:27 PM CET, Paul Gortmaker via lists.yoctoproject.org wrote:
> From: Paul Gortmaker <paul.gortmaker@kernel.org>
>
> Bitbake commit 0d2e682d00df ("bitbake: lib/bb: Bump minimum python
> version requirement to 3.9" -- poky commit 67566c7410e1) means that
> Ubuntu 20.04 is no longer supported out-of-the-box as detailed further
> in the respective commit log.
>
> While it is true that it can still be used with buildtools, that can
> also be said for nearly every other unsupported distro out there,
> including Ubuntu 18.04 that we listed as unsupported some years ago.
> Hence continuing to list it as supported with the new python requirement
> in place does not make sense.
>
> So we move it alongside of the 18.04 entry, into the "possibly tested,
> but you get what you get" category. And add an explicit mention of the
> buildtools, so people have a thread to pull on.
>
> Signed-off-by: Paul Gortmaker <paulg@kernel.org>
>
> diff --git a/documentation/ref-manual/system-requirements.rst b/documentation/ref-manual/system-requirements.rst
> index 93b95a7fb251..3d0d26e2f08b 100644
> --- a/documentation/ref-manual/system-requirements.rst
> +++ b/documentation/ref-manual/system-requirements.rst
> @@ -58,8 +58,6 @@ Supported Linux Distributions
> Currently, the &DISTRO; release ("&DISTRO_NAME;") of the Yocto Project is
> supported on the following distributions:
>
> -- Ubuntu 20.04 (LTS)
> -
> - Ubuntu 22.04 (LTS)
>
> - Ubuntu 24.04 (LTS)
> @@ -93,11 +91,15 @@ organizations publishing them no longer make updates publicly available:
>
> - Ubuntu 18.04 (LTS)
>
> +- Ubuntu 20.04 (LTS)
> +
> - Ubuntu 23.04
>
> Note that the Yocto Project doesn't have access to private updates
> that some of these versions may have. Therefore, our testing has
> -limited value if you have access to such updates.
> +limited value if you have access to such updates. Also, buildtools
s/buildtools/:term:`buildtools`/, so users are hinted towards what this is.
I can make that change before merging if that's ok to you.
Antonin
--
Antonin Godard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2025-03-24 8:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-21 19:27 [PATCH] requirements: move Ubuntu-20.04 into unsupported category due to python paulg
2025-03-24 8:11 ` Antonin Godard [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=D8OCEZ6BIJBN.36VNEE4M3EGL5@bootlin.com \
--to=antonin.godard@bootlin.com \
--cc=docs@lists.yoctoproject.org \
--cc=paulg@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.