From: zlice <zlice@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] libdrm: update to 2.4.119
Date: Thu, 11 Jan 2024 18:26:08 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48170@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 598 bytes --]
There is a new pull request by zlice against master on the void-packages repository
https://github.com/zlice/void-packages libdrm-2.4.119
https://github.com/void-linux/void-packages/pull/48170
libdrm: update to 2.4.119
<!-- 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**
#### Comments
need any revbumps?
A patch file from https://github.com/void-linux/void-packages/pull/48170.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-libdrm-2.4.119-48170.patch --]
[-- Type: text/x-diff, Size: 1105 bytes --]
From 16fe4b4c36f10a51c30c240e7f9d52962f97fb6c Mon Sep 17 00:00:00 2001
From: zlice <zlice555@gmail.com>
Date: Thu, 11 Jan 2024 12:20:08 -0500
Subject: [PATCH] libdrm: update to 2.4.119
---
srcpkgs/libdrm/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/libdrm/template b/srcpkgs/libdrm/template
index 5c7578cef7450..ffbd8bcab7195 100644
--- a/srcpkgs/libdrm/template
+++ b/srcpkgs/libdrm/template
@@ -1,6 +1,6 @@
# Template file for 'libdrm'
pkgname=libdrm
-version=2.4.115
+version=2.4.119
revision=1
build_style=meson
configure_args="-Dudev=true -Dvalgrind=disabled -Dinstall-test-programs=true"
@@ -11,7 +11,7 @@ maintainer="Orphaned <orphan@voidlinux.org>"
license="MIT"
homepage="https://dri.freedesktop.org/"
distfiles="https://gitlab.freedesktop.org/mesa/drm/-/archive/libdrm-${version}/drm-libdrm-${version}.tar.gz"
-checksum=fd8b7c6e4e40d13c32ab67ace2cb6c71e08c9ca53124ff33ccadd74f604117e3
+checksum=6e798976e175f1f6e83706681644d0ce0527855b95a471479875ae3c1ef9870a
case "$XBPS_TARGET_MACHINE" in
aarch64*) configure_args+=" -Dvc4=enabled";;
next reply other threads:[~2024-01-11 17:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-11 17:26 zlice [this message]
2024-02-01 17:43 ` SpidFightFR
2024-02-01 17:47 ` zlice
2024-02-01 18:20 ` SpidFightFR
2024-02-15 12:49 ` [PR PATCH] [Closed]: " zlice
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-48170@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).