From: rhynix <rhynix@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] socat: update to 1.7.4.4.
Date: Wed, 30 Nov 2022 18:33:48 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40859@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 888 bytes --]
There is a new pull request by rhynix against master on the void-packages repository
https://github.com/rhynix/void-packages socat-1.7.4.4
https://github.com/void-linux/void-packages/pull/40859
socat: update to 1.7.4.4.
The extra `configure_args` for musl is no longer necessary since this has been fixed upstream.
See: https://repo.or.cz/socat.git/commit/75cb44bc90577c3487458564ca803163681319f1
#### Testing the changes
- I tested the changes in this PR: **briefly**
#### Local build testing
- I built this PR locally for my native architecture, x86_64-musl
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- aarch64-musl (crossbuild)
- aarch64 (crossbuild)
- armv7l-musl (crossbuild)
- armv7l (crossbuild)
- x86_64 (crossbuild)
A patch file from https://github.com/void-linux/void-packages/pull/40859.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-socat-1.7.4.4-40859.patch --]
[-- Type: text/x-diff, Size: 1296 bytes --]
From c98861383537e881032c4192653b99c4bdf3c783 Mon Sep 17 00:00:00 2001
From: Rik Tonnard <rik@tonnard.nl>
Date: Wed, 30 Nov 2022 18:23:48 +0100
Subject: [PATCH] socat: update to 1.7.4.4.
The extra configure_args for musl is no longer necessary since this has
been fixed upstream.
See: https://repo.or.cz/socat.git/commit/75cb44bc90577c3487458564ca803163681319f1
---
srcpkgs/socat/template | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/srcpkgs/socat/template b/srcpkgs/socat/template
index 44fe3e4ce6d6..639ebf28042b 100644
--- a/srcpkgs/socat/template
+++ b/srcpkgs/socat/template
@@ -1,6 +1,6 @@
# Template file for 'socat'
pkgname=socat
-version=1.7.4.3
+version=1.7.4.4
revision=1
build_style=gnu-configure
configure_args="--disable-libwrap --enable-fips
@@ -11,11 +11,10 @@ maintainer="Orphaned <orphan@voidlinux.org>"
license="GPL-2.0-only"
homepage="http://www.dest-unreach.org/socat/"
distfiles="http://www.dest-unreach.org/socat/download/socat-${version}.tar.bz2"
-checksum=d47318104415077635119dfee44bcfb41de3497374a9a001b1aff6e2f0858007
+checksum=fbd42bd2f0e54a3af6d01bdf15385384ab82dbc0e4f1a5e153b3e0be1b6380ac
case "$XBPS_TARGET_MACHINE" in
*-musl) CFLAGS="-D_LINUX_IF_ETHER_H"
- configure_args+=" sc_cv_getprotobynumber_r=2"
;;
esac
next reply other threads:[~2022-11-30 17:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-30 17:33 rhynix [this message]
2022-12-02 3:28 ` [PR REVIEW] " classabbyamp
2022-12-02 10:19 ` [PR PATCH] [Updated] " rhynix
2022-12-02 17:00 ` classabbyamp
2022-12-02 17:05 ` [PR PATCH] [Updated] " rhynix
2022-12-02 17:06 ` rhynix
2022-12-02 17:36 ` [PR PATCH] [Merged]: " classabbyamp
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-40859@inbox.vuxu.org \
--to=rhynix@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).