Arch Linux User Repository

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).

@knuxyl thanks for the report. Do you call makepkg manually or do you use an AUR helper?

Do you use a clean chroot?

This doesn't work. It errors saying /dev/loop0 or whichever is already mounted, which was mounted by this pkgbuild. I had to manually umount the http and /dev/loop mounts, restarted, tried again, same problem. The loop device is mounted with the iso file this script downloads, and then complains it's already mounted and fails.

Hey @carlosal1015,

while not pretty there's no way to prevent this warnings to appear at the moment.

Please read the instructions in the PKGBUILD before reporting:

Please ignore any 'ln' errors when building this package. This is expected  behavior.

Thanks!

Hi, I have the following message during installation

==> Removing existing $srcdir/ directory...
==> Extracting sources...
ln: failed to create symbolic link '/tmp/makepkg/ttf-ms-win10-auto/src/' -> '': No such file or directory
ln: failed to create symbolic link '/tmp/makepkg/ttf-ms-win10-auto/src/' -> '': No such file or directory
ln: failed to create symbolic link '/tmp/makepkg/ttf-ms-win10-auto/src/' -> '': No such file or directory
ln: failed to create symbolic link '/tmp/makepkg/ttf-ms-win10-auto/src/' -> '': No such file or directory
ln: failed to create symbolic link '/tmp/makepkg/ttf-ms-win10-auto/src/' -> '': No such file or directory
ln: failed to create symbolic link '/tmp/makepkg/ttf-ms-win10-auto/src/' -> '': No such file or directory
ln: failed to create symbolic link '/tmp/m

To whom it may concern: Don't feed the troll. Thanks :)

@RubenKelevra Noob? It sounds like you're the noob here since you can't even manage to make a working PKGBUILD.

@boyd8444 yeah, I end the discussion here. This is not the place for noobs to ask basic questions.

Have a nice day.

@RubenKelevra If I were an official package maintainer I might make the effort to use a chroot build environment, but yay uses a normal user to build and has the option to remove build dependencies which is all I need.

Your needs may be different, but claiming that a chroot build environment is more serure is just false. A chroot in no way protects you from installing malicious code if that is what you mean by security.

@boyd8444 pkgrel 6 includes the suggested cleanup code and may work in your setup.

Anyway, I suggest moving away from yay, as building packages outside a chroot is not a safe practice.

And stop marking packages out of date, if they are not out of date, just because they don't build for you. That's what comments are for.

@RubenKelevra I saw the instructions about loopback devices and didn't ignore them, but thought a well designed PKGBUILD should include error handling for this case. We just disagree.

You are correct to point out that yay does not support a chroot build environment and so is not supported.

The ttf-ms-win11-auto worked with yay so I switched to that one.