From: SpidFightFR <SpidFightFR@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] mesa: update to version 23.1.9.
Date: Mon, 16 Oct 2023 19:34:58 +0200 [thread overview]
Message-ID: <20231016173458.PRezKlu_CeExWGKoSBhBn5cTN6MCJNStZGW_F4fc-8s@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46172@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 668 bytes --]
There is an updated pull request by SpidFightFR against master on the void-packages repository
https://github.com/SpidFightFR/void-packages update-mesa-23.1.8
https://github.com/void-linux/void-packages/pull/46172
mesa: update to version 23.1.9.
#### Testing the changes
- I tested the changes in this PR: **briefly**
#### Local build testing
- I built this PR locally for my native architecture, (x64-GlibC)
Hey lads, this time again for a PR, with the 23.1.8 version.
I'll be testing this PR in a moment on my laptop, as issues happened in the past 2 PRs.
A patch file from https://github.com/void-linux/void-packages/pull/46172.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-update-mesa-23.1.8-46172.patch --]
[-- Type: text/x-diff, Size: 1618 bytes --]
From 10b665bbdff9d8eeedeb92f0673a9ce153da7e3e Mon Sep 17 00:00:00 2001
From: SpidFightFR <spidfight.one@gmail.com>
Date: Mon, 16 Oct 2023 17:19:26 +0000
Subject: [PATCH] mesa: update to version 23.2.1.
---
srcpkgs/mesa/template | 8 +++-----
1 file changed, 3 insertions(+), 5 deletions(-)
diff --git a/srcpkgs/mesa/template b/srcpkgs/mesa/template
index df788fe3b0f00..165f19466380f 100644
--- a/srcpkgs/mesa/template
+++ b/srcpkgs/mesa/template
@@ -1,6 +1,6 @@
# Template file for 'mesa'
pkgname=mesa
-version=23.1.3
+version=23.2.1
revision=1
build_style=meson
#Disable LTO flag should be present, see https://gitlab.freedesktop.org/mesa/mesa/-/issues/6911
@@ -23,7 +23,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=2f6d7381bc10fbd2d6263ad1022785b8b511046c1a904162f8f7da18eea8aed9
+checksum=64de0616fc2d801f929ab1ac2a4f16b3e2783c4309a724c8a259b20df8bbc1cc
build_options="wayland"
build_options_default="wayland"
@@ -185,11 +185,9 @@ esac
post_configure() {
if [ "$CROSS_BUILD" ]; then
find -iname "*.ninja" -exec sed -i "{}" \
+ -e "s;/usr/bin/meson --internal regenerate.*;/usr/bin/touch ${wrksrc}/build/build.ninja;g" \
-e "/rustc/s; --sysroot ${XBPS_CROSS_BASE}/usr;;g" \
-e "s; /usr/lib/; ${XBPS_CROSS_BASE}/usr/lib/;g" \
- -e "s;-L/usr/lib;-L${XBPS_CROSS_BASE}/usr/lib;g" \
- -e "s;-I/usr/include;-I${XBPS_CROSS_BASE}/usr/include;g" \
- -e "s;-isystem;-I${XBPS_CROSS_BASE};g" \
\;
fi
}
next prev parent reply other threads:[~2023-10-16 17:34 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-21 20:02 [PR PATCH] mesa: update to version 23.1.8 SpidFightFR
2023-09-21 20:03 ` [PR PATCH] [Updated] " SpidFightFR
2023-09-21 20:05 ` SpidFightFR
2023-09-21 20:14 ` SpidFightFR
2023-09-21 20:29 ` mhmdanas
2023-09-21 20:29 ` mhmdanas
2023-09-22 4:03 ` SpidFightFR
2023-09-26 13:02 ` SpidFightFR
2023-09-26 13:03 ` SpidFightFR
2023-09-30 12:14 ` [PR PATCH] [Updated] " SpidFightFR
2023-09-30 12:15 ` mesa: update to version 23.2.1 SpidFightFR
2023-09-30 12:36 ` SpidFightFR
2023-10-02 9:45 ` SpidFightFR
2023-10-07 7:21 ` [PR PATCH] [Updated] " SpidFightFR
2023-10-07 7:44 ` SpidFightFR
2023-10-07 13:46 ` mesa: update to version 23.1.9 mhmdanas
2023-10-07 13:47 ` mhmdanas
2023-10-07 13:58 ` SpidFightFR
2023-10-07 13:58 ` SpidFightFR
2023-10-10 7:10 ` [PR PATCH] [Updated] " SpidFightFR
2023-10-10 7:28 ` SpidFightFR
2023-10-10 7:28 ` SpidFightFR
2023-10-10 7:28 ` SpidFightFR
2023-10-10 7:33 ` [PR PATCH] [Updated] " SpidFightFR
2023-10-10 7:40 ` SpidFightFR
2023-10-11 17:15 ` SpidFightFR
2023-10-11 17:36 ` Johnnynator
2023-10-11 17:46 ` Johnnynator
2023-10-11 17:57 ` [PR PATCH] [Updated] " SpidFightFR
2023-10-11 17:58 ` SpidFightFR
2023-10-11 17:59 ` SpidFightFR
2023-10-11 18:01 ` SpidFightFR
2023-10-11 18:02 ` SpidFightFR
2023-10-12 2:13 ` sgn
2023-10-12 12:45 ` sgn
2023-10-12 19:07 ` SpidFightFR
2023-10-14 7:29 ` [PR PATCH] [Updated] " SpidFightFR
2023-10-16 17:30 ` SpidFightFR
2023-10-16 17:34 ` SpidFightFR [this message]
2023-10-16 17:35 ` mesa: update to version 23.2.1 SpidFightFR
2023-10-16 17:38 ` [PR PATCH] [Updated] " SpidFightFR
2023-10-16 17:48 ` Anachron
2023-10-16 18:01 ` [PR PATCH] [Updated] " SpidFightFR
2023-10-16 18:03 ` SpidFightFR
2023-10-16 18:20 ` [PR PATCH] [Updated] " SpidFightFR
2023-10-16 18:20 ` SpidFightFR
2023-11-01 3:39 ` rationalize-zz
2023-11-01 10:20 ` [PR PATCH] [Updated] " SpidFightFR
2023-11-01 10:20 ` SpidFightFR
2023-11-01 10:42 ` SpidFightFR
2023-11-01 16:13 ` [PR REVIEW] " Johnnynator
2023-11-01 16:22 ` SpidFightFR
2023-11-01 16:26 ` [PR PATCH] [Updated] " SpidFightFR
2023-11-01 17:09 ` [PR REVIEW] " SpidFightFR
2023-11-02 9:12 ` [PR PATCH] [Merged]: " Johnnynator
2023-11-02 9:13 ` Johnnynator
2023-11-02 17:37 ` 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=20231016173458.PRezKlu_CeExWGKoSBhBn5cTN6MCJNStZGW_F4fc-8s@z \
--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).