| Git Clone URL: | https://aur.archlinux.org/nerd-fonts-sf-mono.git (read-only, click to copy) |
|---|---|
| Package Base: | nerd-fonts-sf-mono |
| Description: | Monospaced variant of San Francisco. Sourced directly from Apple, patched with the Nerd Fonts Patcher |
| Upstream URL: | https://developer.apple.com/fonts/ |
| Keywords: | apple font fonts francisco mono monospace nerd nerd-fonts nerdfonts otf san sanfrancisco sf |
| Licenses: | custom |
| Conflicts: | nerd-fonts-sf-mono |
| Provides: | nerd-fonts-sf-mono |
| Submitter: | D3SOX |
| Maintainer: | D3SOX |
| Last Packager: | D3SOX |
| Votes: | 12 |
| Popularity: | 0.004239 |
| First Submitted: | 2020-09-23 11:59 (UTC) |
| Last Updated: | 2025-05-11 10:45 (UTC) |
==> Validating source files with sha256sums...
SF-Mono-14.dmg ... Passed
font-patcher-3.4.0 ... FAILED
==> ERROR: One or more files did not pass the validity check!
Wrong FontPatcher checksum. Maybe it has re-released its 3.4 version.
> wget https://github.com/ryanoasis/nerd-fonts/releases/download/v3.4.0/FontPatcher.zip
> sha256sum FontPatcher.zip
a8f11e511ed7c69e96680858c06b50a643ea7752e26d5cd13dd5e5cc53ab1760 FontPatcher.zip
As ttz suggested, the font is failing to patch via python.
Using "fontforge -script" instead of python to call the font patcher, fixed my build problem.
Suggest modifying the build() command's last line to:
fontforge -script instead of python to call the font patcherI had to do this in order to get it to build.
@D3SOX font patching unfortunately did not work for me when building the package without an AUR helper
@ripsivis weird, wasn't able to replicate. Performance wise it's about the same my machine.
For some reason, parallel command no longer works. All I know is that the command exits with 255.
But we can use xargs for a similar approach, just replace the parallel's line with this:
ls "$srcdir/Library/Fonts"/*.otf | xargs -P $(nproc) -I {} python "$srcdir/font-patcher" -q -c -s {} -out "$srcdir/patched" &> /dev/null
or just apply this patch: https://gist.github.com/onurmercury/507628bf575080a4c729b5cedb32e6b0
@sentientmachin3 Hm ok maybe yay has some bug when checking out via Subversion. I could change how it fetches the glyphs but I don't think it's worth the hassle. If it works when building it manually via makepkg it should work with yay too so I see the problem on yay's side (or some sort of setup issue with yay on your machine)
@D3SOX I built it with paru as well. I don't know what changes, but it works. Yay is still failing.
@sentientmachin3 I just successfully built the package again (using paru but that shouldn't matter).
The PowerlineSymbols.otf is definitely inside src/glyphs/powerline-symbols/ and the one in src/glyphs/ is named PowerlineExtraSymbols.otf
@D3SOX apparently the build process is looking for PowerlineSymbols.otf in src/glyphs/powerline-symbols/, but I found no powerline-symbols folder, instead my file is in src/glyphs/.
Pinned Comments
D3SOX commented on 2021-09-28 07:25 (UTC)
I'm using a change detection to see when Apple updates the font. If the build doesn't work because of a checksum failure for
SF-Mono.dmgplease flag it out-of-date.