From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Diego Nicola Barbato <dnbarbato@posteo.de>
Cc: "Ludovic Courtès" <ludo@gnu.org>, 33080-done@debbugs.gnu.org
Subject: bug#33080: [PATCH] gnu: Add inferno.
Date: Tue, 13 Jul 2021 08:51:35 -0400 [thread overview]
Message-ID: <87mtqqs7fs.fsf_-_@gmail.com> (raw)
In-Reply-To: <87a7mazit8.fsf@GlaDOS.home> (Diego Nicola Barbato's message of "Thu, 15 Nov 2018 12:22:43 +0100")
Hello Diego,
Diego Nicola Barbato <dnbarbato@posteo.de> writes:
> Hello Ludo,
>
> ludo@gnu.org (Ludovic Courtès) writes:
>
>> Hi Diego,
>>
>> Sorry for the late reply.
>>
>> Diego Nicola Barbato <dnbarbato@posteo.de> skribis:
>>
>>> This patch adds inferno as discussed here:
>>> https://lists.gnu.org/archive/html/guix-devel/2018-10/msg00031.html
>>
>> In that thread we discussed the font issue, and I’m unsure if it was
>> resolved:
>>
>> <https://lists.gnu.org/archive/html/guix-devel/2018-10/msg00265.html>
>>
>> Is everything “known good” with this version of the patch?
>
> Unfortunately it is not. As you suggested, I wrote to the
> GNU/Linux-libre mailing list asking for advice on the font issues [1]
> and the licensing issues [2]. The only reply I got so far is not very
> encouraging. Maybe it is best to put this on hold until I receive more
> information?
>
[...]
> If it is OK I will wait for the font and licensing issues to be resolved
> before I update the patch, since, as of now, it looks to me like Inferno
> can not be included in an FSDG distro.
Sadly, it seems a blocker that there are no sources to rebuild the fonts
from.
We'll have to do without them it seems.
Closing.
Maxim
prev parent reply other threads:[~2021-07-13 12:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-17 21:25 [bug#33080] [PATCH] gnu: Add inferno Diego Nicola Barbato
2018-11-10 18:05 ` Ludovic Courtès
2018-11-15 11:22 ` Diego Nicola Barbato
2018-11-15 11:51 ` Ludovic Courtès
2021-07-13 12:51 ` Maxim Cournoyer [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mtqqs7fs.fsf_-_@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=33080-done@debbugs.gnu.org \
--cc=dnbarbato@posteo.de \
--cc=ludo@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.