From: Michael Vetter <jubalh@iodoru.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/libstrophe: bump to version 0.10.1
Date: Mon, 4 Jan 2021 11:10:54 +0100 [thread overview]
Message-ID: <20210104101054.5392-1-jubalh@iodoru.org> (raw)
Changes:
* Fixed compilation error when LibreSSL is used
* Fixed crash when NULL is provided as password
Signed-off-by: Michael Vetter <jubalh@iodoru.org>
---
package/libstrophe/libstrophe.hash | 2 +-
package/libstrophe/libstrophe.mk | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/package/libstrophe/libstrophe.hash b/package/libstrophe/libstrophe.hash
index 5f3b098c89..6aca289fb5 100644
--- a/package/libstrophe/libstrophe.hash
+++ b/package/libstrophe/libstrophe.hash
@@ -1,4 +1,4 @@
# Locally calculated
-sha256 8d804e4c74cea1133203cc95a59a88f700fbdaead076e7959b495d734dd7936d libstrophe-0.10.0.tar.gz
+sha256 4918c47029ecdea2deab4b0f9336ca4a8bb12c28b72b2cec397d98664b94c771 libstrophe-0.10.1.tar.gz
sha256 82476f36ffd5e895a176013c0812166ba7b7d99f3d536fc7f5ed2e33e9f74a08 MIT-LICENSE.txt
sha256 8ceb4b9ee5adedde47b31e975c1d90c73ad27b6b165a1dcd80c7c545eb65b903 GPL-LICENSE.txt
diff --git a/package/libstrophe/libstrophe.mk b/package/libstrophe/libstrophe.mk
index 81fc1b9f97..e078eb25cd 100644
--- a/package/libstrophe/libstrophe.mk
+++ b/package/libstrophe/libstrophe.mk
@@ -4,7 +4,7 @@
#
################################################################################
-LIBSTROPHE_VERSION = 0.10.0
+LIBSTROPHE_VERSION = 0.10.1
LIBSTROPHE_SITE = $(call github,strophe,libstrophe,$(LIBSTROPHE_VERSION))
LIBSTROPHE_DEPENDENCIES = openssl host-pkgconf
# Doesn't ship configure
--
2.26.2
next reply other threads:[~2021-01-04 10:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-04 10:10 Michael Vetter [this message]
2021-01-19 21:14 ` [Buildroot] [PATCH 1/1] package/libstrophe: bump to version 0.10.1 Thomas Petazzoni
2021-01-20 8:06 ` Michael Vetter
-- strict thread matches above, loose matches on Subject: below --
2021-03-03 14:49 Michael Vetter
2021-03-04 7:12 ` Peter Korsgaard
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=20210104101054.5392-1-jubalh@iodoru.org \
--to=jubalh@iodoru.org \
--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.