Hello everyone,
Calamares 2.3-beta2 is here. The present tarball is the result of a week of
bug fixing: we are now steadily reaching the end of the 2.3 pre-release cycle.
Calamares 2.3 final might happen as early as next friday, or should unexpected
issues come up, 2 weeks from now.
Changes since 2.3-beta1 include:
* fixed build with GCC 4.9 series (my bad for dropping in C++14 features);
* fixed very long standing issue with filesystem check jobs randomly failing
with a "Possibly non-existent device?" message from e2fsck (this was most
noticeable with Alongside install operations, though not every time);
* updated KPMcore dependency to 2.2;
* added support for NVME device naming scheme in fstab module;
* added support for generating /etc/crypttab, this relies on a single master
passphrase (for the rootfs) and on the luksbootkeyfile module, which creates a
keyfile on / and registers it with all the LUKS-encrypted partitions for which
the user selected a mount point.
I have personally tested a manual install with 3 LUKS-encrypted partitions
(rootfs, swap and /home) on EFI and it worked flawlessly, but much more
testing is absolutely essential at this point.
Tarball:
https://calamares.io/downloads/calamares-2.3-beta2.tar.gz
SHA1: d476c0479181080893450473f64d1821ec8d8c17
MD5: 7cd495715b43c9727ca995c286ef3893
### Note for packagers ###
If you've been waiting for the right time to work on your Calamares 2.3
deployment, my suggestion is to start now. Calamares 2.3 final is around the
corner, so this is your chance to
1) help make 2.3 a polished and high quality software product by reporting
Calamares bugs on our issue tracker [1],
2) get a head start on packaging and configuring distribution specific bits
(some of this might be non-trivial because of changes required by the LUKS
feature),
3) identify and fix distro-specific bugs early, so you don't have to wait for
later 2.3.x series releases to get something that works for you.
[1]
https://calamares.io/bugs/
Cheers,
--
Teo Mrnjavac
http://teom.org |
t...@kde.org