From: Mike Gilbert <floppym@gentoo.org>
To: Gentoo Dev <gentoo-dev@lists.gentoo.org>
Cc: William Hubbs <williamh@gentoo.org>, zmedico@gentoo.org
Subject: Re: [gentoo-dev] [PATCH] meson.eclass: require at least meson-0.41.1
Date: Mon, 23 Jul 2018 10:56:58 -0400 [thread overview]
Message-ID: <CAJ0EP43uoor_XaYGytLjGjgn0dPd3CzLCCpDP30cOKeoiSibQQ@mail.gmail.com> (raw)
In-Reply-To: <20180723032730.2405-1-zmedico@gentoo.org>
On Sun, Jul 22, 2018 at 11:27 PM Zac Medico <zmedico@gentoo.org> wrote:
>
> Require newer meson in order to avoid build failures triggered
> if >=meson-0.41.1 is not installed soon enough. For example,
> I experienced bug 649264 because I upgraded xorg-proto and
> libxshmfence packages before meson.
>
> Fixes: https://bugs.gentoo.org/649264
I suggest jumping to 0.45.1 (latest stable on all archs). Feel free to
push that.
next prev parent reply other threads:[~2018-07-23 14:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-23 3:27 [gentoo-dev] [PATCH] meson.eclass: require at least meson-0.41.1 Zac Medico
2018-07-23 8:08 ` Mart Raudsepp
2018-07-23 8:25 ` Zac Medico
2018-07-23 14:56 ` Mike Gilbert [this message]
2018-07-23 20:29 ` Zac Medico
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=CAJ0EP43uoor_XaYGytLjGjgn0dPd3CzLCCpDP30cOKeoiSibQQ@mail.gmail.com \
--to=floppym@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=williamh@gentoo.org \
--cc=zmedico@gentoo.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