From: Gary Bisson <gary.bisson@boundarydevices.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] swupdate: bump to version 2016.10
Date: Tue, 8 Nov 2016 15:34:46 +0100 [thread overview]
Message-ID: <20161108143446.9525-1-gary.bisson@boundarydevices.com> (raw)
A short list of new features:
- progress interface as general way to signalize the update
status outside of the process.
- support encrypted artifacts (encryption via simmetric keys)
- host verification for swu images (-c option)
- configuration file to configure the update process
- HAwkbit backend: API extended, support for configData messages
- Hawkbit backend: supports SSL certificates
- remote handler : general interface to connect external
installers.
Signed-off-by: Gary Bisson <gary.bisson@boundarydevices.com>
---
package/swupdate/swupdate.hash | 2 +-
package/swupdate/swupdate.mk | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/package/swupdate/swupdate.hash b/package/swupdate/swupdate.hash
index 918ca2f..1ba10f6 100644
--- a/package/swupdate/swupdate.hash
+++ b/package/swupdate/swupdate.hash
@@ -1,2 +1,2 @@
# Locally calculated
-sha256 c21d2fd52eb7ed9c304a7a996d230a8f1b47b9879a8c9fa50c80b41e117d1e60 swupdate-2016.07.tar.gz
+sha256 840d6287a41f7a42e08a74045ee40b7c2f82c1ecfedf8c915e3935d4f0084376 swupdate-2016.10.tar.gz
diff --git a/package/swupdate/swupdate.mk b/package/swupdate/swupdate.mk
index d442810..c905c1d 100644
--- a/package/swupdate/swupdate.mk
+++ b/package/swupdate/swupdate.mk
@@ -4,7 +4,7 @@
#
################################################################################
-SWUPDATE_VERSION = 2016.07
+SWUPDATE_VERSION = 2016.10
SWUPDATE_SITE = $(call github,sbabic,swupdate,$(SWUPDATE_VERSION))
SWUPDATE_LICENSE = GPLv2+, MIT, Public Domain
SWUPDATE_LICENSE_FILES = COPYING
--
2.9.3
next reply other threads:[~2016-11-08 14:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-08 14:34 Gary Bisson [this message]
2016-11-09 21:37 ` [Buildroot] [PATCH] swupdate: bump to version 2016.10 Thomas Petazzoni
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=20161108143446.9525-1-gary.bisson@boundarydevices.com \
--to=gary.bisson@boundarydevices.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox