From: znedw <znedw@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] boringtun: update to 0.3.0.
Date: Mon, 27 Apr 2020 23:45:19 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-21413@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 346 bytes --]
There is a new pull request by znedw against master on the void-packages repository
https://github.com/znedw/void-packages master
https://github.com/void-linux/void-packages/pull/21413
boringtun: update to 0.3.0.
compiles on musl without a patch now :)
A patch file from https://github.com/void-linux/void-packages/pull/21413.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-master-21413.patch --]
[-- Type: text/x-diff, Size: 2479 bytes --]
From 947d0612e2ddb117becb9a6fc99ca3330fea9ce4 Mon Sep 17 00:00:00 2001
From: Zach Nedwich <zach@znedw.com>
Date: Tue, 28 Apr 2020 07:30:10 +1000
Subject: [PATCH] boringtun: update to 0.3.0.
---
...y-letting-Rust-infer-the-correct-typ.patch | 26 -------------------
srcpkgs/boringtun/template | 4 +--
2 files changed, 2 insertions(+), 28 deletions(-)
delete mode 100644 srcpkgs/boringtun/patches/0001-Fix-musl-build-by-letting-Rust-infer-the-correct-typ.patch
diff --git a/srcpkgs/boringtun/patches/0001-Fix-musl-build-by-letting-Rust-infer-the-correct-typ.patch b/srcpkgs/boringtun/patches/0001-Fix-musl-build-by-letting-Rust-infer-the-correct-typ.patch
deleted file mode 100644
index 54bbab5842b..00000000000
--- a/srcpkgs/boringtun/patches/0001-Fix-musl-build-by-letting-Rust-infer-the-correct-typ.patch
+++ /dev/null
@@ -1,26 +0,0 @@
-From 3fad8bed118e629a985da17bf7af3de43e1e690b Mon Sep 17 00:00:00 2001
-From: Vlad Krasnov <vkrasnov@users.noreply.github.com>
-Date: Tue, 2 Apr 2019 07:37:55 -0400
-Subject: [PATCH] Fix musl build by letting Rust infer the correct type for
- SIOCGIFMTU (#60)
-
----
- src/device/tun_linux.rs | 2 +-
- 1 file changed, 1 insertion(+), 1 deletion(-)
-
-diff --git a/src/device/tun_linux.rs b/src/device/tun_linux.rs
-index ffac9c6..7167553 100644
---- src/device/tun_linux.rs
-+++ src/device/tun_linux.rs
-@@ -122,7 +122,7 @@ impl TunSocket {
-
- ifr.ifr_name[..iface_name.len()].copy_from_slice(iface_name);
-
-- if unsafe { ioctl(fd, SIOCGIFMTU, &ifr) } < 0 {
-+ if unsafe { ioctl(fd, SIOCGIFMTU as _, &ifr) } < 0 {
- return Err(Error::IOCtl(errno_str()));
- }
-
---
-2.24.0
-
diff --git a/srcpkgs/boringtun/template b/srcpkgs/boringtun/template
index f8007444c8e..d74a72f6c84 100644
--- a/srcpkgs/boringtun/template
+++ b/srcpkgs/boringtun/template
@@ -1,6 +1,6 @@
# Template file for 'boringtun'
pkgname=boringtun
-version=0.2.0
+version=0.3.0
revision=1
build_style=cargo
short_desc="Implementation of the WireGuard protocol"
@@ -8,7 +8,7 @@ maintainer="Zach Nedwich <zach@znedw.com>"
license="BSD-3-Clause"
homepage="https://github.com/cloudflare/boringtun"
distfiles="https://github.com/cloudflare/${pkgname}/archive/v${version}.tar.gz"
-checksum=544c72fc482b636e7f6460bfee205adafc55de534067819e4e4914980f0d1350
+checksum=@7ba22dcb785c9dfa99d70fc3ea0fa86908debd59eabc278f65db50a22bcc731c
case "$XBPS_TARGET_MACHINE" in
ppc*) broken="ftbfs in ring" ;;
next reply other threads:[~2020-04-27 21:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-27 21:45 znedw [this message]
2020-04-28 13:13 ` [PR PATCH] [Merged]: " Hoshpak
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-21413@inbox.vuxu.org \
--to=znedw@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).