Github messages for voidlinux
 help / color / mirror / Atom feed
From: newbluemoon <newbluemoon@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] ocl-icd: update to 2.3.1
Date: Tue, 09 Nov 2021 21:48:37 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-33999@inbox.vuxu.org> (raw)

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

There is a new pull request by newbluemoon against master on the void-packages repository

https://github.com/newbluemoon/void-packages ocl-icd
https://github.com/void-linux/void-packages/pull/33999

ocl-icd: update to 2.3.1
Current `ocl-icd` 2.2.12 fails to build, update to 2.3.1 fixes it.

<!-- Mark items with [x] where applicable -->

#### General
- [ ] This is a new package and it conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements)

#### Have the results of the proposed changes been tested?
- [ ] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [ ] I generally don't use the affected packages but briefly tested this PR

<!--
If GitHub CI cannot be used to validate the build result (for example, if the
build is likely to take several hours), make sure to
[skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration).
When skipping CI, uncomment and fill out the following section.
Note: for builds that are likely to complete in less than 2 hours, it is not
acceptable to skip CI.
-->
<!-- 
#### Does it build and run successfully? 
(Please choose at least one native build and, if supported, at least one cross build. More are better.)
- [ ] I built this PR locally for my native architecture, (ARCH-LIBC)
- [ ] I built this PR locally for these architectures (if supported. mark crossbuilds):
  - [ ] aarch64-musl
  - [ ] armv7l
  - [ ] armv6l-musl
-->


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

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

From 563760e488df58b5dbde3b9a395e45d12883db99 Mon Sep 17 00:00:00 2001
From: newbluemoon <blaumolch@mailbox.org>
Date: Tue, 9 Nov 2021 21:45:49 +0100
Subject: [PATCH] ocl-icd: update to 2.3.1

---
 srcpkgs/ocl-icd/template | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/srcpkgs/ocl-icd/template b/srcpkgs/ocl-icd/template
index c0a1dabda813..552b0618f78b 100644
--- a/srcpkgs/ocl-icd/template
+++ b/srcpkgs/ocl-icd/template
@@ -1,7 +1,7 @@
 # Template file for 'ocl-icd'
 pkgname=ocl-icd
-version=2.2.12
-revision=2
+version=2.3.1
+revision=1
 build_style=gnu-configure
 hostmakedepends="ruby xmlto asciidoc automake libtool"
 makedepends="opencl2-headers"
@@ -10,7 +10,7 @@ maintainer="Orphaned <orphan@voidlinux.org>"
 license="BSD-2-Clause"
 homepage="https://forge.imag.fr/projects/ocl-icd/"
 distfiles="https://github.com/OCL-dev/${pkgname}/archive/v${version}.tar.gz"
-checksum=17500e5788304eef5b52dbe784cec197bdae64e05eecf38317840d2d05484272
+checksum=a32b67c2d52ffbaf490be9fc18b46428ab807ab11eff7664d7ff75e06cfafd6d
 
 provides="libOpenCL-1.2_1"
 replaces="libOpenCL>=0"

             reply	other threads:[~2021-11-09 20:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-09 20:48 newbluemoon [this message]
2021-11-10  0:09 ` ericonr
2021-11-10  4:45 ` newbluemoon
2021-11-10  6:27 ` ericonr
2021-11-17 14:54 ` newbluemoon
2022-01-28  1:32 ` ericonr
2022-01-28  1:32 ` ericonr
2022-01-28  1:32 ` [PR PATCH] [Closed]: " ericonr
2022-01-28  6:07 ` newbluemoon

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-33999@inbox.vuxu.org \
    --to=newbluemoon@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).