From: Min Xu <xuminready@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/shadowsocks-libev bump version to 3.3.3
Date: Thu, 14 Nov 2019 00:28:53 -0800 [thread overview]
Message-ID: <20191114082853.5090-1-xuminready@gmail.com> (raw)
Signed-off-by: Min Xu <xuminready@gmail.com>
---
package/shadowsocks-libev/shadowsocks-libev.hash | 2 +-
package/shadowsocks-libev/shadowsocks-libev.mk | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/package/shadowsocks-libev/shadowsocks-libev.hash b/package/shadowsocks-libev/shadowsocks-libev.hash
index b8bc437..76928eb 100644
--- a/package/shadowsocks-libev/shadowsocks-libev.hash
+++ b/package/shadowsocks-libev/shadowsocks-libev.hash
@@ -1,5 +1,5 @@
# Locally computed
-sha256 65a67c355df1794dc0ef94d80d2d596fd590b13fdcd0a21bda28859c88924ce5 shadowsocks-libev-3.2.4.tar.gz
+sha256 677356a5ed6b5ae9e32a898061db2587158ff27e245db03f4bde9b006ef12dc9 shadowsocks-libev-3.3.3.tar.gz
# License files, locally calculated
sha256 736883f97d44dbec288bb82819f18f4f86d02ae3192f6a9abefa00db76bace41 COPYING
diff --git a/package/shadowsocks-libev/shadowsocks-libev.mk b/package/shadowsocks-libev/shadowsocks-libev.mk
index fcebe34..4b0b963 100644
--- a/package/shadowsocks-libev/shadowsocks-libev.mk
+++ b/package/shadowsocks-libev/shadowsocks-libev.mk
@@ -4,7 +4,7 @@
#
################################################################################
-SHADOWSOCKS_LIBEV_VERSION = 3.2.4
+SHADOWSOCKS_LIBEV_VERSION = 3.3.3
SHADOWSOCKS_LIBEV_SITE = https://github.com/shadowsocks/shadowsocks-libev/releases/download/v$(SHADOWSOCKS_LIBEV_VERSION)
SHADOWSOCKS_LIBEV_LICENSE = GPL-3.0+, BSD-2-Clause (libbloom), BSD-3-Clause (libcork, libipset)
SHADOWSOCKS_LIBEV_LICENSE_FILES = COPYING libbloom/LICENSE libcork/COPYING
--
2.20.1
next reply other threads:[~2019-11-14 8:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-14 8:28 Min Xu [this message]
2019-11-14 16:50 ` [Buildroot] [PATCH 1/1] package/shadowsocks-libev bump version to 3.3.3 Thomas Petazzoni
2019-11-14 20:44 ` xu min
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=20191114082853.5090-1-xuminready@gmail.com \
--to=xuminready@gmail.com \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.