From: dkwo <dkwo@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] xrootd: update to 5.5.1
Date: Sat, 04 Feb 2023 17:55:12 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42076@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 550 bytes --]
There is a new pull request by dkwo against master on the void-packages repository
https://github.com/dkwo/void-packages O3xr
https://github.com/void-linux/void-packages/pull/42076
xrootd: update to 5.5.1
- I tested the changes in this PR: no
- I built this PR locally for my native architecture, (x86_64-musl)
Builds fine with openssl3 #37681 but note https://github.com/xrootd/xrootd/issues/1877
It performs no tests, so it is hard to tell @BenJarg
A patch file from https://github.com/void-linux/void-packages/pull/42076.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-O3xr-42076.patch --]
[-- Type: text/x-diff, Size: 1105 bytes --]
From 39714f9489c3078c61af578232ea46a30d4e19b2 Mon Sep 17 00:00:00 2001
From: dkwo <nicolopiazzalunga@gmail.com>
Date: Sat, 4 Feb 2023 11:51:41 -0500
Subject: [PATCH] xrootd: update to 5.5.1
---
srcpkgs/xrootd/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/xrootd/template b/srcpkgs/xrootd/template
index 2bd0b59714c2..3973741d0e3e 100644
--- a/srcpkgs/xrootd/template
+++ b/srcpkgs/xrootd/template
@@ -1,6 +1,6 @@
# Template file for 'xrootd'
pkgname=xrootd
-version=5.4.2
+version=5.5.1
revision=1
build_style=cmake
makedepends="zlib-devel openssl-devel libuuid-devel readline-devel"
@@ -9,7 +9,7 @@ maintainer="Ben Jargowsky <benjar63@gmail.com>"
license="LGPL-3.0-or-later"
homepage="https://xrootd.slac.stanford.edu"
distfiles="http://xrootd.org/download/v${version}/xrootd-${version}.tar.gz"
-checksum=d868ba5d8b71ec38f7a113d2d8f3e25bbcedc1bc23d21bba1686ddfdb2b900c1
+checksum=3556d5afcae20ed9a12c89229d515492f6c6f94f829a3d537f5880fcd2fa77e4
if [ "$XBPS_TARGET_LIBC" = musl ]; then
configure_args+=" -DCMAKE_CXX_STANDARD_LIBRARIES=-lexecinfo"
next reply other threads:[~2023-02-04 16:55 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-04 16:55 dkwo [this message]
2023-02-06 13:10 ` amadio
2023-02-06 19:27 ` dkwo
2023-02-14 21:10 ` dkwo
2023-02-14 21:27 ` [PR PATCH] [Updated] " dkwo
2023-02-14 21:30 ` BenJarg
2023-02-14 21:31 ` BenJarg
2023-02-14 21:46 ` [PR PATCH] [Updated] " dkwo
2023-02-14 21:47 ` dkwo
2023-02-15 9:19 ` amadio
2023-03-02 22:43 ` dkwo
2023-03-03 8:03 ` amadio
2023-05-15 15:01 ` xrootd: update dkwo
2023-05-16 6:09 ` amadio
2023-05-16 6:10 ` amadio
2023-05-16 14:44 ` dkwo
2023-05-23 8:01 ` amadio
2023-05-23 11:31 ` dkwo
2023-05-23 12:03 ` amadio
2023-05-23 12:19 ` amadio
2023-05-23 12:20 ` amadio
2023-05-23 12:21 ` amadio
2023-05-23 14:49 ` dkwo
2023-05-23 14:53 ` [PR PATCH] [Updated] " dkwo
2023-06-24 14:45 ` [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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42076@inbox.vuxu.org \
--to=dkwo@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).