From: someone13574 <someone13574@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] nvidia-vaapi-driver: update to 0.0.11.
Date: Wed, 08 Nov 2023 21:24:39 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-47126@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 520 bytes --]
There is a new pull request by someone13574 against master on the void-packages repository
https://github.com/someone13574/void-packages nvidia-vaapi-driver-0.0.11
https://github.com/void-linux/void-packages/pull/47126
nvidia-vaapi-driver: update to 0.0.11.
#### 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-glibc)
A patch file from https://github.com/void-linux/void-packages/pull/47126.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-nvidia-vaapi-driver-0.0.11-47126.patch --]
[-- Type: text/x-diff, Size: 1124 bytes --]
From 35dde249fa4459775732e11bd37c3ec2cc4adde1 Mon Sep 17 00:00:00 2001
From: Owen Law <owenlaw222@gmail.com>
Date: Wed, 8 Nov 2023 15:20:50 -0500
Subject: [PATCH] nvidia-vaapi-driver: update to 0.0.11.
---
srcpkgs/nvidia-vaapi-driver/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/nvidia-vaapi-driver/template b/srcpkgs/nvidia-vaapi-driver/template
index f0278f19a33ac..48f33fc0c62c2 100644
--- a/srcpkgs/nvidia-vaapi-driver/template
+++ b/srcpkgs/nvidia-vaapi-driver/template
@@ -1,6 +1,6 @@
# Template file for 'nvidia-vaapi-driver'
pkgname=nvidia-vaapi-driver
-version=0.0.10
+version=0.0.11
revision=1
archs="x86_64"
build_style=meson
@@ -11,7 +11,7 @@ maintainer="Owen Law <owenlaw222@gmail.com>"
license="MIT"
homepage="https://github.com/elFarto/nvidia-vaapi-driver"
distfiles="https://github.com/elFarto/nvidia-vaapi-driver/archive/refs/tags/v${version}.tar.gz"
-checksum=df63b0832ccf9f74a90ff8b26d8e069606e0614d1748e35a857d2e53745ab95c
+checksum=3e1ed95d7e2b2b1377c9cb59c3e7caaf960134694e9441e1d91c38f224d1d5d9
conflicts="libva-vdpau-driver"
post_install() {
next reply other threads:[~2023-11-08 20:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-08 20:24 someone13574 [this message]
2023-12-03 20:09 ` [PR PATCH] [Merged]: " Duncaen
-- strict thread matches above, loose matches on Subject: below --
2023-11-08 14:31 [PR PATCH] " dataCobra
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-47126@inbox.vuxu.org \
--to=someone13574@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).