From: uhohspaghetios <uhohspaghetios@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] rdma-core: update to 37.1
Date: Thu, 04 Nov 2021 18:41:04 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-33905@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1782 bytes --]
There is a new pull request by uhohspaghetios against master on the void-packages repository
https://github.com/uhohspaghetios/void-packages rdma-core-37.1
https://github.com/void-linux/void-packages/pull/33905
rdma-core: update to 37.1
<!-- Mark items with [x] where applicable -->
#### General
- [x] 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
-->
Please confirm I did the hostmakedepends correctly with pandoc and python3-docutils, needed to build the manpages. Installs and works on my RDMA-enabled storage cluster.
A patch file from https://github.com/void-linux/void-packages/pull/33905.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-rdma-core-37.1-33905.patch --]
[-- Type: text/x-diff, Size: 1429 bytes --]
From 216c6e053d9502f71b326fd65029ba2d3ac412c2 Mon Sep 17 00:00:00 2001
From: uhohspaghetios <rich@servermonkeys.com>
Date: Thu, 4 Nov 2021 13:27:15 -0400
Subject: [PATCH] rdma-core: update to 37.1
---
srcpkgs/rdma-core/template | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/srcpkgs/rdma-core/template b/srcpkgs/rdma-core/template
index 25f1e1e6bb84..c405e5ebda07 100644
--- a/srcpkgs/rdma-core/template
+++ b/srcpkgs/rdma-core/template
@@ -1,17 +1,17 @@
# Template file for 'rdma-core'
pkgname=rdma-core
-version=23.3
+version=37.1
revision=1
build_style=cmake
configure_args="-DENABLE_VALGRIND=OFF"
-hostmakedepends="pkg-config python3"
-makedepends="libnl3-devel eudev-libudev-devel python3-devel"
+hostmakedepends="pandoc pkg-config python3 python3-docutils"
+makedepends="libnl3-devel eudev-libudev-devel python3-Cython python3-devel"
short_desc="RDMA core userspace libraries and daemons"
-maintainer="Rich G <rich@richgannon.net>"
+maintainer="uhohspaghetios <rich@servermonkeys.com>"
license="GPL-2.0-or-later, BSD-2-Clause-FreeBSD"
homepage="https://github.com/linux-rdma/rdma-core"
distfiles="https://github.com/linux-rdma/rdma-core/releases/download/v${version}/rdma-core-${version}.tar.gz"
-checksum=0afb7aa2654ea914c3b5d12e6e8f2fc3f325b0a52da1febf4f66788bf0b2bb14
+checksum=3ff6ff0592eb0ff92e829b39ea6eaf1365f9a9c401e8e2a17e1b915edc535cc2
conf_files="
/etc/iwpmd.conf
next reply other threads:[~2021-11-04 17:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-04 17:41 uhohspaghetios [this message]
2022-01-29 21:05 ` [PR PATCH] [Closed]: " uhohspaghetios
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-33905@inbox.vuxu.org \
--to=uhohspaghetios@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).