Package Details: ttf-google-fonts-git 1:r11002.cdabad3d0-1

Git Clone URL: https://aur.archlinux.org/ttf-google-fonts-git.git (read-only, click to copy)
Package Base: ttf-google-fonts-git
Description: TrueType fonts from the Google Fonts project (git version)
Upstream URL: https://github.com/google/fonts
Keywords: fonts google ttf
Licenses: custom:SIL Open Font License, custom:Ubuntu Font License v1.0
Conflicts: jsmath-fonts, lohit-fonts, ttf-andika, ttf-arabeyes-fonts, ttf-cardo, ttf-comfortaa, ttf-google-fonts-typewolf, ttf-lekton, ttf-lora-cyrillic, ttf-medievalsharp, ttf-nova, ttf-oxygen, ttf-oxygen-git, ttf-pt-fonts, ttf-source-code-pro-ibx, ttf-source-sans-pro-ibx, ttf-vollkorn-ibx
Provides: jsmath-fonts, lohit-fonts, ttf-andika, ttf-cardo, ttf-carlito, ttf-comfortaa, ttf-lekton, ttf-lora-cyrillic, ttf-medievalsharp, ttf-nova, ttf-oxygen, ttf-oxygen-git, ttf-pt-fonts, ttf-source-code-pro-ibx, ttf-source-sans-pro-ibx, ttf-vollkorn-ibx
Submitter: sebstar
Maintainer: andrewSC
Last Packager: andrewSC
Votes: 560
Popularity: 1.01
First Submitted: 2013-04-27 20:41 (UTC)
Last Updated: 2025-06-30 16:08 (UTC)

Dependencies (24)

Required by (8)

Sources (1)

Pinned Comments

thatgeek commented on 2017-11-17 03:56 (UTC)

If you're having an issue upgraded with errors related to fonts like merriweather, here's my steps to resolve the issue (assuming you have Yaourt): #Clear out what you had before yaourt -R fonts-meta-extended-lt sudo pacman -Rns $(pacman -Qtdq) sudo pacman -R ttf-google-fonts-git sudo pacman -Rns $(pacman -Qtdq) #Install dependencies yaourt -S ttf-merriweather-sans ttf-opensans ttf-oswald ttf-quintessential ttf-signika yaourt -S fonts-meta-extended-lt #Heads up, if ttf-impallari-cantora isn't fixed yet, change the PKGBUILD source to the URL in the comments on the package yaourt -S ttf-impallari-cantora yaourt -S ttf-google-fonts-git

Latest Comments

« First ‹ Previous 1 .. 5 6 7 8 9 10 11 12 13 14 15 .. 40 Next › Last »

FadeMind commented on 2018-03-27 10:48 (UTC)

Hi, this is valid info during making package?

: Can't translate pathname 'usr/share/fonts/배달의민족-한나/' to UTF-8: Can't translate pathname 'usr/share/fonts/나눔고딕/' to UTF-8: Can't translate pathname 'usr/share/fonts/나눔명조/' to UTF-8: Can't translate pathname 'usr/share/fonts/나눔명조/NanumMyeongjo-Bold.ttf' to UTF-8: Can't translate pathname 'usr/share/fonts/나눔명조/NanumMyeongjo-ExtraBold.ttf' to UTF-8: Can't translate pathname 'usr/share/fonts/나눔명조/NanumMyeongjo-Regular.ttf' to UTF-8: Can't translate pathname 'usr/share/fonts/나눔고딕/NanumGothic-Bold.ttf' to UTF-8: Can't translate pathname 'usr/share/fonts/나눔고딕/NanumGothic-ExtraBold.ttf' to UTF-8: Can't translate pathname 'usr/share/fonts/나눔고딕/NanumGothic-Regular.ttf' to UTF-8: Can't translate pathname 'usr/share/fonts/배달의민족-한나/BM-HANNA.ttf' to UTF-8: Can't translate pathname 'usr/share/licenses/ttf-google-fonts-git/LICENSE.배달의민족-한나' to UTF-8: Can't translate pathname 'usr/share/licenses/ttf-google-fonts-git/LICENSE.나눔고딕' to UTF-8: Can't translate pathname 'usr/share/licenses/ttf-google-fonts-git/LICENSE.나눔명조' to UTF-8

Regards ;)

CommodoreCrunch commented on 2018-01-14 07:21 (UTC)

Thanks to Thermi for commenting on one of my packages that I should have bumped the pkgrel on fonts like merriweather. And uhhhhhh sorry you guys had a borked dependency issue for two months. Didn't know!

keepitsimpleengr commented on 2017-11-17 18:47 (UTC) (edited on 2017-11-17 18:48 (UTC) by keepitsimpleengr)

