@boyd8444 building in a chroot is always recommended, for safety reasons. If yay doesn't support this, you shouldn't use it.
"To avoid problems caused by your particular system configuration, build packages in a clean chroot. If the build process still fails in a clean chroot, the issue is probably with the PKGBUILD."
-- https://wiki.archlinux.org/title/Arch_User_Repository
Apart from this, the PKGBUILD always explained, that you need to clean-up manually after failed buidling attempts. So please read the PKGBUILD instructions, before complaining:
# If the
# build fails, it might be that these must be unmounted manually. This can be
# done with:
#
# $ udisksctl unmount -b /dev/loop0
# $ udisksctl loop-delete -b /dev/loop0
# $ fusermount -uz src/mnt/http
#
# Replace /dev/loop0 with the relevant loop device, which is reported during
# package build.
Pinned Comments
Zepman commented on 2021-02-24 16:49 (UTC) (edited on 2021-03-24 22:08 (UTC) by Zepman)
This package is based on ttf-ms-win10. It differs in that it automatically downloads the fonts from Microsoft, if possible without downloading an entire ISO file.
If Polkit allows the user to create loop devices and mount files using udisks, around 200 MB of (mostly compressed) data will be downloaded. This can be a slow download method even over the fastest connections, since the fonts are taken from a large ISO file without downloading the entire file.
If Polkit is not available or it does not allow the user to use udisks, the entire ISO file will be downloaded and install.wim will be extracted. A check ensures that enough temporary disk space is available, which can be up to twice the size of the ISO file. This can happen if either Polkit or an authentication agent is not running, or when a user is logged in remotely (e.g. through SSH).