./enter_chroot.sh for testing (core or lib32) and staging configuration should enter corresponding chroot but not stable chroot
Steps to reproduce
- ./make_chroot.sh conf/testing.conf (should also be applied on lib32-testing.conf)
- after first step is done (chroot created), use ./enter_chroot.sh core (or lib32)
- then it will shows chroots/stable doesn't exist
What is the current bug behavior?
Shows chroots/stable doesn't exist.
What is the expected correct behavior?
Enter correct testing chroot.
To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information