Broken chroot configuration in feature/buster?
Originally created by @CyrilBrulebois on #16289 (Redmine)
Here’s the current configuration:
$ ls -l config/chroot_sources/*
lrwxrwxrwx 1 kibi kibi 10 Sep 9 2016 config/chroot_sources/sid.binary -> sid.chroot
-rw-r--r-- 1 kibi kibi 63 Oct 1 16:48 config/chroot_sources/sid.chroot
lrwxrwxrwx 1 kibi kibi 12 Sep 9 2016 config/chroot_sources/tails.binary -> tails.chroot
lrwxrwxrwx 1 kibi kibi 16 Sep 9 2016 config/chroot_sources/tails.binary.gpg -> tails.chroot.gpg
-rw-r--r-- 1 kibi kibi 5909 Oct 1 16:48 config/chroot_sources/tails.chroot.gpg
lrwxrwxrwx 1 kibi kibi 17 Sep 9 2016 config/chroot_sources/torproject.binary -> torproject.chroot
lrwxrwxrwx 1 kibi kibi 21 Sep 9 2016 config/chroot_sources/torproject.binary.gpg -> torproject.chroot.gpg
-rw-r--r-- 1 kibi kibi 57 Jan 5 14:24 config/chroot_sources/torproject.chroot
-rw-r--r-- 1 kibi kibi 45068 Jan 4 14:20 config/chroot_sources/torproject.chroot.gpgwhich means tails.binary is a broken symlink to tails.chroot.
This doesn’t lead to an FTBFS but that should probably be fixed?
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information