RAUC v1.2 Released
Right before the ELC-E starts tomorrow, we used the time in the hotel to bake a brand new RAUC release for you (and your embedded devices)! Well, here it is: RAUC v1.2
Are there any good reasons for updating to it? Of course! As always there is a good mix of bug fixes and new features your setups will benefit from:
We fixed some leaking file descriptors that may have caused RAUC to be killed with ‘Too many open files’ errors when executing a significant number of 'rauc status' or 'rauc install' actions without reboot.
RAUC now also will abort earlier in case of errors that are detectable before actually entering the atomic region and writing slots. This allows RAUC to fail earlier without leaving behind a disabled slot group with incomplete contents.
Another noteworthy change is that we changed the default of one of RAUC's most discussed optimization features: The skipping of slot updates where the intended and the current slots hash matches exactly. The past showed that this behaviour was often perceived as 'unexpected'. It is now disabled by default but may be explicitly enabled with install-same=false.
The command line interface received some new features and polishing so that we now have a more structured status output and an optional installation progress, activatable with rauc install --progress [...].
For devices that boot from the first MBR partition, RAUC now also supports atomic bootloader updates by manipulating the MBR to switch between redundant partition regions.
Thanks to all contributors since v1.1: Bastian Krause, Ellie Reeves, Enrico Jörns, Fabian Knapp, Gaël PORTAY, Jan Lübbe, Leif Middelschulte, Michael Heimpold , Stephan Michaelsen , Thomas Hämmerle, Thorsten Scherer, Tobias Junghans, Uwe Kleine-König
"Getting things off the ground" could be the motto for the v1.9 release of RAUC. The support for custom metadata in the manifest got a step further, a new, more flexible, D-Bus API for bundle inspection paved the way for obtaining more detailed information, and a new manifest hash marks the first of several planned changes for configurable event logging. However, one of the most invasive changes happened under the hood: We have started the transition from autotools to meson as a build system.