The suggestions (pinned) offered by @thatgeek resulted in successful installation. Thanks to both @thatgeek and to @andrewSC for all his work on this package.

andrewSC commented on 2017-11-17 11:19 (UTC)

pebs74: I'd like to direct your attention to the second pinned comment. Also please make sure you have the latest version of this pkgbuild.

pebs74 commented on 2017-11-17 10:54 (UTC)

getting this error during the latest update: ==> Starting package()... mv: cannot stat '/home/pebs74/.cache/pacaur/ttf-google-fonts-git/pkg/ttf-google-fonts-git/usr/share/fonts/cwtex-仿宋體': No such file or directory ==> ERROR: A failure occurred in package(). Aborting... :: failed to build ttf-google-fonts-git package(s)

andrewSC commented on 2017-11-17 10:12 (UTC)

Throne3d: Thanks for the kind words! And I got my timestamp from the Last Updated field on the fontconfig webpage: https://www.archlinux.org/packages/extra/x86_64/fontconfig/ the difference between that timestamp and the one from git must be the time it takes to deploy ;) Interesting.

thatgeek commented on 2017-11-17 03:56 (UTC)

If you're having an issue upgraded with errors related to fonts like merriweather, here's my steps to resolve the issue (assuming you have Yaourt): #Clear out what you had before yaourt -R fonts-meta-extended-lt sudo pacman -Rns $(pacman -Qtdq) sudo pacman -R ttf-google-fonts-git sudo pacman -Rns $(pacman -Qtdq) #Install dependencies yaourt -S ttf-merriweather-sans ttf-opensans ttf-oswald ttf-quintessential ttf-signika yaourt -S fonts-meta-extended-lt #Heads up, if ttf-impallari-cantora isn't fixed yet, change the PKGBUILD source to the URL in the comments on the package yaourt -S ttf-impallari-cantora yaourt -S ttf-google-fonts-git

Throne3d commented on 2017-11-16 22:49 (UTC)

@andrewSC apparently I just have great timing, to have sent that message four minutes after the announcement. :P I didn't realize it hadn't landed in extra until today. Where did you get the timestamp 15:41 from? Looking around a bit, I can find a commit at 15:39:59 which looks to be doing it: https://git.archlinux.org/svntogit/packages.git/commit/?h=packages/fontconfig&id=b680d4fc7cf52b8ea8287d78b0c6563d93faf55f That makes sense, to centralize the onus on keeping font packages updated, assuming the other packages get it from some other source which is kept sufficiently updated. And yeah – it seems like a good choice, from how the list has been growing so rapidly. Thank you for your work in maintaining this package!

andrewSC commented on 2017-11-16 19:30 (UTC)

Throne3d: Technically correct. I do want to note that it landed in extra today (2017-11-16 15:41 UTC) from the testing repo and that's what I was waiting for. The package has been updated to reflect the fix (per the announcement I made prior to your comment). Regarding your separate question, yes, my understanding is the same as yours in that the upstream repo is simply a collection of fonts which may or may not be the latest version of any given font. In short, the upstream repo is not _always_ the latest version of a given font. Again, this is my understanding. A point to make though is it seems that anyone can go and make updates to a font upstream so that it is indeed the latest version. In theory this package could potentially have a dependency on a font that becomes outdated (while google/fonts contains the latest version). However, in that case I want to put the onus on the community to contact the maintainer of the outdated dependency font package and have them update it accordingly. The idea here is that we'll improve the quality of the font packages within the community (while at the same time, improve the health/prevent rot of the AUR). Does that make sense? Also, we're not talking half or even a quarter of the fonts provided by this package as existent within the AUR, but there are more than 10 lol.

Throne3d commented on 2017-11-16 18:25 (UTC)

@andrewSC: it looks like there's been a release since the linked commit (assuming the timestamp is for when it was merged into the main tree) – 2.12.6; this was added to extra/fontconfig almost two days ago: https://git.archlinux.org/svntogit/packages.git/commit/trunk?h=packages/fontconfig&id=30e82412901f2421b73587ef5d7b99a9167b78f9 I've been getting the listed error and I'm on this version, so it seems like the package should be updated as a result of this. Separately – I was worried, at first, about the fonts being moved to dependencies – git packages are usually more up-to-date than their stable alternatives, so I thought this was restricting the package to the less recently updated stable versions of packages. However, unless I'm misunderstanding, the upstream git repo actually just collects together the latest versions of the relevant fonts, and that's why it's okay to move them to dependencies? (I'd appreciate clarification.)

« First ‹ Previous 1 .. 5 6 7 8 9 10 11 12 13 14 15 .. 40 Next › Last »