Posted in Arch Linux

Infinality Fonts and Arch Linux

The use of Infinality fonts within Arch linux will greatly improve font rendering. But as mentioned in a few posts on the interwebs, the developers of the Infinality fonts pretty much fell off the face of the earth and no one has heard for him in quite a while. There is a way to get around this issue from what I have found so far. The following is how I got the Infinality fonts to install as there appeared to be public key issues since this packages in the repository have not been updated for a little while now. I will take you through the process that I found to work.

—===—===—===–

 

This part is from AJ Reissig who came up with the initial installation process within Arch:

 

To improve the fonts in Arch we first need to add some additional fonts. Add the following to the terminal:

sudo pacman -S ttf-bitstream-vera ttf-inconsolata ttf-ubuntu-font-family ttf-dejavu ttf-freefont ttf-linux-libertine ttf-liberation

yaourt -S ttf-ms-fonts ttf-vista-fonts monaco-linux-font ttf-qurancomplex-fonts

 

–Since monaco-linux-font no longer exists, change it to ttf-monaco

 

Next we will disable bitmat fonts, which are used as a fallback.

sudo ln -s /etc/fonts/conf.avail/70-no-bitmaps.conf /etc/fonts/conf.d

 

— I skipped adding the repos to the pacman.conf as the locations no longer exist

 

—===—===—===—

[kf4bzt@tim-pc ~]$ yaourt -S freetype2-infinality

 

Now, more than likely you will see a similar error like below. There is a way to fix it so that you can get on with the install process. :0)

 

==> Verifying source file signatures with gpg…
freetype-2.7.1.tar.bz2 … FAILED (unknown public key C1A60EACE707FDA5)
freetype-doc-2.7.1.tar.bz2 … FAILED (unknown public key C1A60EACE707FDA5)
ft2demos-2.7.1.tar.bz2 … FAILED (unknown public key C1A60EACE707FDA5)
==> ERROR: One or more PGP signatures could not be verified!
==> ERROR: Makepkg was unable to build freetype2-infinality.

 

—===—===—===—

Take the public key that is shown in the error and receive the key into the keyring. The -r switch is the same as –recv-keys which is also Equivalent to the –recv-keys switch in GnuPG.

 

[kf4bzt@tim-pc ~]$ sudo pacman-key -r C1A60EACE707FDA5
gpg: key C1A60EACE707FDA5: public key “Werner Lemberg <wl@gnu.org>” imported
gpg: marginals needed: 3 completes needed: 1 trust model: pgp
gpg: depth: 0 valid: 1 signed: 19 trust: 0-, 0q, 0n, 0m, 0f, 1u
gpg: depth: 1 valid: 19 signed: 69 trust: 1-, 0q, 0n, 18m, 0f, 0u
gpg: depth: 2 valid: 69 signed: 7 trust: 69-, 0q, 0n, 0m, 0f, 0u
gpg: next trustdb check due at 2017-09-07
gpg: Total number processed: 1
gpg: imported: 1
==> Updating trust database…
gpg: next trustdb check due at 2017-09-07

 

Once you have receive the keys in the keyring, go ahead and sign the keys using the -lsign-key switch as shown below.

 

[kf4bzt@tim-pc ~]$ sudo pacman-key –lsign-key C1A60EACE707FDA5
-> Locally signing key C1A60EACE707FDA5…
==> Updating trust database…
gpg: marginals needed: 3 completes needed: 1 trust model: pgp
gpg: depth: 0 valid: 1 signed: 20 trust: 0-, 0q, 0n, 0m, 0f, 1u
gpg: depth: 1 valid: 20 signed: 69 trust: 2-, 0q, 0n, 18m, 0f, 0u
gpg: depth: 2 valid: 69 signed: 7 trust: 69-, 0q, 0n, 0m, 0f, 0u
gpg: next trustdb check due at 2017-09-07
—===—===—===—

Now that you have added the keys successfully, have gpg list the keys and created a trusted key database.

 

[kf4bzt@tim-pc ~]$ gpg –list-keys

gpg: /home/kf4bzt/.gnupg/trustdb.gpg: trustdb created

 

—===—===—===—

Add the following line to the ~/.gnupg/gpg.conf file which tells gpg where your keyring lives.

 

[kf4bzt@tim-pc ~]$ vim ~/.gnupg/gpg.conf

add “keyring /etc/pacman.d/gnupg/pubring.gpg” to the end of the configuration file

 

—===—===—===—

After you have the keys good to go, start the install process once more as shown below.

 

[kf4bzt@tim-pc ~]$ yaourt -S freetype2-infinality

 

That is all there is to it. You will now have a working copy of the Infinality fonts on your Arch system giving you better font rendering quality than the stock fonts.

Leave a Reply

Your email address will not be published. Required fields are marked *