From: SpidFightFR <SpidFightFR@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] mesa: update to version 23.3.6.
Date: Fri, 16 Feb 2024 14:21:24 +0100 [thread overview]
Message-ID: <20240216132124.E585E212FB@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48767@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 678 bytes --]
There is an updated pull request by SpidFightFR against master on the void-packages repository
https://github.com/SpidFightFR/void-packages update-mesa
https://github.com/void-linux/void-packages/pull/48767
mesa: update to version 23.3.6.
<!-- 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, (x64-GlibC)
Last bugfix release for mesa 23 branch. From now on, the next releases will go to mesa 24.
A patch file from https://github.com/void-linux/void-packages/pull/48767.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-update-mesa-48767.patch --]
[-- Type: text/x-diff, Size: 1003 bytes --]
From 6ff00b95c0fdefafefdb4c673b72255a358f2ecc Mon Sep 17 00:00:00 2001
From: SpidFightFR <spidfight@swisscows.email>
Date: Fri, 16 Feb 2024 13:39:47 +0100
Subject: [PATCH] mesa: update to version 23.3.6.
---
srcpkgs/mesa/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/mesa/template b/srcpkgs/mesa/template
index 8613d434f71b2..66b6b6b13c77c 100644
--- a/srcpkgs/mesa/template
+++ b/srcpkgs/mesa/template
@@ -1,6 +1,6 @@
# Template file for 'mesa'
pkgname=mesa
-version=23.3.5
+version=23.3.6
revision=3
build_style=meson
_llvmver=17
@@ -24,7 +24,7 @@ license="MIT, LGPL-2.1-or-later"
homepage="https://www.mesa3d.org/"
changelog="https://docs.mesa3d.org/relnotes.html"
distfiles="https://mesa.freedesktop.org/archive/mesa-${version}.tar.xz"
-checksum=69ccb1278641ff5bad71ca0f866188aeb1a92aadc4dbb9d35f50aebec5b8b50f
+checksum=cd3d6c60121dea73abbae99d399dc2facaecde1a8c6bd647e6d85410ff4b577b
build_options="wayland"
build_options_default="wayland"
next prev parent reply other threads:[~2024-02-16 13:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-16 13:15 [PR PATCH] " SpidFightFR
2024-02-16 13:21 ` SpidFightFR [this message]
2024-02-16 13:23 ` [PR PATCH] [Updated] " SpidFightFR
2024-02-28 20:23 ` SpidFightFR
2024-02-28 20:23 ` [PR PATCH] [Closed]: " SpidFightFR
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=20240216132124.E585E212FB@inbox.vuxu.org \
--to=spidfightfr@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).