From: Bnyro <Bnyro@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] iproute2: update to 6.4.0.
Date: Mon, 31 Jul 2023 15:58:05 +0200 [thread overview]
Message-ID: <20230731135805.FMOcGEnFsJ3SpgGqpAXaYfmpaGOaQFNFAtjSaLUtv8Q@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45353@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 480 bytes --]
There is an updated pull request by Bnyro against master on the void-packages repository
https://github.com/Bnyro/void-packages iproute2
https://github.com/void-linux/void-packages/pull/45353
iproute2: update to 6.4.0.
#### 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
A patch file from https://github.com/void-linux/void-packages/pull/45353.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-iproute2-45353.patch --]
[-- Type: text/x-diff, Size: 1793 bytes --]
From 4a473a9f22b3dc8a0a1ecc5e8ecdb8c79215bc6b Mon Sep 17 00:00:00 2001
From: Bnyro <bnyro@tutanota.com>
Date: Mon, 31 Jul 2023 15:43:23 +0200
Subject: [PATCH] iproute2: update to 6.4.0.
---
srcpkgs/iproute2/patches/include-limits-h.patch | 14 ++++++++++++++
srcpkgs/iproute2/template | 4 ++--
2 files changed, 16 insertions(+), 2 deletions(-)
create mode 100644 srcpkgs/iproute2/patches/include-limits-h.patch
diff --git a/srcpkgs/iproute2/patches/include-limits-h.patch b/srcpkgs/iproute2/patches/include-limits-h.patch
new file mode 100644
index 0000000000000..fd46ed681b7f9
--- /dev/null
+++ b/srcpkgs/iproute2/patches/include-limits-h.patch
@@ -0,0 +1,14 @@
+import missing on musl
+--
+diff --git a/bridge/mdb.c b/bridge/mdb.c
+index fbb4f70..1879345 100644
+--- a/bridge/mdb.c
++++ b/bridge/mdb.c
+@@ -15,6 +15,7 @@
+ #include <string.h>
+ #include <arpa/inet.h>
+ #include <netdb.h>
++#include <limits.h>
+
+ #include "libnetlink.h"
+ #include "utils.h"
diff --git a/srcpkgs/iproute2/template b/srcpkgs/iproute2/template
index 6d188731ec1fe..e7ca6e6527a46 100644
--- a/srcpkgs/iproute2/template
+++ b/srcpkgs/iproute2/template
@@ -1,6 +1,6 @@
# Template file for 'iproute2'
pkgname=iproute2
-version=6.3.0
+version=6.4.0
revision=1
build_style=configure
make_install_args="SBINDIR=/usr/bin"
@@ -11,7 +11,7 @@ maintainer="Enno Boland <gottox@voidlinux.org>"
license="GPL-2.0-only"
homepage="https://wiki.linuxfoundation.org/networking/iproute2"
distfiles="${KERNEL_SITE}/utils/net/iproute2/iproute2-${version}.tar.xz"
-checksum=dfb2a98db96e7a653cffc6693335a1a466e29a34b6ac528be48f35e1d2766732
+checksum=4c51b8decbc7e4da159ffb066f590cfb93dbf9af7ff86b1647ce42b7c179a272
# Requires unshare, which is not provided by chroot-util-linux.
make_check=no
next prev parent reply other threads:[~2023-07-31 13:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-31 13:48 [PR PATCH] " Bnyro
2023-07-31 13:56 ` [PR PATCH] [Updated] " Bnyro
2023-07-31 13:58 ` Bnyro [this message]
2023-08-04 16:43 ` [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=20230731135805.FMOcGEnFsJ3SpgGqpAXaYfmpaGOaQFNFAtjSaLUtv8Q@z \
--to=bnyro@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).