Github messages for voidlinux
 help / color / mirror / Atom feed
From: icp1994 <icp1994@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] libva{,-glx,-utils}: update to 2.18
Date: Fri, 31 Mar 2023 09:57:53 +0200	[thread overview]
Message-ID: <20230331075753.JsfYrkFPxGg6_xQtbPqPZcTFFo55Z5XsDtIXv1IxPfI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43102@inbox.vuxu.org>

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

There is an updated pull request by icp1994 against master on the void-packages repository

https://github.com/icp1994/void-packages libva
https://github.com/void-linux/void-packages/pull/43102

libva{,-glx,-utils}: update to 2.18
#### 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**

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

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

From 587f9a8372421dc158557b24def5192501f2018c Mon Sep 17 00:00:00 2001
From: icp <pangolin@vivaldi.net>
Date: Tue, 28 Mar 2023 01:20:49 +0530
Subject: [PATCH 1/3] libva: update to 2.18.0.

---
 srcpkgs/libva/template | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/srcpkgs/libva/template b/srcpkgs/libva/template
index 5bb1bbd13a22..a411f3ee45da 100644
--- a/srcpkgs/libva/template
+++ b/srcpkgs/libva/template
@@ -1,7 +1,7 @@
 # Template file for 'libva'
-# NOTE: keep this pkg synchronized with libva-glx
+# NOTE: keep this pkg synchronized with libva-glx and the minor version with libva-utils
 pkgname=libva
-version=2.17.0
+version=2.18.0
 revision=1
 build_style=meson
 configure_args="-Dwith_glx=no"
@@ -13,8 +13,8 @@ maintainer="Orphaned <orphan@voidlinux.org>"
 license="MIT"
 homepage="https://01.org/linuxmedia/vaapi"
 changelog="https://raw.githubusercontent.com/intel/libva/master/NEWS"
-distfiles="https://github.com/intel/libva/archive/${version}.tar.gz"
-checksum=8940541980ef998a36cd8f6ad905e81838ea4ddf56dc479ed2bebd12711e6001
+distfiles="https://github.com/intel/libva/archive/refs/tags/${version}.tar.gz"
+checksum=9d666c70c12dfefcdd27ae7dea771557f75e24961d0ed4cb050d96fb6136f438
 
 build_options="wayland"
 build_options_default="wayland"

From 211fb01cf50675c0ff8fc74391ff963560a5a8f0 Mon Sep 17 00:00:00 2001
From: icp <pangolin@vivaldi.net>
Date: Tue, 28 Mar 2023 01:23:20 +0530
Subject: [PATCH 2/3] libva-glx: update to 2.18.0.

---
 srcpkgs/libva-glx/template | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/srcpkgs/libva-glx/template b/srcpkgs/libva-glx/template
index 2e4849927001..4c299577993d 100644
--- a/srcpkgs/libva-glx/template
+++ b/srcpkgs/libva-glx/template
@@ -4,10 +4,10 @@
 #
 # 	libva -> mesa -> libva
 #
-# KEEP THIS PACKAGE SYNCHRONIZED WITH "libva".
+# NOTE: keep this pkg synchronized with libva and the minor version with libva-utils
 #
 pkgname=libva-glx
-version=2.17.0
+version=2.18.0
 revision=1
 build_style=meson
 configure_args="-Dwith_glx=yes -Dwith_wayland=yes"
@@ -18,8 +18,8 @@ maintainer="Orphaned <orphan@voidlinux.org>"
 license="MIT"
 homepage="https://01.org/linuxmedia/vaapi"
 changelog="https://raw.githubusercontent.com/intel/libva/master/NEWS"
-distfiles="https://github.com/intel/libva/archive/${version}.tar.gz"
-checksum=8940541980ef998a36cd8f6ad905e81838ea4ddf56dc479ed2bebd12711e6001
+distfiles="https://github.com/intel/libva/archive/refs/tags/${version}.tar.gz"
+checksum=9d666c70c12dfefcdd27ae7dea771557f75e24961d0ed4cb050d96fb6136f438
 
 post_install() {
 	# We are only interested in the glx component, remove everything else.

From 05b309d760bb63901ba5586b04149c8b444921b8 Mon Sep 17 00:00:00 2001
From: icp <pangolin@vivaldi.net>
Date: Fri, 31 Mar 2023 13:20:10 +0530
Subject: [PATCH 3/3] libva-utils: update to 2.18.1.

---
 srcpkgs/libva-utils/template | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/srcpkgs/libva-utils/template b/srcpkgs/libva-utils/template
index e5422e5921a3..ba8e66cde3b0 100644
--- a/srcpkgs/libva-utils/template
+++ b/srcpkgs/libva-utils/template
@@ -1,6 +1,7 @@
 # Template file for 'libva-utils'
+# NOTE: keep minor version synchronized with libva and libva-glx
 pkgname=libva-utils
-version=2.17.1
+version=2.18.1
 revision=1
 build_style=meson
 configure_args="-Ddrm=true -Dx11=true -Dwayland=true"
@@ -13,7 +14,7 @@ license="MIT"
 homepage="https://01.org/linuxmedia"
 changelog="https://raw.githubusercontent.com/intel/libva-utils/master/NEWS"
 distfiles="https://github.com/intel/libva-utils/archive/refs/tags/${version}.tar.gz"
-checksum=6ea5993c3eba230a979fa9d35b4cad8df06d4474a773dc0918033bf50353f966
+checksum=79da4a683dc4b10639edd7ad4c9434789ef208f5361f87aca9bc986a4ebcb155
 
 post_install() {
 	vlicense COPYING

  parent reply	other threads:[~2023-03-31  7:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-29 18:54 [PR PATCH] " icp1994
2023-03-30 20:23 ` [PR REVIEW] " paper42
2023-03-31  7:57 ` icp1994 [this message]
2023-04-11 23:54 ` mhmdanas
2023-04-25 20:14 ` [PR PATCH] [Updated] " icp1994
2023-06-23 20:05 ` [PR PATCH] [Merged]: " Duncaen

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=20230331075753.JsfYrkFPxGg6_xQtbPqPZcTFFo55Z5XsDtIXv1IxPfI@z \
    --to=icp1994@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).