Hi
Did anyone else encounter the following error when trying to create and install the package?
Is there a need to remove any old installation from the package, and do the reinstallation?
Log of errors
Git Clone URL: | https://aur.archlinux.org/ttf-ms-win10.git (read-only, click to copy) |
---|---|
Package Base: | ttf-ms-win10 |
Description: | Microsoft Windows 10 TrueType fonts |
Upstream URL: | http://www.microsoft.com/typography/fonts/product.aspx?PID=164 |
Licenses: | custom |
Conflicts: | ttf-ms-fonts, ttf-tahoma, ttf-vista-fonts |
Provides: | ttf-font, ttf-ms-fonts, ttf-tahoma |
Submitter: | Bevan |
Maintainer: | Bevan (Scimmia) |
Last Packager: | Scimmia |
Votes: | 122 |
Popularity: | 1.28 |
First Submitted: | 2015-08-21 07:39 (UTC) |
Last Updated: | 2021-10-18 14:15 (UTC) |
« First ‹ Previous 1 .. 4 5 6 7 8 9 10 11 12 13 14 .. 24 Next › Last »
Hi
Did anyone else encounter the following error when trying to create and install the package?
Is there a need to remove any old installation from the package, and do the reinstallation?
Log of errors
Could you please fix the readme? wimlib is available in the repo's. :)
And both are crap. The AUR uses git, if you want a different version, just check that version out.
ttf-win7-fonts has done multiple SHA sums for many years now. ttf-ms-win8 has it too.
Ataraxy: Multiple SHA sums for one file are not possible. We could only set it to "SKIP" to completely ignore them but I don't think that's a good idea. If you know what causes the different checksum (as in this case), you can simply run updpkgsums before makepkg as a workaround. Or run makepkg with the argument --skipchecksums.
I have a fully updated Win10 box, with cour.ttf saying it is File version 6.90.
d4557f9674de7c5ef58ad4c3651016944672c6bf1f5e9253abfeea9730939808 cour.ttf
Is it possible to allow more than one SHAsum for a file? What version does the PKGBUILD expect?
Good to know, thanks for the quick help!
@chraffx: The checksum of that file was changed in Januar's Windows update, so we updated it here as well. I guess you have some pending updates that haven't been installed after your recent installation yet.
@Bevan ah, thx, I misinterpreted the skip as an error. The one that actually failed was cour.ttf, which was fixed by changing the checksum entry '8da71b5c11b17bade23095559fb0905741c15ee2f8800b1fa0ceb100e3fd6f45' to '4dc9a0be2df1d3872a3fae62be7c7aec1b6d6838a4a3302c6428a06635f4d2cb'. My windows install was pretty recent, are there two versions of that file? Or is that entry just outdated?
@chraffx: The checksum of license.rtf differs for different languages and maybe also different versions of Windows. That's why we skip the checksum check for that file (last entry of sha256sums is 'SKIP').
Pinned Comments
Bevan commented on 2019-04-16 07:36 (UTC) (edited on 2019-07-11 18:01 (UTC) by Bevan)
FAQ, please read before posting:
I get an error that the sources cannot be downloaded: Please read the instructions on the top of the PKGBUILD.
Some fonts are missing in my copy of Windows (e.g., holomdl2, corbel, chandra, ...): It seems that Microsoft distributes some fonts only with some Windows versions. You can just comment out the corresponding line in the PKGBUILD and then build with "makepkg --skipchecksums".
Some fonts have different checksums: We keep the checksums synchronized with our own Windows installations that are regularly updated. Different Windows versions, different ISOs etc. may contain fonts in different versions/variants. Just build the package using "makepkg --skipchecksums".
Why does the version not correspond to the latest Windows 10 build: If fonts have not changes between builds, there is no reason to change the version number of this package.
Why are some fonts (e.g., traditional chinese, japanese etc.) not included here, not even in the corresponding split packages: We currently only include fonts that are installed on a standard Windows installation, without additional feature-on-demand packages (see: https://docs.microsoft.com/en-us/typography/fonts/windows_10_font_list).
Bevan commented on 2016-08-08 18:05 (UTC)