Package Details: ttf-ricty 4.1.1-3

Git Clone URL: (read-only, click to copy)
Package Base: ttf-ricty
Description: Japanese TrueType font for developers by mixing Inconsolata and Migu 1M.
Upstream URL:
Licenses: custom
Submitter: ginjiro
Maintainer: tomoaki (ny-a)
Last Packager: tomoaki
Votes: 14
Popularity: 0.099813
First Submitted: 2015-08-19 06:11
Last Updated: 2020-04-05 06:54

Latest Comments

1 2 Next › Last »

tomoaki commented on 2020-04-05 06:55

Hi ny-a, I think I fixed the problem you pointed out.

or I can co-maintain, if you wish. I would like to accept your kind offer!

ny-a commented on 2020-04-01 00:18

tomoaki, Thank you for updating package, but .SRCINFO is not updated. Could you update it?

or I can co-maintain, if you wish.

tomoaki commented on 2020-03-31 19:46

Hi, yu_izawa and ny-a. Thank you for pointing out that the package was broke. Sorry,yu_izawa. I didn't notice your message on 2019-10-21.

yu_izawa commented on 2020-03-30 07:09

Hi ny-a,

Thank you for your suggestion. I agreed with your opinion and turned off out-of-date flag.


ny-a commented on 2020-03-30 06:59

Is this package out-of-date? Indeed it's updated source-url to , but it's not out-of-date.

I think commenting it is more appropriate for these kind of problems.

yu_izawa commented on 2019-10-21 06:37

Hi tomoaki,

Building ttf-ricty is still failed now. It seems that a download URL for the ricty_generator is changed.

old: new:

Would you fix PKGBUILD script to solve this problem?


ginjiro commented on 2017-01-26 07:39

Hi colajam.
Sorry, I made a mistake in fixing the script.
Thanks report!

colajam commented on 2017-01-26 06:48


I got the following error.

==> Starting build()...
chmod: cannot access './': No such file or directory
==> ERROR: A failure occurred in build().

I think the script name in the build() should be ''.

ginjiro commented on 2017-01-26 04:07

Hi revel.
The source I specified was a beta release version.
So I modified source to version 4.1.0.
Thanks your report!

revel commented on 2017-01-24 03:58

It looks like sha1 hash is wrong, source file must have changed since the last update.