All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Thomas Schmitt" <scdbackup@gmx.net>
To: grub-devel@gnu.org
Subject: Re: make check: grub-mkrescue fails missing unicode.pf2. Leftovers in /tmp
Date: Wed, 15 Feb 2023 09:51:18 +0100	[thread overview]
Message-ID: <20883390706746626444@scdbackup.webframe.org> (raw)
In-Reply-To: <20230214110050.7c9a0f93@crass-HP-ZBook-15-G2>

Hi,

Glenn Washburn wrote:
> IIRC, xfonts-unifont is pulled in by the unifont package on Debian, but
> it is the one with the files you need. No, its not documented, but then
> not every single debian package name needed is documented because the
> documentation is partially distribution agnostic. If it were documented
> it would be in ./INSTALL, which does talk about needing unifonts. If
> you'd like to modify that file to help other Debian users, I'm
> supportive.

Unicode is mentioned two times in INSTALL.
Once for building "GRUB's graphical terminal (gfxterm)", once as
"Platform-agnostic tools and data".

There is also a section "Debian named packages required mostly for the
full suite of filesystem testing" which could host the name of the needed
package. Although it is not about filesystems the mentioning could be
justified by the word "mostly" in the headline.
Or it could be mentioned as own point one level higher under
"Prerequisites for make-check".


But actually the lack of unifont did not hamper building GRUB from git.
So i would expect that this tolerance is somewhat reflected by the tests.

How about putting in tests/grub_func_test.in a test for the existence of
/boot/grub/fonts/unicode.pf2 with an informative error message if it is
missing ?
Since we know that xorriso under grub-mkrescue will cause early failure if
the file is missing, there is no use in running grub-shell with the demand
for unicode.pf2.

I see that grub_func_test.in already has provisions to declare
"Functional test failure". Maybe the new code path could join that.
Or it could be declared as skipped. (I still have to find out how to
cause a SKIP message in the test log.)


Have a nice day :)

Thomas



  reply	other threads:[~2023-02-15  8:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-10 11:10 make check: grub-mkrescue fails missing unicode.pf2. Leftovers in /tmp Thomas Schmitt
2023-02-12 23:09 ` Vladimir 'phcoder' Serbinenko
2023-02-13  8:53   ` Thomas Schmitt
2023-02-13 12:36     ` Thomas Schmitt
2023-02-13 22:00     ` Glenn Washburn
2023-02-14  9:10       ` Thomas Schmitt
2023-02-14 17:00         ` Glenn Washburn
2023-02-15  8:51           ` Thomas Schmitt [this message]
2023-02-15  9:55             ` Thomas Schmitt
2023-02-16  6:16             ` Glenn Washburn
2023-02-13 22:14 ` Glenn Washburn
2023-02-13 22:35   ` Glenn Washburn

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=20883390706746626444@scdbackup.webframe.org \
    --to=scdbackup@gmx.net \
    --cc=grub-devel@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.
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.