From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] hdf5: update to 1.10.5.
Date: Sun, 23 Jun 2019 16:40:14 +0200 [thread overview]
Message-ID: <20190623144014.k6Waw1nZGIgkrpcf6LPWNFKZpzXaIL0F-MvR1_z53N0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-12627@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 315 bytes --]
There is an updated pull request by Piraty against master on the void-packages repository
https://github.com/Piraty/void-packages hdf5-1.10.5
https://github.com/void-linux/void-packages/pull/12627
hdf5: update to 1.10.5.
A patch file from https://github.com/void-linux/void-packages/pull/12627.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-hdf5-1.10.5-12627.patch --]
[-- Type: application/text/x-diff, Size: 1815 bytes --]
From 83974365f291c8de39244d5f8a4ef0239e58f499 Mon Sep 17 00:00:00 2001
From: Piraty <piraty1@inbox.ru>
Date: Sun, 23 Jun 2019 00:40:52 +0200
Subject: [PATCH] hdf5: update to 1.10.5.
no revbumps required, because no package uses to the libhdf5_fortran
library.
---
common/shlibs | 2 +-
srcpkgs/hdf5/template | 6 +++---
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/common/shlibs b/common/shlibs
index 0f6742b2fa4..433add7d202 100644
--- a/common/shlibs
+++ b/common/shlibs
@@ -2307,7 +2307,7 @@ libhdf5.so.103 hdf5-1.10.4_1
libhdf5_hl_cpp.so.100 hdf5-1.10.1_2
libhdf5_cpp.so.103 hdf5-1.10.4_1
libhdf5hl_fortran.so.100 hdf5-1.10.1_2
-libhdf5_fortran.so.100 hdf5-1.10.1_2
+libhdf5_fortran.so.102 hdf5-1.10.5_1
libhdf5.so.10 hdf5-18-1.8.20_1
libhdf5_hl.so.10 hdf5-18-1.8.20_1
libhdf5_hl_cpp.so.11 hdf5-18-1.8.20_1
diff --git a/srcpkgs/hdf5/template b/srcpkgs/hdf5/template
index c5ecc418bdb..e035fa670ab 100644
--- a/srcpkgs/hdf5/template
+++ b/srcpkgs/hdf5/template
@@ -1,17 +1,17 @@
# Template file for 'hdf5'
pkgname=hdf5
-version=1.10.4
+version=1.10.5
revision=1
build_style=gnu-configure
configure_args="--enable-cxx --enable-fortran"
hostmakedepends="gcc-fortran"
makedepends="zlib-devel"
-short_desc="A data model, library, and file format for storing and managing data"
+short_desc="Data model, library, and file format for storing and managing data"
maintainer="pulux <pulux@pf4sh.de>"
license="custom"
homepage="https://hdfgroup.org"
distfiles="https://www.hdfgroup.org/ftp/HDF5/current/src/hdf5-${version}.tar.gz"
-checksum=8f60dc4dd6ab5fcd23c750d1dc5bca3d0453bdce5c8cdaf0a4a61a9d1122adb2
+checksum=6d4ce8bf902a97b050f6f491f4268634e252a63dadd6656a1a9be5b7b7726fa8
nocross="https://portal.hdfgroup.org/pages/viewpage.action?pageId=48808266"
post_install() {
next prev parent reply other threads:[~2019-06-23 14:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-22 22:49 [PR PATCH] " voidlinux-github
2019-06-23 14:40 ` voidlinux-github [this message]
2019-06-23 14:40 ` [PR PATCH] [Updated] " voidlinux-github
2019-06-25 6:44 ` voidlinux-github
2019-06-25 9:24 ` voidlinux-github
2019-06-25 9:45 ` [PR PATCH] [Merged]: " voidlinux-github
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=20190623144014.k6Waw1nZGIgkrpcf6LPWNFKZpzXaIL0F-MvR1_z53N0@z \
--to=voidlinux-github@inbox.vuxu.org \
--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).