From: motorto <motorto@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] lksctp-tools: update to 1.0.19.
Date: Wed, 10 Aug 2022 13:08:38 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38581@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 824 bytes --]
There is a new pull request by motorto against master on the void-packages repository
https://github.com/motorto/void-packages lksctp-tools
https://github.com/void-linux/void-packages/pull/38581
lksctp-tools: update to 1.0.19.
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### 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-glibc
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- armv6l
Orphaning the package because git blame tells me that is pullmoll the creator of the package.
Updating the package to make it build with #38412
A patch file from https://github.com/void-linux/void-packages/pull/38581.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-lksctp-tools-38581.patch --]
[-- Type: text/x-diff, Size: 1439 bytes --]
From 217a69663060458774f6e8a01af071014f942cb0 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Andr=C3=A9=20Cerqueira?= <acerqueira021@gmail.com>
Date: Wed, 10 Aug 2022 12:05:38 +0100
Subject: [PATCH] lksctp-tools: update to 1.0.19; orphan.
---
srcpkgs/lksctp-tools/template | 12 ++++--------
1 file changed, 4 insertions(+), 8 deletions(-)
diff --git a/srcpkgs/lksctp-tools/template b/srcpkgs/lksctp-tools/template
index 7fd8f02aa1ca..6bb8061d6473 100644
--- a/srcpkgs/lksctp-tools/template
+++ b/srcpkgs/lksctp-tools/template
@@ -1,24 +1,20 @@
# Template file for 'lksctp-tools'
pkgname=lksctp-tools
-version=1.0.18
-revision=2
+version=1.0.19
+revision=1
build_style=gnu-configure
hostmakedepends="automake libtool linux-headers"
short_desc="User-space access to Linux Kernel SCTP"
-maintainer="bitshark <bitshark@bitshark.net>"
+maintainer="Orphaned <orphan@voidlinux.org>"
license="GPL-2.0-or-later, LGPL-2.1-only"
homepage="http://lksctp.sourceforge.net"
distfiles="https://github.com/sctp/lksctp-tools/archive/v${version}.tar.gz"
-checksum=3e9ab5b3844a8b65fc8152633aafe85f406e6da463e53921583dfc4a443ff03a
+checksum=9251b1368472fb55aaeafe4787131bdde4e96758f6170620bc75b638449cef01
pre_configure() {
autoreconf -fi
}
-post_install() {
- mv ${DESTDIR}/usr/include/netinet/sctp.h{.in,}
-}
-
lksctp-tools-devel_package() {
depends="${makedepends} ${sourcepkg}>=${version}_${revision}"
short_desc+=" - development files"
next reply other threads:[~2022-08-10 11:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-10 11:08 motorto [this message]
2022-08-10 23:02 ` [PR REVIEW] " classabbyamp
2022-08-10 23:05 ` [PR PATCH] [Updated] " motorto
2022-08-10 23:05 ` [PR REVIEW] " motorto
2022-08-10 23:09 ` [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-38581@inbox.vuxu.org \
--to=motorto@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).