@andrewSC Please update it to the one provided by: jeagoss commented on 2022-01-10 01:27 (UTC)
Search Criteria
Package Details: ttf-google-fonts-git 1:r2002.37e0f8a4-1
Package Actions
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: | adobe-source-code-pro-fonts, adobe-source-sans-pro-fonts, jsmath-fonts, lohit-fonts, ttf-andika, ttf-anonymous-pro, ttf-arabeyes-fonts, ttf-caladea, ttf-cardo, ttf-comfortaa, ttf-google-fonts-typewolf, ttf-lato, ttf-lekton, ttf-lora-cyrillic, ttf-medievalsharp, ttf-nova, ttf-oxygen, ttf-oxygen-git, ttf-pt-fonts, ttf-roboto-mono, ttf-source-code-pro-ibx, ttf-source-sans-pro-ibx, ttf-vollkorn-ibx |
Provides: | adobe-source-code-pro-fonts, adobe-source-sans-pro-fonts, jsmath-fonts, lohit-fonts, ttf-andika, ttf-anonymous-pro, ttf-caladea, ttf-cardo, ttf-comfortaa, ttf-lato, ttf-lekton, ttf-lora-cyrillic, ttf-medievalsharp, ttf-nova, ttf-oxygen, ttf-oxygen-git, ttf-pt-fonts, ttf-roboto-mono, ttf-source-code-pro-ibx, ttf-source-sans-pro-ibx, ttf-vollkorn-ibx |
Submitter: | sebstar |
Maintainer: | andrewSC |
Last Packager: | andrewSC |
Votes: | 557 |
Popularity: | 2.50 |
First Submitted: | 2013-04-27 20:41 (UTC) |
Last Updated: | 2020-07-23 20:49 (UTC) |
Dependencies (17)
- cantarell-fonts (cantarell-fonts-0.100, cantarell-static-fonts)
- noto-fonts (ttf-noto-fonts-ib, ttf-noto-fonts-simple, noto-fonts-variable-lite, noto-fonts-lite)
- noto-fonts-extra (noto-fonts-variable-lite)
- ttf-croscore
- ttf-fira-mono
- ttf-fira-sans (ttf-google-fonts-typewolf)
- ttf-inconsolata (ttf-google-fonts-typewolf)
- ttf-merriweather (ttf-google-fonts-typewolf)
- ttf-merriweather-sans
- ttf-opensans (ttf-google-fonts-typewolf)
- ttf-oswald
- ttf-quintessential
- ttf-roboto (ttf-roboto-fontconfig, ttf-google-fonts-typewolf)
- ttf-signika
- ttf-ubuntu-font-family
- fontconfig (fontconfig-srb, fontconfig-minimal-git, fontconfig-git, fontconfig-ubuntu) (make)
- git (git-git, git-vfs, git-run-command-patch-git) (make)
Required by (28)
- adobe-source-pro-fonts (requires adobe-source-code-pro-fonts)
- adobe-source-pro-fonts (requires adobe-source-sans-pro-fonts)
- all-repository-fonts (requires ttf-caladea)
- all-repository-fonts (requires adobe-source-code-pro-fonts)
- all-repository-fonts (requires ttf-lato)
- all-repository-fonts (requires ttf-roboto-mono)
- all-repository-fonts (requires ttf-anonymous-pro)
- fonts-meta-extended-lt (requires ttf-caladea)
- gnome-shell-theme-viva-git (requires adobe-source-sans-pro-fonts)
- gsettings-desktop-schemas-338 (requires adobe-source-code-pro-fonts)
- gsettings-desktop-schemas-dev (requires adobe-source-code-pro-fonts)
- gsettings-desktop-schemas-git (requires adobe-source-code-pro-fonts)
- gsettings-desktop-schemas-oldstable (requires adobe-source-code-pro-fonts)
- insync (requires adobe-source-code-pro-fonts)
- llpp-git (requires adobe-source-code-pro-fonts) (optional)
- multicolor-sddm-theme (optional)
- o20-git (requires ttf-roboto-mono)
- peppercarrot-fonts (requires lohit-fonts)
- radium (requires ttf-lato)
- regolith-desktop-config (requires adobe-source-code-pro-fonts)
Sources (1)
Latest Comments
05storm26 commented on 2022-05-30 11:02 (UTC)
andrewSC commented on 2022-04-11 14:55 (UTC)
vishvas: Thanks for the heads up--i'll incorporate the feedback into the next PKGBUILD update
vishvas commented on 2022-04-11 04:32 (UTC) (edited on 2022-04-11 04:35 (UTC) by vishvas)
Please remove "Noto Color Emoji Compat Test". No reason to include test fonts in production environment (being in conflict with adobe-source-code-pro-fonts, this package is an indirect dependency of gsettings-desktop-schemas-git etc.). Badly misrenders 🦅🦍…🐒🐍.
Drishal commented on 2022-03-24 05:37 (UTC)
One small question I have, why are fonts like adobe and fira in conflict with google fonts?
andrewSC commented on 2022-01-10 15:32 (UTC)
Thanks jeagoss, I'll take a look at the changes and incorporate them into the PKGBUILD
jeagoss commented on 2022-01-10 01:27 (UTC)
I've updated the PKGBUILD for this to include omitted_font_families that are in community and extra, and updated depends, conflicts, and provides.
The updated PKGBUILD can be seen here. https://pastebin.com/ecdiL3B7
jopejoe1 commented on 2021-10-14 21:08 (UTC)
ttf-roboto-mono, ttf-lato, ttf-caladea, ttf-anonymous-pro, adobe-source-sans-fonts, adobe-source-code-pro-fonts are in the community and extra repos and it would be nice if they could be added to the omitted_font_families list like other fonts that are in the community and extra repos.
dwheeler commented on 2021-08-29 05:00 (UTC)
The package adobe-source-sans-pro-fonts was renamed to adobe-source-sans-fonts. Please update the conflicts and provides arrays to reflect this.
andrewSC commented on 2021-08-14 21:38 (UTC)
Just a heads up if you're having trouble building this try deleting your fonts repo folder and building the package in a clean chroot (after installing the package deps in it first). I was able to build e9c23c2ef64eb190f12d0e54f0ce75e14ac32b95 from upstream main branch without issue.
sebstar commented on 2021-07-25 12:57 (UTC)
Getting
Cloning into 'fonts'...
done.
warning: remote HEAD refers to nonexistent ref, unable to checkout.
==> Starting prepare()...
rm: cannot remove '/home/$USER/.cache/yay/ttf-google-fonts-git/src/fonts/ofl/adobeblank': No such file or directory
==> ERROR: A failure occurred in prepare().
Aborting...
during latest upgrade to r2002.37e0f8a4-1
.
deathtrip commented on 2021-03-07 13:51 (UTC)
i tried deleting the fonts folder and still get the error
gustawho commented on 2021-03-02 03:21 (UTC)
@xuanruiqi You might be keeping the sources of AUR packages. Upstream recently changed their primary branch from "master" to "main". Try deleting the "fonts" directory.
xuanruiqi commented on 2021-02-28 00:22 (UTC)
Am I the only one getting this?
==> Extracting sources...
-> Creating working copy of fonts git repo...
fatal: invalid reference: origin/HEAD
JohnnyDeacon commented on 2020-12-18 15:56 (UTC)
How can i fix this conflict?
: ttf-google-fonts-git and adobe-source-code-pro-fonts are in conflict. Remove adobe-source-code-pro-fonts? [y/N] y :: ttf-google-fonts-git and ttf-google-fonts-typewolf are in conflict (adobe-source-sans-pro-fonts). Remove ttf-google-fonts-typewolf? [y/N] y error: failed to prepare transaction (could not satisfy dependencies) :: unable to satisfy dependency 'ttf-fira-sans' required by ttf-google-fonts-git :: unable to satisfy dependency 'ttf-roboto' required by ttf-google-fonts-git :: unable to satisfy dependency 'ttf-inconsolata' required by ttf-google-fonts-git :: unable to satisfy dependency 'ttf-merriweather' required by ttf-google-fonts-git :: unable to satisfy dependency 'ttf-opensans' required by ttf-google-fonts-git
andrewSC commented on 2020-07-23 20:49 (UTC)
I've reverted the Rubik revert in prepare() as it doesn't seem apparent to me that this is an issue anymore. If anyone has trouble with it please let me know. Thanks!
theaifam5 commented on 2020-07-23 20:13 (UTC)
Same on my side, unpossible to build:
CONFLICT (modify/delete): ofl/rubik/Rubik-Regular.ttf deleted in HEAD and modified in parent of dfd43510... rubik: v2.100 added with VTT hinting (#1076). Version parent of dfd43510... rubik: v2.100 added with VTT hinting (#1076) of ofl/rubik/Rubik-Regular.ttf left in tree.
CONFLICT (modify/delete): ofl/rubik/Rubik-MediumItalic.ttf deleted in HEAD and modified in parent of dfd43510... rubik: v2.100 added with VTT hinting (#1076). Version parent of dfd43510... rubik: v2.100 added with VTT hinting (#1076) of ofl/rubik/Rubik-MediumItalic.ttf left in tree.
CONFLICT (modify/delete): ofl/rubik/Rubik-Medium.ttf deleted in HEAD and modified in parent of dfd43510... rubik: v2.100 added with VTT hinting (#1076). Version parent of dfd43510... rubik: v2.100 added with VTT hinting (#1076) of ofl/rubik/Rubik-Medium.ttf left in tree.
CONFLICT (modify/delete): ofl/rubik/Rubik-LightItalic.ttf deleted in HEAD and modified in parent of dfd43510... rubik: v2.100 added with VTT hinting (#1076). Version parent of dfd43510... rubik: v2.100 added with VTT hinting (#1076) of ofl/rubik/Rubik-LightItalic.ttf left in tree.
CONFLICT (modify/delete): ofl/rubik/Rubik-Light.ttf deleted in HEAD and modified in parent of dfd43510... rubik: v2.100 added with VTT hinting (#1076). Version parent of dfd43510... rubik: v2.100 added with VTT hinting (#1076) of ofl/rubik/Rubik-Light.ttf left in tree.
CONFLICT (modify/delete): ofl/rubik/Rubik-Italic.ttf deleted in HEAD and modified in parent of dfd43510... rubik: v2.100 added with VTT hinting (#1076). Version parent of dfd43510... rubik: v2.100 added with VTT hinting (#1076) of ofl/rubik/Rubik-Italic.ttf left in tree.
CONFLICT (modify/delete): ofl/rubik/Rubik-BoldItalic.ttf deleted in HEAD and modified in parent of dfd43510... rubik: v2.100 added with VTT hinting (#1076). Version parent of dfd43510... rubik: v2.100 added with VTT hinting (#1076) of ofl/rubik/Rubik-BoldItalic.ttf left in tree.
CONFLICT (modify/delete): ofl/rubik/Rubik-Bold.ttf deleted in HEAD and modified in parent of dfd43510... rubik: v2.100 added with VTT hinting (#1076). Version parent of dfd43510... rubik: v2.100 added with VTT hinting (#1076) of ofl/rubik/Rubik-Bold.ttf left in tree.
CONFLICT (modify/delete): ofl/rubik/Rubik-BlackItalic.ttf deleted in HEAD and modified in parent of dfd43510... rubik: v2.100 added with VTT hinting (#1076). Version parent of dfd43510... rubik: v2.100 added with VTT hinting (#1076) of ofl/rubik/Rubik-BlackItalic.ttf left in tree.
CONFLICT (modify/delete): ofl/rubik/Rubik-Black.ttf deleted in HEAD and modified in parent of dfd43510... rubik: v2.100 added with VTT hinting (#1076). Version parent of dfd43510... rubik: v2.100 added with VTT hinting (#1076) of ofl/rubik/Rubik-Black.ttf left in tree.
Auto-merging ofl/rubik/METADATA.pb
CONFLICT (content): Merge conflict in ofl/rubik/METADATA.pb
error: could not revert dfd43510... rubik: v2.100 added with VTT hinting (#1076)
hint: after resolving the conflicts, mark the corrected paths
hint: with 'git add <paths>' or 'git rm <paths>'
polygamma commented on 2020-07-23 09:05 (UTC)
It's not possible to build ttf-google-fonts-git as of now.
CONFLICT (modify/delete): ofl/rubik/Rubik-Black.ttf deleted in HEAD and modified in parent of dfd43510... rubik: v2.100 added with VTT hinting (#1076). Version parent of dfd43510... rubik: v2.100 added with VTT hinting (#1076) of ofl/rubik/Rubik-Black.ttf left in tree.
Auto-merging ofl/rubik/METADATA.pb
CONFLICT (content): Merge conflict in ofl/rubik/METADATA.pb
error: could not revert dfd43510... rubik: v2.100 added with VTT hinting (#1076)
hint: after resolving the conflicts, mark the corrected paths
hint: with 'git add <paths>' or 'git rm <paths>'
==> ERROR: A failure occurred in prepare().
Aborting...
dwheeler commented on 2020-07-15 19:06 (UTC) (edited on 2020-07-15 19:07 (UTC) by dwheeler)
Can you please add fontconfig to the makedepends array? It resolves the following error caused by fc-query being used in the PKGBUILD. Thanks!
==> Starting package()... /startdir/PKGBUILD: line 112: fc-query: command not found /startdir/PKGBUILD: line 115: omitted_font_families[]: bad array subscript fakeroot internal error #43: Identifier removed semop(2): encountered an error: Invalid argument ==> ERROR: Build failed, check /mnt/build/build
alerque commented on 2020-06-29 20:16 (UTC)
@polygamma All of the fonts with issues are all maintained by the same person who was active posting updates just a few days ago. There is hope they will be addressed soon. If not we'll file orphan requests so somebody else can fix them (I'd be happy to) in a bit, we we have to give them a bit of a shot first.
polygamma commented on 2020-06-29 20:00 (UTC)
@caleb I have already done so, before reporting it under this package. I'd still argue to do something about it, since those mentioned dependencies are maintained by other people, who knows how long it is going to take, until that stuff is fixed, if it ever happens.
alerque commented on 2020-06-29 19:52 (UTC)
@polygamma Please report that to the respective packages that actually have the bogus (legacy, now completely deprecated) dependency. This package can't fix that problem except by dropping the font packages. They should be fixed in the other packages.
polygamma commented on 2020-06-29 18:37 (UTC)
The package xorg-font-utils has been removed from the Arch repositories, this package cannot be built and installed anymore, since it depends on ttf-oswald, ttf-merriweather, ttf-quintessential, ttf-merriweather-sans and ttf-signika all of which depend on xorg-font-utils.
RubenKelevra commented on 2020-06-18 00:12 (UTC)
@andrewSC nobody has to pull the source every time. Yay caches the git from one build to the next one. :)
andrewSC commented on 2020-06-01 00:38 (UTC)
TheGoliath: Thanks for the contribution--looking at the upstream repo it doesn't seem the font itself has changed however I'll be watching issue #1137 and have enabled notifications.
Regarding the warning: inexact rename detection was skipped due to too many files.
message. I've disable merge rename detection until we get a change/answer from upstream.
Finally, since I know some of you don't like having to pull source every time to build this, I'm going to setup a repo to push built packages to and make it available to everyone. No ETA, however, it's on my shorter todo list as I think it'd benefit quite a number of people.
Thanks!
RubenKelevra commented on 2020-05-13 22:53 (UTC)
The bug is still happening:
==> Starting prepare()...
warning: inexact rename detection was skipped due to too many files.
warning: you may want to set your merge.renamelimit variable to at least 2070 and retry the command.
hrehfeld commented on 2020-04-11 09:50 (UTC)
==> Starting prepare()...
warning: inexact rename detection was skipped due to too many files.
warning: you may want to set your merge.renamelimit variable to at least 1930 and retry the command.
alerque commented on 2020-03-11 13:55 (UTC) (edited on 2020-03-11 13:59 (UTC) by alerque)
<strike>Please remove the depends on fontconfig and all the xorg-* entries, those are obsoleted by upstream hook changes in Arch. Also 'ttf-sil-fonts' is now a meta package, so providing that doesn't make any sense, and not all the fonts it depends on are listed here. Google fonts only has some of those fonts. I'll be updating the ttf-google-fonts-opinionated-git package with these changes shortly, if you'd like me to fix this at the same time please add me as a co-maintainer.</strike>
Edit: I see I already said most of that last month. Maybe just the suggestion to add me as a co-maintainer is new ;-)
andrewSC commented on 2020-02-17 14:32 (UTC)
Just a quick note that comments aren't falling on deaf ears--apologies for the radio silence. I've been tracking updating this package (along with several others) in my backlog and have put aside time tomorrow night to address concerns/issues. Thanks for understanding
alerque commented on 2020-02-17 07:57 (UTC)
Please remove the provides/conflicts for ttf-sil-fonts as this package does not currently supply all the same fonts. Also that is now a meta-package that depends on specific font packages, all built from their latest upstream releases. Even the fonts that are in google fonts are frequently out of date, but they are not all there. Listing provides/conflicts for specific packages that overlap would be fine.
HMPerson1 commented on 2020-02-14 03:21 (UTC) (edited on 2020-02-14 03:27 (UTC) by HMPerson1)
I get the following error when trying to install:
error: failed to commit transaction (conflicting files)
ttf-google-fonts-git: /usr/share/fonts/caladea/Caladea-Bold.ttf exists in filesystem (owned by ttf-caladea)
ttf-google-fonts-git: /usr/share/fonts/caladea/Caladea-BoldItalic.ttf exists in filesystem (owned by ttf-caladea)
ttf-google-fonts-git: /usr/share/fonts/caladea/Caladea-Italic.ttf exists in filesystem (owned by ttf-caladea)
ttf-google-fonts-git: /usr/share/fonts/caladea/Caladea-Regular.ttf exists in filesystem (owned by ttf-caladea)
It looks like Caladea was recently added to Google Fonts and ttf-caladea exists in [extra]:
FirstAirBender commented on 2019-12-21 23:40 (UTC) (edited on 2019-12-21 23:41 (UTC) by FirstAirBender)
I don't know how, but you need to make the dependencies, ttf-merriweather-sans
and ttf-merriweather
, mutually exclusive.
Attempting to install this package while choosing to use the ttf-merriweather
provided by ttf-google-fonts-typewolf
, results in an installation error because ttf-merriweather
in ttf-google-fonts-typewolf
actually installs the MerriweatherSans
fonts.
andrewSC commented on 2019-10-09 03:06 (UTC)
es20490446e, Juma7C9: Just pushed a change up where I added a prepare for reverting the offending Rubik commit as well as pulling adobeblank out entirely per the suggestion. Thanks! es20490446e, with #2, I still get an error relating to the zcool-xiaowei font and can confirm both through the git history as well as running fc-query -f '%{family[0]|downcase|translate( ,-)}\n' ZCOOLXiaoWei-Regular.ttf
that we're still seeing "站酷小薇体" as the resultant text. We'll want to keep the last two mv
lines for the time being. I'll need to think on #3.
es20490446e commented on 2019-10-08 10:43 (UTC) (edited on 2019-10-08 10:47 (UTC) by es20490446e)
Okay, these could be:
-
rm --recursive "${srcdir}/fonts/ofl/adobeblank"
-
Remove the Chinese characters work-around, as now all fonts names use Latin characters.
-
Do not perform "install" on the files. But "mv" them, then set permissions with "find -type d -exec chmod u=rwx,g=rx,o=rx {} \;" "find -type f -exec chmod u=rw,g=r,o=r {} \;". So you skip having to copy 1.5GB of data.
andrewSC commented on 2019-10-08 01:57 (UTC)
es20490446e: Yes I am and it's been on my todo for quite some time.. I'll make a priority to look at what needs to be changed tomorrow.
es20490446e commented on 2019-10-08 01:15 (UTC)
Are you still maintaining this package?
es20490446e commented on 2019-08-06 02:20 (UTC) (edited on 2019-08-09 22:45 (UTC) by es20490446e)
The conflict with noto-fonts-emoji can be fixed with:
rm --recursive "${srcdir}/fonts/ofl/adobeblank"
Reported the issue with that font upstream:
https://github.com/google/fonts/issues/2106
Feedback was that the font isn't meant to be installed.
Juma7C9 commented on 2019-05-12 19:47 (UTC) (edited on 2019-05-12 19:48 (UTC) by Juma7C9)
There is an issue with the Rubik Family, open upstream since 2017 link 1, which causes it not to be rendered at all (at least inside Firefox, example link 2).
In the meantime a workaround is to revert the incriminated commit link 3, for example adding to the PKGBUILD:
prepare() {
cd fonts
git revert -n dfd435109b718b1c5a8da7bd0872c751e2ae1820
}
es20490446e commented on 2019-04-09 21:32 (UTC)
Installing this package breaks emojis, the same ones provided by noto-fonts-emoji.
You can test with: https://getemoji.com/
ameed commented on 2019-03-09 22:13 (UTC)
I'm unable to install this with ttf-gentium-plus, since this package provides ttf-sil-fonts and ttf-gentium-plus conflicts with ttf-sil-fonts. But it doesn't seem like this package contains any of the SIL fonts anymore (except Gentium Basic, which isn't included in ttf-sil-fonts). Could that "provides" designation be removed?
fuan_k commented on 2019-01-24 23:11 (UTC)
@andrewSC: strange, I did not have ttf-google-fonts-typewolf installed, I only had that package listed as available from a custom added repository which I don't even use. So I disabled the repo in pacman.conf and it now installs fine. Thanks!
andrewSC commented on 2019-01-22 17:48 (UTC)
nightuser: Resolved the problem, thanks for pointing it out!
fuan_k: You'll need to uninstall ttf-google-fonts-typewolf in order to install this package. I've updated the conflicts array to reflect this.
fuan_k commented on 2019-01-17 13:24 (UTC) (edited on 2019-01-17 13:26 (UTC) by fuan_k)
I get an inner conflict error trying to install with yay (9.0.1):
:: Checking for conflicts...
:: Checking for inner conflicts...
==> Inner conflicts found:
-> ttf-google-fonts-typewolf Conflicts with: ttf-fira-sans, ttf-opensans, ttf-roboto
Unavoidable conflicts, aborting
nightuser commented on 2018-12-24 08:23 (UTC)
One of the new fonts doesn't have proper name in English:
: Can't translate pathname 'usr/share/fonts/站酷小薇体/' to UTF-8 : Can't translate pathname 'usr/share/fonts/站酷小薇体/ZCOOLXiaoWei-Regular.ttf' to UTF-8 : Can't translate pathname 'usr/share/licenses/ttf-google-fonts-git/LICENSE.站酷小薇体' to UTF-8
Perhaps we should rename it to something that uses latin alphabet (ZCOOLXiaoWei probably?).
10111 commented on 2018-10-20 20:12 (UTC)
Just installed the package. Build fails, because some files have new names (without special characters). Can confirm previous comments: Just remove the section from the PKGBUILD starting with:
"# NOTE: Since the nanum* and hanna Korean font families have special characters we need to change"
ncoder-2 commented on 2018-10-17 20:58 (UTC)
Should we tag this package as unmaintained?
+1 for zip and please fix the PKGBUILD issue with Korean fonts, it's literally commenting out 6 lines...
resetko commented on 2018-10-14 16:07 (UTC)
+1 for downloading as zip, and fix for Korean fonts related problem
theorangeone commented on 2018-10-10 19:48 (UTC)
Running git clone
to download this repo is incredibly slow, especially on a fairly poor network connection. I think this could be changed by downloading using the archive.zip
(as recommended in https://github.com/google/fonts#download-all-google-fonts), it'll download a lot faster (as proven by running locally on my machine). Not only will this download faster, but it's a lot less data, due to the fact it's not downloading the full repo history.
We could maintain version support by using git ls-remote
to build the version number.
andrewSC commented on 2018-10-01 13:21 (UTC)
JohnnyDeacon: Yes. There was a lull in activity upstream for several months but it looks like it's picked back up somewhat consistently. I'll be revisiting this package and making updates shortly.
JohnnyDeacon commented on 2018-10-01 02:04 (UTC)
Is this still maintained?
Meltea commented on 2018-08-26 12:46 (UTC)
Anybody getting this error?
==> Starting package()... mv: cannot stat ' ... pkg/ttf-google-fonts-git/usr/share/fonts/배달의민족-한나': No such file or directory
Fixed by removing the
# NOTE: Since the nanum* and hanna Korean font families have special characters we need to change # those folder names to prevent errors during package compression.
section
prash commented on 2018-06-05 07:32 (UTC) (edited on 2018-06-05 07:34 (UTC) by prash)
Google currently packages only 3 Indic fonts from the Lohit project: Bengali, Devanagari, and Tamil. However, the Lohit project supports many more Indic languages and fonts, viz. Assamese, Gujarati, Gurmukhi, Hindi, Kannada, Kashmiri, Konkani, Maithili, Malayalam, Marathi, Nepali, Odia, Oriya, Punjabi, Sindhi, Tamil-Classical, Telugu.
Could you please make the following changes to PKGBUILD:
- The last line of the package() function should have: find ${pkgdir} -iname "lohit" -delete
- Remove 'lohit-fonts' from the conflicts and provides arrays.
If you think it's important, you could add 'lohit-fonts' to your depends array. But if you don't, people who need it can install 'lohit-fonts' on their own, and not worry about conflicts with existing packages.
andrewSC commented on 2018-05-30 12:22 (UTC)
misc: No worries, my autobuilds were still showing successful (and I tested this build in a clean chroot just to be sure) so I just wanted to double check about things on your end. Thanks for sharing the diff!
misc commented on 2018-05-29 22:13 (UTC)
Ugh, apologies, I was too dumb to keep in mind that my fontconfig is actually from git, always newer (now at head from 05-25) than Extra's (03-15). Reverting for the build made the issue go away.
Since this will thus likely show for everyone with the next bump in Extra, here's the diff between build with fontconfig 03-15 (having the lines) and 05-25 (not having them): https://www.pastiebin.com/5b0dd0235c347
andrewSC commented on 2018-05-29 15:42 (UTC)
misc: What is the locale you have set on your machine? Can you provide links to pastes of the build output both with and without the korean lines commented out?
misc commented on 2018-05-20 18:55 (UTC)
Still can't build this package without removing the lines containing Hangul.
They don't appear to be required anymore anyway, the first font file is already named / installed as bm-hanna_ttf, the second nanummyeongjo, the third nanumgothic.
andrewSC commented on 2018-04-28 21:22 (UTC)
deathtrip: There's a good amount to read though, but my recommendation would be go to back through the commentary on the package for why things are the way they are. If that raises more questions, I'm happy to answer them here or via email.
deathtrip commented on 2018-04-24 15:08 (UTC)
Some fonts in the conflicts list, like ttf-anonymous-pro or the adobe fonts, are in the official repos. Shouldn't they also be removed from this package? Or is there a reason they are in conflict?
misc commented on 2018-04-13 13:53 (UTC) (edited on 2018-04-13 14:20 (UTC) by misc)
mv for the first file with Korean moonrunes fails with not found.
e: nvm, seems my repo clone got corrupted e2: Or not, not found in new one as well.
andrewSC commented on 2018-04-11 21:17 (UTC)
Hi all, terribly sorry for not giving this package some TLC sooner! I've removed the cwtex fonts from the bottom of the PKGBUILD and added the nanum family in its place to get the package back to functional.
If there's anything you would like to see or have any comments, I'm all ears :)
dbdbdb commented on 2018-04-11 19:36 (UTC) (edited on 2018-04-11 19:42 (UTC) by dbdbdb)
Since cwTeX-* fonts have already been removed in upstream (https://github.com/google/fonts/commit/98670058578c5d93f157347bccce91b23f6b245e) Do we still need the "mv's" for these fonts at PKGBUILD?
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!
Pinned Comments
thatgeek commented on 2017-11-17 03:56 (UTC)