From: Enrico Joerns <ejo@pengutronix.de>
To: rauc@pengutronix.de
Subject: [RAUC] [ANNOUNCE] RAUC v0.1.1 released
Date: Thu, 11 May 2017 18:10:57 +0200 [thread overview]
Message-ID: <0551dbea-fc2d-0975-d763-506157fcb35d@pengutronix.de> (raw)
Hi,
we are proud to announce that we've just released RAUC v0.1.1:
https://github.com/rauc/rauc/releases/tag/v0.1.1
This is mainly a bugfix release. We also introduced a CHANGES file that
allows you to track the project development from a more high-level
perspective:
http://rauc.readthedocs.io/en/latest/changes.html
For the current version, the changes are as follows (copy+paste from
`CHANGES`):
Release 0.1.1 (released May 11, 2017)
-------------------------------------
.. rubric:: Enhancements
* systemd service: allow systemd to manage and cleanup RAUCs mount directory
.. rubric:: Bugs fixed
* Fix signature verification with OpenSSL 1.1.x by adding missing binary
flag
* Fix typo in json status output formatter ("mountpint" -> "mountpoint")
* Fixed packaging of systemd service files by removing generated service
files
from distribution
* src/context: initialize datainstream to NULL
* Added missing git-version-gen script to automake distribution which made
autoreconf runs on release packages fail
* Fixed D-Bus activation of RAUC service for non-systemd systems
.. rubric:: Documentation
* Added contribution guideline
* Added CHANGES file
* Converted README.md to README.rst
* Added RAUC logo
* Several typos fixed
* Updated documentation for mainline PTXdist recipes
Best regards,
The RAUC Team
--
Pengutronix e.K. | Enrico Jörns |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-5080 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
RAUC mailing list
_______________________________________________
RAUC mailing list
reply other threads:[~2017-05-11 16:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=0551dbea-fc2d-0975-d763-506157fcb35d@pengutronix.de \
--to=ejo@pengutronix.de \
--cc=rauc@pengutronix.de \
/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