public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Adam Williamson <awilliam@redhat.com>
To: git-commits@fedoraproject.org
Subject: [flatpaks/flatpak-runtime] f45: Add google-noto-serif-vf-fonts to runtime
Date: Fri, 11 Sep 2026 14:42:11 GMT	[thread overview]
Message-ID: <178913773160.1.2885710987417741197.flatpaks-flatpak-runtime-f6b526b64f34@fedoraproject.org> (raw)

            A new commit has been pushed.

            Repo   : flatpaks/flatpak-runtime
            Branch : f45
            Commit : f6b526b64f34fbdd00f86e68e1d81f36a1c79844
            Author : Adam Williamson <awilliam@redhat.com>
            Date   : 2022-09-17T15:39:15+02:00
            Stats  : +4/-0 in 1 file(s)
            URL    : https://src.fedoraproject.org/flatpaks/flatpak-runtime/c/f6b526b64f34fbdd00f86e68e1d81f36a1c79844?branch=f45

            Log:
            Add google-noto-serif-vf-fonts to runtime

See https://github.com/fedora-silverblue/issue-tracker/issues/305
@mcatanzaro and I believe that this package not being in the
runtime, combined with some weirdness to do with fontconfig
caches, is likely the cause of help not working in various app
flatpaks. The weirdness is being poked at, but it seems in any
case a good idea to include Fedora's official default serif font
in the runtime.

Signed-off-by: Adam Williamson <awilliam@redhat.com>

---
diff --git a/flatpak-runtime.yaml b/flatpak-runtime.yaml
index e9a6f2f..bc6c1cb 100644
--- a/flatpak-runtime.yaml
+++ b/flatpak-runtime.yaml
@@ -146,6 +146,7 @@ data:
       - google-carlito-fonts
       - google-noto-fonts-common
       - google-noto-sans-vf-fonts
+      - google-noto-serif-vf-fonts
       - gpgme
       - gpgmepp
       - graphene
@@ -750,6 +751,7 @@ data:
       - google-carlito-fonts
       - google-noto-fonts-common
       - google-noto-sans-vf-fonts
+      - google-noto-serif-vf-fonts
       - gpgme
       - gpgmepp
       - graphene
@@ -1456,6 +1458,7 @@ data:
       - google-droid-sans-fonts
       - google-noto-fonts-common
       - google-noto-sans-vf-fonts
+      - google-noto-serif-vf-fonts
       - gperf
       - gpgme
       - gpgme-devel
@@ -2805,6 +2808,7 @@ data:
       - google-droid-sans-fonts
       - google-noto-fonts-common
       - google-noto-sans-vf-fonts
+      - google-noto-serif-vf-fonts
       - gperf
       - gpgme
       - gpgme-devel

                 reply	other threads:[~2026-09-11 14:42 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=178913773160.1.2885710987417741197.flatpaks-flatpak-runtime-f6b526b64f34@fedoraproject.org \
    --to=awilliam@redhat.com \
    --cc=git-commits@fedoraproject.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox