Package Base Details: freetype2-infinality

Git Clone URL: https://aur.archlinux.org/freetype2-infinality.git (read-only)
Submitter: None
Maintainer: SolarAquarion
Last Packager: SolarAquarion
Votes: 470
Popularity: 0.605933
First Submitted: 2010-07-14 15:27
Last Updated: 2019-03-19 11:07

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 ... Next › Last »

Ralf_Mardorf commented on 2017-01-14 19:52

Read the comments!

This was several times explained by the comments.

Read the Wiki!

validpgpkeys is basic PKGBUILD knowledge, let alone that this topic was part of the latest checksum discussion.

Aco commented on 2017-01-14 18:30

what is wrong..

Wats 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.

dobo commented on 2017-01-13 14:00

I will update tonight. I was quite busy last days.

ebrilo commented on 2017-01-12 18:25

>I don't know what you are discussing

We're discussing newely released freetype2 v. 2.7.1, wich is needed by updated harfbuzz.

Freetype2 v. 2.7.1 haven't yet been patched with infinality by it's maintainer (and looks like it will never be), plus original infinality site is long dead.

So some good guys yesterday did the maintainer's job here: https://github.com/archfan/infinality_bundle/

And we're currently talking about how to get this patched freetype2 to AUR in order to make the world perfect again.

Ralf_Mardorf commented on 2017-01-12 17:41

I don't know what you are discussing. Assuming it should be the harfbuzz issue, consider just to rebuild harfbuzz

$ sudo abs
$ sudo pacman -Syu
$ cp -ai /var/abs/extra/harfbuzz/ /tmp/
$ cd /tmp/harfbuzz/
$ nano PKGBUILD
$ makepkg -si

does the trick.

With nano I edited the pkgrel, but even this isn't required.

[rocketmouse@archlinux ~]$ pacman -Si harfbuzz{,-icu} | grep Ver
Version : 1.4.1-1
Version : 1.4.1-1
[rocketmouse@archlinux ~]$ pacman -Q harfbuzz{,-icu}
harfbuzz 1.4.1-2
harfbuzz-icu 1.4.1-2

Ok, now I see, official repositories provide 2.7.1 instead of 2.7, so it's not in sync anymore with the package from extra.

ebrilo commented on 2017-01-12 17:23

>Ask dobo :)

Looks like he's not going to do anything with it since 2016-11-29.. Orphan mb?

kokoko3k commented on 2017-01-12 11:51

> Will it be presented in aur?
Ask dobo :)

ebrilo commented on 2017-01-11 15:11

>I think we managed to make it work with 2.7.1
>Changes should stabilize soon, please check:
>https://github.com/archfan/infinality_bundle/

I've just installed it (from your github link) - works just fine. I'd say, it works perfectly. Will it be presented in aur? Just to keep it in order, you know..

And many thanks, man! I've already started becoming desperate breaking my eyes with soapy, smoky glyphs, rendered with standard freetype.

kokoko3k commented on 2017-01-11 11:53

I think we managed to make it work with 2.7.1
Changes should stabilize soon, please check:
https://github.com/archfan/infinality_bundle/

Bunker commented on 2017-01-09 12:09

Ralf:

Thank you for the reply. Now I do have the problem that's listed below by nTia89. So the I'm supposed to do the downgrade.

However, if you get p*ssed off everytime some user, that maybe like me is rather new and asks a question that seems stupid to you, you should maybe ask if maintaining a package is something for you.

To explain I did skim the comments, but the one you are referring to, doesn't show until you choose show all comments.

I knew I had to import a key, but I did not know that I have to use the key that's shown as failed to import. That is my mistake I agree.