Package Details: ttf-fantasque-sans-git 1.7.2.r184.b9c399d-1

Git Clone URL: (read-only, click to copy)
Package Base: ttf-fantasque-sans-git
Description: A font family with a great monospaced variant for programmers.
Upstream URL:
Licenses: SIL OPEN FONT LICENSE Version 1.1
Conflicts: ttf-fantasque-sans-mono
Submitter: parantapa
Maintainer: None
Last Packager: parantapa
Votes: 21
Popularity: 0.000002
First Submitted: 2014-01-20 04:57 (UTC)
Last Updated: 2019-03-25 13:39 (UTC)

Latest Comments

ffmin commented on 2019-03-25 04:04 (UTC)

Please add zip to the make dependencies. I didn't realize that I didn't have it installed and the installation failed with a command not found.

parantapa commented on 2017-11-07 13:57 (UTC)

@Ataraxy thanks for info. I have added the conflict section. I have also added a 2to3 conversion of It should compile now.

Ataraxy commented on 2017-11-04 03:42 (UTC)

Would you add that conflict be added to the PKGBUILD? Currently, in building, I get: ==> Starting build()... mkdir -p Variants Scripts/validate-font "Sources/FantasqueSansMono-Bold.sfdir" Validating FantasqueSansMono-Bold... Scripts/generate-font-variants "Sources/FantasqueSansMono-Bold.sfdir" Variants Generating FantasqueSansMono-Bold variants... Traceback (most recent call last): File "/home/ravi/.cache/pacaur/ttf-fantasque-sans-git/src/repo/Scripts/", line 55, in <module> build_batch(output, sys.argv[3], int(sys.argv[1]), int(sys.argv[2])) File "/home/var/ravi/.cache/pacaur/ttf-fantasque-sans-git/src/repo/Scripts/", line 126, in build_batch _build(dstdir, font, list(permutations())[node_number::total_nodes]) File "/home/var/ravi/.cache/pacaur/ttf-fantasque-sans-git/src/repo/Scripts/", line 72, in permutations for i in xrange(bitmap_max): NameError: name 'xrange' is not defined make: *** [Makefile:16: Variants/Normal/TTF/FantasqueSansMono-Bold.ttf] Error 1 ==> ERROR: A failure occurred in build(). Aborting... :: sfnt2woff is now an orphan package :: ttf2eot is now an orphan package :: ttfautohint is now an orphan package :: woff2-git is now an orphan package :: failed to build ttf-fantasque-sans-git package(s)

parantapa commented on 2017-11-03 14:41 (UTC)

@Ataraxy It does conflict with ttf-fantasque-sans-mono. Both install TTF files for the same font.

Ataraxy commented on 2017-11-03 14:30 (UTC)

Does this conflict with fantasque-sans-mono?

parantapa commented on 2016-01-18 06:45 (UTC)

Hi @zsrkmyn It seems woff2-git is available on AUR. I have added it to the make-depends array. Things should start working again.

zsrkmyn commented on 2016-01-17 16:50 (UTC)

The PKGBUILD seems to be out-of-date, which lacks of dependence `woff2`[1]. And woff2 is currently not available in AUR. [1]

parantapa commented on 2015-05-11 06:43 (UTC)

Hi @vogelchr An issue has been reported upstream. Hopefully it will be fixed soon. I don't think changing the PKGBUILD for this is a good idea. Things will break as soon as upstream releases a fix.

vogelchr commented on 2015-05-10 10:45 (UTC)

Currently does not build (2015-05-10). ==> Starting build()... mkdir -p OTF Webfonts ./validate-generate "FantasqueSansMono-BoldItalic" Generating FantasqueSansMono-BoldItalic... Copyright (c) 2000-2014 by George Williams. See AUTHORS for Contributors. License GPLv3+: GNU GPL version 3 or later <> with many parts BSD <>. Please read LICENSE. Based on sources from 23:39 TAHT 6-May-2015-ML-D. Based on source from git with hash: File "<stdin>", line 6 print font.fontname ^ SyntaxError: Missing parentheses in call to 'print' Error in FantasqueSansMono-BoldItalic. If works if one changes the print statements in "validate-generate.tmp", for examply by changing the build() function in the PKGBUILD. build() { cd "$srcdir/repo" sed 's/^print \(.*\)/print(\1)/' <validate-generate >validate-generate.tmp mv validate-generate.tmp validate-generate chmod 755 validate-generate make }

parantapa commented on 2014-07-27 07:18 (UTC)

Hi @nomadpenguin The problem has been fixed upstream. So there shouldn't be any need for the workaround.

parantapa commented on 2014-07-27 07:06 (UTC)

Hi @nomadpenguin It seems that a bug was introduced in the upstream since version 46e79a7. I have opened an issue to report it. Since this is a git based package, the problem should be automatically fixed here once it is fixed upstream. For now, a workaround would be to replace the line cd "$srcdir/repo" with cd "$srcdir/repo" ; git checkout 89c1267 in the pkgver and build functions in the PKGBUILD file before doing a makepkg.

nomadpenguin commented on 2014-07-27 00:45 (UTC)

When I try to build it I get this error.

manuel commented on 2014-01-20 13:00 (UTC)

@parantapa: Thanks for what you do :)

parantapa commented on 2014-01-20 05:12 (UTC)

@manuel: Thanks for the update I have created a new package ttf-fantasque-sans-git. I have also sent a request that this package be merged into the new one, so that there is no future confusion.

manuel commented on 2014-01-19 15:27 (UTC)

The font has been renamed to fantasque-sans due to the same name being already in use. The repository is now

parantapa commented on 2014-01-02 15:38 (UTC)

@mar77i Thanks for the update. Added fontforge, ttfautohint, sfnt2woff, and ttf2eot to makedepends array, instead of depends array as you asked. As I understand you dont need them to use the ttf files, only to build them.

mar77i commented on 2014-01-02 13:37 (UTC)

there's no build() function. the git repo doesn't deliver the built ttf any longer. please add the build function as follows, as well as ttfautohint, sfnt2woff, ttf2eot to the depends array. build() { cd "$srcdir/cosmic-sans-neue" make } cheers! mar77i

parantapa commented on 2013-12-07 13:51 (UTC)

I think, you mean parse package version into pkgver and use hash in pkgrel. I think epoch is not used for this purpose. Anyway, I looked into a number of -git packages at aur and it seems the current way is the way to go. However, suggestions are always welcome.

bb010g commented on 2013-12-05 14:32 (UTC)

You could keep the version at the hash and parse the for version and use that for epoch.

parantapa commented on 2013-12-05 05:33 (UTC)

Epoch changes when version number format is changed. Since this pulls down directly from git repo, it is not really at 1.3.1, but what ever stage the master branch is at. I tried a couple of different version number formats and so had to change the epoch value. Currently i am using the one given here (the third one, since the repo doesn't seem to use tags)

bb010g commented on 2013-12-04 23:51 (UTC)

How is it at epoch 2? Shouldn't it be 1.3.1?