Package Details: ttf-unifont 15.1.05-2

Git Clone URL: (read-only, click to copy)
Package Base: ttf-unifont
Description: TrueType version of the GNU Unifont
Upstream URL:
Keywords: font unicode
Licenses: OFL-1.1 OR GPL-2.0-or-later WITH Font-exception-2.0
Provides: emoji-font
Submitter: None
Maintainer: davidmcinnis (nl6720, txtsd, zkiroel, jfcandidofilho, coolsidd, adsun)
Last Packager: txtsd
Votes: 120
Popularity: 0.79
First Submitted: 2010-01-15 11:57 (UTC)
Last Updated: 2024-05-21 16:12 (UTC)

Dependencies (1)

Required by (14)

Sources (2)

Latest Comments

1 2 3 4 5 Next › Last »

txtsd commented on 2023-11-09 05:23 (UTC)

@tfl5034 Yes, they haven't changed their key in ages. I emailed unifoundry about it but they don't seem to care.

tfl5034 commented on 2023-11-09 05:21 (UTC)

I get a warning that the pgp key is expired.

txtsd commented on 2023-09-14 13:04 (UTC)

Updated the PKGBUILD. It should build and install correctly now.

Tpaefawzen commented on 2023-09-14 05:55 (UTC)

I found NEWS saying:

2023-09-12: Release 15.1.01
   * OpenType fonts are now built by default, replacing TrueType fonts.
     TrueType fonts can be built manually by invoking "make truetype"
     in the font directory.

Then tried this:

build() {
    cd "${srcdir}/unifont-${pkgver}/font"
    make truetype

And I got this error message from Makefile:

make[1]: fontforge: No such file or directory
make[1]: *** [Makefile:77: ttf] Error 127

The new (15.1.01-1) version seems to require fontforge to build.

PolarianDev commented on 2023-09-12 23:18 (UTC)

I believe this is the same error as the comment below, but just in case here is my build output which is failing:

==> Making package: ttf-unifont 15.1.01-1 (Wed 13 Sep 2023 00:15:55 BST)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Found unifont-15.1.01.tar.gz
  -> Found unifont-15.1.01.tar.gz.sig
==> Validating source files with sha256sums...
    unifont-15.1.01.tar.gz ... Passed
    unifont-15.1.01.tar.gz.sig ... Skipped
==> Verifying source file signatures with gpg...
    unifont-15.1.01.tar.gz ... Passed
==> Removing existing $srcdir/ directory...
==> Extracting sources...
  -> Extracting unifont-15.1.01.tar.gz with bsdtar
==> Sources are ready.
==> Making package: ttf-unifont 15.1.01-1 (Wed 13 Sep 2023 00:15:56 BST)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> WARNING: Using existing $srcdir/ tree
==> Entering fakeroot environment...
==> Starting package()...
install: cannot stat 'unifont-15.1.01/font/precompiled/unifont-15.1.01.ttf': No such file or directory
==> ERROR: A failure occurred in package().


anarsoul commented on 2023-09-12 22:23 (UTC)

The build fails since doesn't have precompiled TTF

1ace commented on 2023-06-07 17:27 (UTC)

@nl6720: indeed, but I worked around it by just downloading the files myself as I do not like gambling :P

nl6720 commented on 2023-06-06 09:29 (UTC)

@1ace, is not a single server, try again and you may get a better server.

1ace commented on 2023-06-06 09:14 (UTC)

==> Retrieving sources...
  -> Downloading unifont-15.0.06.tar.gz...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
curl: (35) OpenSSL/3.0.8: error:0A000152:SSL routines::unsafe legacy renegotiation disabled
==> ERROR: Failure while downloading

Looks like the server behind is severely out of date, to the point that curl doesn't support it anymore. I'm not sure if there's anything that can be done in the PKGBUILD to work around that?

Morn commented on 2023-05-22 13:33 (UTC)

I have switched to otf-unifont on my system, so I am disowning the TTF package now. Upstream will stop distributing prebuilt TTF files later this year, although you can still build them from source.