v2.1.0

What's Changed

Major Fixes

• Fixed package management issue in Arch-based distributions by automatically resolving pacman-related problems.
  See: #73
• Fixed internet connectivity issues in some distributions, ensuring compatibility with both systemd and non-systemd systems.
  See: #88
• Fixed mount point verification issues.
  See: #93

Improvements

• Added colored output for error, note, and warning messages to improve readability.
• Updated how-to.md to include new sections:
  • Fixing sudo issues
  • Adding a custom distribution
  • Running chroot-distro on GNU/Linux systems
  • Deleting a chroot-distro environment

Other Fixes

• Fixed some minor issues not noticeable by the user.

Full Changelog: v2.0.0...v2.1.0

v2.0.0

Sorry, I don't have time to write this right now. I will edit it later.

Full Changelog: v1.4.0...v2.0.0

v1.4.0

What's Changed

• Kali rootfs download fix by @pluseach in #65
• Void alpine rootfs download fix by @pluseach in #64
• Fix download links by @jjkola in #66
  • With above mentioned changes every download link should now work properly
  • Every download link has been updated to the latest available version
  • Also, apart from the issue mentioned in known issues there is currently no known bugs (only feature requests) with this release, and as such it is recommended to update to this version.

New Contributors

• @pluseach made their first contribution in #65

Known issues

• Busybox for Android NDK may not be found from the PATH #60
  • If you are experiencing the issue we would like to hear from you so that it can be fixed properly. In the case you are experiencing the issue, please comment on the issue and provide the asked information.

Full Changelog: v1.3.2...v1.4.0

v1.3.2

What's Changed

• Fix relative custom backup path handling by @jjkola in #61

Full Changelog: v1.3.1...v1.3.2

v1.3.1

What's Changed

• Fix slow lsof check by @jjkola in #57
• Added a check for resolv.conf being a broken link by @jjkola in #58

Full Changelog: v1.3.0...v1.3.1

Known issues

• Custom backup path with relative path is saved at wrong location #59
  • Workaround is to use absolute path.
  • This is a regression from 1.1.0 version.

v1.3.0

What's Changed

• Force unmount and unmount all mount points by @jjkola in #50

Full Changelog: v1.2.3...v1.3.0

v1.2.3

What's Changed

• Fix distro identification check by @jjkola in #48
• Fix backup compression by @jjkola in #48
• Fix restoring backups without compression by @jjkola in #48

Users are strongly recommended to upgrade to this version.

This version fixes a security problem with distro identification check (accepted anything as a distro identification). Also, starting with this version the compression is always used for the backups (custom backups are compressed based on extension). Before 1.2.0 some of the backups were compressed, and a regression caused versions starting from 1.2.0 to not compress backups at all when using Busybox or Toybox tar. Also, in the case user tried to restore such uncompressed backups the restore would fail (regression from 1.1.0).

Full Changelog: v1.2.2...v1.2.3

v1.2.2

What's Changed

• Unconditionally remove /dev/pts system mount point by @jjkola in #45
• Fix Magisk version detection for the cases where there is no separate 32/64 version by @jjkola in #47

Full Changelog: v1.2.1...v1.2.2

v1.2.1

Fixed version information

Full Changelog: v1.2.0...v1.2.1

v1.2.0

What's Changed

• Fix KernelSU/APatch/Magisk without separately installed Busybox NDK by @jjkola in #44

Full Changelog: v1.1.5...v1.2.0