Skip to content

v2.1.3

Choose a tag to compare

View all tags
@Torxed Torxed released this 29 Mar 16:31
· 3641 commits to master since this release
v2.1.3
This tag was signed with the committer’s verified signature. The key has expired.
Torxed Anton Hvornum
GPG key ID: F1234C5BA67C59DF
Expired
Verified
Learn about vigilant mode.
bb5caf7
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.

This is a minor release and addresses some smaller bugs that were creeping around.

  • A inconsistency was detected when trying to format a disk/partition that previously had encryption enabled and going to a setup where encryption was not used. This was identified by @Didr and the issue was that the Partition().encrypted flag was carried over from the internal cache (created initially when building the cache to present to the user during initialization).
    • The .encrypted flag is now more accurately set by correctly identifying file system as reported by the kernel rather than our own internal cache after .format is called. It also checks the parent device if there is one to not falsely check on unlocked encrypted devices.
  • #116 has partially been corrected, in that the log will fall back to ./ if archinstall couldn't put the log in /var/log/archinstall
  • sys_command now has a better working workdir flag to put logs and execute from.
  • Removed vfat as a root-partition option
  • Fixed an issue where completely empty drives would cause a glitch due to .has_content()'s mount command would crash due to "wrong fs type".

No new features were added.

Assets 3
Loading