From: David Marchand <david.marchand@redhat.com>
To: Stephen Hemminger <stephen@networkplumber.org>,
Tyler Retzlaff <roretzla@linux.microsoft.com>
Cc: Patrick Robb <probb@iol.unh.edu>,
dev@dpdk.org, bruce.richardson@intel.com, zhoumin@loongson.cn,
aconole@redhat.com, rajesh.t.puttaswamy@intel.com, ci@dpdk.org
Subject: Re: [PATCH] Increasing ci meson version to .57
Date: Wed, 9 Oct 2024 09:47:12 +0200 [thread overview]
Message-ID: <CAJFAV8xDSZUOC=aUX8VMTobR+NMAZTmhfpZ41psEQF5da27qNg@mail.gmail.com> (raw)
In-Reply-To: <20241008204311.6928528a@hermes.local>
On Wed, Oct 9, 2024 at 5:43 AM Stephen Hemminger
<stephen@networkplumber.org> wrote:
>
> On Tue, 8 Oct 2024 15:25:43 -0400
> Patrick Robb <probb@iol.unh.edu> wrote:
>
> > There is a proposed increase in the minimum meson version to .57
> > This patch aligns the linux setup ci script with this change.
> >
> > Signed-off-by: Patrick Robb <probb@iol.unh.edu>
>
> I wonder if we shouldn't push it to something later.
> Debian stable is using 1.0.1 and testing is up to 1.5.2
>
> 0.57.0 was released on Feb 14,2021
> 1.0.0 was released on Dec 23, 2022
>
> So getting a release that was more recent makes sense.
> The users stuck on enterprise distro's are going to have to resort
> to pip anyway to get a new version.
Tyler reported an issue for Windows with meson > 0.57.
https://inbox.dpdk.org/dev/ZvuoUizQiDeE62zB@bricha3-mobl1.ger.corp.intel.com/
--
David Marchand
next prev parent reply other threads:[~2024-10-09 7:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-08 19:25 Patrick Robb
2024-10-08 19:33 ` Patrick Robb
2024-10-08 20:05 ` Bruce Richardson
2024-10-08 20:11 ` Patrick Robb
2024-10-09 2:43 ` Aaron Conole
2024-10-09 3:43 ` Stephen Hemminger
2024-10-09 7:47 ` David Marchand [this message]
2024-10-09 8:10 ` Bruce Richardson
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='CAJFAV8xDSZUOC=aUX8VMTobR+NMAZTmhfpZ41psEQF5da27qNg@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=aconole@redhat.com \
--cc=bruce.richardson@intel.com \
--cc=ci@dpdk.org \
--cc=dev@dpdk.org \
--cc=probb@iol.unh.edu \
--cc=rajesh.t.puttaswamy@intel.com \
--cc=roretzla@linux.microsoft.com \
--cc=stephen@networkplumber.org \
--cc=zhoumin@loongson.cn \
/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 NNTP newsgroup(s).