From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Alexander Kanavin <alex.kanavin@gmail.com>,
Khem Raj <raj.khem@gmail.com>
Cc: Alexander Kanavin <alex@linutronix.de>,
openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH 6/6] mesa: update 22.3.5 -> 23.0.0
Date: Mon, 20 Mar 2023 10:01:02 +0000 [thread overview]
Message-ID: <b035e00a13a04de67dea942bb202671b7c7d0393.camel@linuxfoundation.org> (raw)
In-Reply-To: <CANNYZj8w3QZ5H4L76ZD=qY3YmLYDP31nrJQWxh+BS+Ub7dc=ww@mail.gmail.com>
On Mon, 2023-03-20 at 08:09 +0100, Alexander Kanavin wrote:
> On Sat, 18 Mar 2023 at 19:38, Khem Raj <raj.khem@gmail.com> wrote:
> > Perhaps in the next cycle yes and definitely for the next LTS it
> > should be dropped.
> >
> > Its stll supported via Extended Security Maintenance (ESM) and users
> > maybe still be using it.
>
> The question is: are ubuntu 18.04 workers going to be maintained after
> 18.04 transitions to ESM next month? In all likelihood they won't be,
> as it is a commercial subscription, and then we can't continue to test
> with it.
I think the fact it can work with buildtools should mean we're ok. As
mentioned, we already need it there for python version requirements and
as mentioned, it is EOL soon anyway.
Cheers,
Richard
prev parent reply other threads:[~2023-03-20 10:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-16 9:40 [PATCH 1/6] runqemu: direct mesa to use its own drivers, rather than ones provided by host distro Alexander Kanavin
2023-03-16 9:40 ` [PATCH 2/6] mesa: allow mesa-native/nativesdk only subject to opengl/vulkan DISTRO_FEATURE Alexander Kanavin
2023-03-16 9:40 ` [PATCH 3/6] mesa: enable a rich set of drivers for native builds Alexander Kanavin
2023-03-20 17:10 ` [OE-core] " Ross Burton
2023-03-20 17:41 ` Alexander Kanavin
2024-08-02 17:52 ` Marko, Peter
2024-08-03 5:13 ` Böszörményi Zoltán
2023-03-16 9:41 ` [PATCH 4/6] llvm: allow building libllvm in native builds, subject to PACKAGECONFIG Alexander Kanavin
2023-03-20 16:20 ` [OE-core] " Ross Burton
2023-03-20 17:36 ` Alexander Kanavin
2023-03-16 9:41 ` [PATCH 5/6] mesa: do not strip rpaths from dri drivers Alexander Kanavin
2023-03-16 9:41 ` [PATCH 6/6] mesa: update 22.3.5 -> 23.0.0 Alexander Kanavin
2023-03-18 2:47 ` [OE-core] " Khem Raj
2023-03-18 8:01 ` Alexander Kanavin
2023-03-18 18:37 ` Khem Raj
2023-03-18 18:57 ` Martin Jansa
2023-03-20 7:09 ` Alexander Kanavin
2023-03-20 10:01 ` Richard Purdie [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=b035e00a13a04de67dea942bb202671b7c7d0393.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=alex.kanavin@gmail.com \
--cc=alex@linutronix.de \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
/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