DPDK patches and discussions
 help / color / mirror / Atom feed
From: Kevin Traynor <ktraynor@redhat.com>
To: David Marchand <david.marchand@redhat.com>,
	Bruce Richardson <bruce.richardson@intel.com>
Cc: Luca Boccassi <bluca@debian.org>, dev <dev@dpdk.org>,
	Aaron Conole <aconole@redhat.com>,
	Michael Santana <maicolgabriel@hotmail.com>,
	Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [dpdk-dev] [PATCH] ci: pin meson to 0.52.0
Date: Wed, 8 Jan 2020 15:56:49 +0000	[thread overview]
Message-ID: <5ead276e-cd0b-1230-7008-efad09da9447@redhat.com> (raw)
In-Reply-To: <CAJFAV8zEGJXWSC9wSE0+4ub8Bu=r_TxKf-qU8vSvDCWR=nGr0Q@mail.gmail.com>

On 08/01/2020 14:22, David Marchand wrote:
> On Wed, Jan 8, 2020 at 1:10 PM Bruce Richardson
> <bruce.richardson@intel.com> wrote:
>>
>> On Wed, Jan 08, 2020 at 12:59:35PM +0100, David Marchand wrote:
>>> On Wed, Jan 8, 2020 at 12:29 PM Luca Boccassi <bluca@debian.org> wrote:
>>>>
>>>> On Wed, 2020-01-08 at 12:02 +0100, David Marchand wrote:
>>>>> meson 0.53.0 has a compatibility issue [1] with the python 3.5.2 that
>>>>> comes
>>>>> in Ubuntu 16.04.
>>>>> Let's pin meson to 0.52.0 while the fix is being prepared in meson.
>>>>>
>>>>> 1:
>>>>> https://github.com/mesonbuild/meson/issues/6427
>>>>>
>>>>>
>>>>> Signed-off-by: David Marchand <
>>>>> david.marchand@redhat.com
>>>>>>
>>>>> ---
>>>>>  .ci/linux-setup.sh | 2 +-
>>>>>  1 file changed, 1 insertion(+), 1 deletion(-)
>>>>
>>>> Acked-by: Luca Boccassi <bluca@debian.org>
>>>
>>> There is a 0.52.1 version available, so I suppose we can blacklist
>>> meson < 0.53 instead.
>>> Thought?
>>>
>>> If noone objects, I will apply a fix by the end of the day.
>>>
>> Wondering if there is value in using 0.47.1, the minimum version we
>> support, to catch potential issues with someone using features from newer
>> versions? I suspect there are more people using the latest releases of
>> meson than the baseline supported version?
> 
> Testing with a fixed version seems better in a CI, and since we
> announce this minimum version, then yes, it makes sense.
> I will post a v2.

You can add a 'cc: stable' tag (in this case no fixes needed) as it is
the same issue for the stable branches - though I will take it straight
away.

> 
> 


      parent reply	other threads:[~2020-01-08 15:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-08 11:02 David Marchand
2020-01-08 11:29 ` Luca Boccassi
2020-01-08 11:59   ` David Marchand
2020-01-08 12:10     ` Bruce Richardson
2020-01-08 14:22       ` David Marchand
2020-01-08 15:10         ` Aaron Conole
2020-01-08 15:50           ` Bruce Richardson
2020-01-08 16:09             ` Aaron Conole
2020-01-08 17:34               ` Bruce Richardson
2020-01-08 15:56         ` Kevin Traynor [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=5ead276e-cd0b-1230-7008-efad09da9447@redhat.com \
    --to=ktraynor@redhat.com \
    --cc=aconole@redhat.com \
    --cc=bluca@debian.org \
    --cc=bruce.richardson@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=maicolgabriel@hotmail.com \
    --cc=thomas@monjalon.net \
    /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).