Github messages for voidlinux
 help / color / mirror / Atom feed
From: zlice <zlice@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] meson: update to 1.3.1
Date: Thu, 11 Jan 2024 18:28:09 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48171@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 710 bytes --]

There is a new pull request by zlice against master on the void-packages repository

https://github.com/zlice/void-packages meson-1.3.1
https://github.com/void-linux/void-packages/pull/48171

meson: update to 1.3.1
<!-- Uncomment relevant sections and delete options which are not applicable -->

#### Testing the changes
- I tested the changes in this PR: **YES**

#### Local build testing
- I built this PR locally for my native architecture, **x86_64**, **i686**

#### Comments

need this and [libdrm-2.4.119](https://github.com/void-linux/void-packages/pull/48170) for mesa-24 soonish

@SpidFightFR fyi

A patch file from https://github.com/void-linux/void-packages/pull/48171.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-meson-1.3.1-48171.patch --]
[-- Type: text/x-diff, Size: 1149 bytes --]

From 76ea99608855c7b81661541df7387c71f27b73b0 Mon Sep 17 00:00:00 2001
From: zlice <zlice555@gmail.com>
Date: Thu, 11 Jan 2024 12:23:48 -0500
Subject: [PATCH] meson: update to 1.3.1

---
 srcpkgs/meson/template | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/srcpkgs/meson/template b/srcpkgs/meson/template
index e76e584049538..e34a283355d8a 100644
--- a/srcpkgs/meson/template
+++ b/srcpkgs/meson/template
@@ -1,6 +1,6 @@
 # Template file for 'meson'
 pkgname=meson
-version=1.3.0
+version=1.3.1
 revision=1
 build_style=python3-module
 hostmakedepends="python3-devel python3-setuptools"
@@ -14,7 +14,7 @@ license="Apache-2.0"
 homepage="https://mesonbuild.com"
 changelog="https://raw.githubusercontent.com/mesonbuild/meson/master/docs/markdown/Release-notes-for-${version%.*}.0.md"
 distfiles="https://github.com/mesonbuild/meson/releases/download/${version}/meson-${version}.tar.gz"
-checksum=4ba253ef60e454e23234696119cbafa082a0aead0bd3bbf6991295054795f5dc
+checksum=6020568bdede1643d4fb41e28215be38eff5d52da28ac7d125457c59e0032ad7
 
 # XXX: sanitizers aren't available on musl
 if [ "$XBPS_TARGET_LIBC" = glibc ]; then

             reply	other threads:[~2024-01-11 17:28 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-11 17:28 zlice [this message]
2024-01-11 17:29 ` classabbyamp
2024-01-11 17:29 ` classabbyamp
2024-01-11 17:31 ` zlice
2024-01-11 17:33 ` zlice
2024-01-11 17:33 ` SpidFightFR
2024-01-11 17:56 ` classabbyamp
2024-01-11 18:35 ` zlice
2024-01-11 18:45 ` classabbyamp
2024-01-11 18:51 ` SpidFightFR
2024-01-13 14:13 ` zlice
2024-01-13 14:18 ` zlice
2024-01-13 14:18 ` zlice
2024-01-13 21:43 ` chrysos349
2024-01-17  1:00 ` [PR PATCH] [Merged]: " classabbyamp

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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48171@inbox.vuxu.org \
    --to=zlice@users.noreply.github.com \
    --cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).