From: Efraim Flashner <efraim@flashner.co.il>
To: 34025@debbugs.gnu.org, leo@famulari.name, stuart.dilts@gmail.com
Subject: [bug#34025] [PATCH] Update meson to 0.49.0
Date: Thu, 10 Jan 2019 09:24:27 +0200 [thread overview]
Message-ID: <20190110072426.GD18849@macbook41> (raw)
In-Reply-To: <20190110010247.GA18759@jasmine.lan>
[-- Attachment #1: Type: text/plain, Size: 1084 bytes --]
On Wed, Jan 09, 2019 at 08:02:47PM -0500, Leo Famulari wrote:
> On Wed, Jan 09, 2019 at 03:50:58PM -0700, Stuart Dilts wrote:
> > * gnu/packages/build-tools.scm: update the version and sha256 hash
>
> Thank you for sending this patch!
>
> We actually already have this change on the 'staging' branch [0], in commit
> f06fdbae8d6318fdabf9c1eb686e2bfa2b9ff18a.
>
> Updating meson will trigger a rebuild of all the packages that use the
> meson-build-system.
>
> I'm not sure how to find out exactly how many packages directly and
> indirectly depend on the meson-build-system, but since the change was
> pushed to the staging branch, it's probably more than 300, which is the
> limit for changes on the master branch.
>
guix refresh -l -e '(@@ (gnu packages build-tools) meson-for-build)'
another one that I've triggered accidentally is libva
--
Efraim Flashner <efraim@flashner.co.il> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-01-10 7:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-09 22:50 [bug#34025] [PATCH] Update meson to 0.49.0 Stuart Dilts
2019-01-10 1:02 ` bug#34025: " Leo Famulari
2019-01-10 7:24 ` Efraim Flashner [this message]
2019-01-10 20:22 ` [bug#34025] " Leo Famulari
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=20190110072426.GD18849@macbook41 \
--to=efraim@flashner.co.il \
--cc=34025@debbugs.gnu.org \
--cc=leo@famulari.name \
--cc=stuart.dilts@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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
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.