From: zimoun <zimon.toutoune@gmail.com>
To: Marius Bakke <mbakke@fastmail.com>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: [PATCH] gnu: fontconfig: Add replacement with font-dejavu instead of gs-fonts.
Date: Wed, 20 May 2020 23:03:01 +0200 [thread overview]
Message-ID: <CAJ3okZ3A7ko+8jUO4N4suGc56LhbUpgkX0je60OiMeWks5o1JA@mail.gmail.com> (raw)
In-Reply-To: <87ftbubtj2.fsf@devup.no>
On Wed, 20 May 2020 at 15:55, Marius Bakke <mbakke@fastmail.com> wrote:
> zimoun <zimon.toutoune@gmail.com> writes:
> > Apparently, there is different fonts on master and core-updates, if yes why?
>
> The only known difference since the core-updates merge is that
> applications using Pango (e.g. GTK+) no longer recognizes bitmap fonts.
>
> https://gitlab.gnome.org/GNOME/pango/issues/386
Thank you for the pointer but I think it is another issue.
> > I mean, on my machine -- Guix on the top of Debian with font-dejavu
> > installed -- why does commit 4bdf4182fe (core-update merge) not
> > display correctly and the parent commit c81457a588 too but the other
> > parent commit 23a59b180b displays nicely?
>
> Leo reported problems with fonts on Debian in
> <https://issues.guix.gnu.org/issue/41132>, but said that fonts installed
> with Guix still worked. I don't know what could cause it to fail on
> your system.
Thank for the pointer, it seems the same issue. But I am not sure
because I am using the font from Guix.
Well, I have font-dejavu-2.37 and fontconfig-2.13.1 installed in
~/.guix-profile from Guix e98689f.
When I run
guix pull --commit=4bdf4182fe -p /tmp/bad
then
display /tmp/bad/share/info/images/bootstrap-graph.png
there is an issue. Note that 'imagemagick' is installed in
~/.guix-profile using the same commit above.
The commit 4bdf4182fe is the commit of merge. If I pull from the
(left) parent commit, i.e., the commit c81457a588,
guix pull --commit=c81457a588 -p /tmp/left
then
display /tmp/right/share/info/images/bootstrap-graph.png
displays nicely and the font is correct. However, if I pull form the
(right) parent commit, i.e., the commit 23a59b180b,
guix pull --commit=23a59b180b -p /tmp/right
then
display /tmp/right/share/info/images/bootstrap-graph.png
displays wrongly. Well, I have changed nothing, considering the
fonts. And the only difference is commit from "master" vs from
"core-updates". And as I explained [1], it always happens when
core-updates is merged.
BTW, let checkout 4bdf4182fe (git worktree add -b) and run ./bootstrap
&& ./configure --localstatedir=/var/ && make -j4 in "guix environment
--pure guix". Then the image doc/images/bootstrap-graph.png displays
nicely. Idem for the two other commits. It is the same when building
using the -C option.
However, if I pull from this fresh Guix using,
./pre-env-inst guix pull --branch=merge --url=$PWD -p /tmp/merge
then outside the environment, using the very same imagemagick,
display /tmp/merge/share/info/images/bootstrap-graph.png
displays wrongly. Same for the (right) commit 23a59b180b. But it is
not the case for the left commit c81457a588. And as I noted [1] this
happens with all the merges of core-updates.
Something is different between 23a59b180b and c81457a588 in regard to
the font, otherwise the exact same procedure would end to the same
result using the same machine. The question is: does someone
reproduce the same behaviour on Guix System? on other than Debian
foreign distro?
[1] http://issues.guix.gnu.org/issue/41282
All the best,
simon
next prev parent reply other threads:[~2020-05-20 21:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-17 14:50 [PATCH] gnu: fontconfig: Add replacement with font-dejavu instead of gs-fonts Marius Bakke
2020-05-19 15:50 ` Leo Famulari
2020-05-20 11:28 ` Marius Bakke
2020-05-20 22:59 ` Leo Famulari
2020-05-20 22:00 ` Marius Bakke
2020-05-20 12:06 ` zimoun
2020-05-20 13:55 ` Marius Bakke
2020-05-20 21:03 ` zimoun [this message]
2020-05-20 21:41 ` Marius Bakke
2020-05-20 23:35 ` zimoun
2020-05-21 12:46 ` Marius Bakke
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=CAJ3okZ3A7ko+8jUO4N4suGc56LhbUpgkX0je60OiMeWks5o1JA@mail.gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=guix-devel@gnu.org \
--cc=mbakke@fastmail.com \
/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.