[opensuse-packaging] How to require at least one default font?
Hi, Because I run into "Trace/breakpoint trap" crashes with Python packages using PyQt5 a lot lately, I asked a question at [1] and found out that the culprit is a missing default font for the bundled chromium in libqt5-webengine. What is the best way to require a default font and into which package should the requirement declaration go? Obvious choices would be libqt5-webengine or python-pytest-qt. For the latter it wouldn't matter much which font to choose, but installing a default with libqt5-webengine or fontconfig has an effect on a lot of systems. Which font package would be the right one? Or is there a meta package? Cheers, Ben [1] https://github.com/pytest-dev/pytest-qt/issues/317 -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
Hi, Am 16.09.20 um 16:41 schrieb Ben Greiner:
Hi,
Because I run into "Trace/breakpoint trap" crashes with Python packages using PyQt5 a lot lately, I asked a question at [1] and found out that the culprit is a missing default font for the bundled chromium in libqt5-webengine.
What is the best way to require a default font and into which package should the requirement declaration go? Obvious choices would be libqt5-webengine or python-pytest-qt. For the latter it wouldn't matter much which font to choose, but installing a default with libqt5-webengine or fontconfig has an effect on a lot of systems. Which font package would be the right one? Or is there a meta package?
Cheers, Ben
Since there was no reply yet, I decided to require free-ttf-fonts in pytest-qt [2]. We should be able to observe the change from "failed" to "succeeded" for python-spyder-notebook [3] as soon as python3-pytest-qt-3.3.0-2 is in the Tumbleweed image. Cheers, Ben [2] https://build.opensuse.org/request/show/837379 [3] https://build.opensuse.org/package/show/devel:languages:python:numeric/pytho... -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
Hi Ben, On Sat, 2020-09-26 at 10:03 +0200, Ben Greiner wrote:
Hi,
Am 16.09.20 um 16:41 schrieb Ben Greiner:
Which font package would be the right one? Or is there a meta package?
Cheers, Ben
Since there was no reply yet, I decided to require free-ttf-fonts in pytest-qt [2]. We should be able to observe the change from "failed" to "succeeded" for python-spyder-notebook [3] as soon as python3-pytest-qt-3.3.0-2 is in the Tumbleweed image.
That's probably not the set of fonts you are looking for, since its summary says: "Free TrueType *Art* Fonts". They are more suitable for posters and artwork rather than as generic fonts. For more generic fonts you can try "font(:lang=en)" which would pull in a default font for the en locale (on TW that seems to be cantarell) or try one of the free gnu fonts "font(freesans)" or "font(freeserif)". Hope that helps (albeit belatedly). Cheers, -- Atri Bhattacharya Sat 26 Sep 12:39:42 CEST 2020 Sent from openSUSE Tumbleweed on my laptop. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
Am 26.09.20 um 12:47 schrieb Atri Bhattacharya:
Which font package would be the right one? Or is there a meta package?
Cheers, Ben
[1] https://github.com/pytest-dev/pytest-qt/issues/317 For more generic fonts you can try "font(:lang=en)" which would pull in a default font for the en locale (on TW that seems to be cantarell) or
Am 16.09.20 um 16:41 schrieb Ben Greiner: try one of the free gnu fonts "font(freesans)" or "font(freeserif)".
Hope that helps (albeit belatedly). Cheers,
Thanks! the font(:lang=en) specification looks like it is perfect to directly include it into libqt5-qtwebengine. Ben -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
Hi again, Am 26.09.20 um 12:56 schrieb Ben Greiner:
Am 26.09.20 um 12:47 schrieb Atri Bhattacharya:
For more generic fonts you can try "font(:lang=en)"
Thanks! the font(:lang=en) specification looks like it is perfect to directly include it into libqt5-qtwebengine.
Ben
Meh, that just creates "unresolvable: have choice ..." with a large list of possible font choices for all packages depending on libqt5-qtwebengine. We cannot demand to set a `Prefer:` for every project. Or `#!BuildIgnore` for every package. So back to `BuildRequires:` an arbitrary font package. `free-ttf-fonts` may be not the perfect choice, but nobody sees the content produced during unit testing anyway. Ben -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
Am 27.09.20 um 19:22 schrieb Ben Greiner:
Am 26.09.20 um 12:56 schrieb Ben Greiner:
Thanks! the font(:lang=en) specification looks like it is perfect to directly include it into libqt5-qtwebengine.
Meh, that just creates "unresolvable: have choice ..." with a large list of possible font choices for all packages depending on libqt5-qtwebengine. We cannot demand to set a `Prefer:` for every project. Or `#!BuildIgnore` for every package.
This would "just" need to be done for all "Top Level" projects, e.g. openSUSE:Factory, openSUSE:Leap:15.2, ... and would be inherited from there.
So back to `BuildRequires:` an arbitrary font package. `free-ttf-fonts` may be not the perfect choice, but nobody sees the content produced during unit testing anyway.
If it is just needed for unit tests, then requiring a specific font might get you more deterministic results anyway. -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On Sun, 2020-09-27 at 21:54 +0200, Stefan Seyfried wrote:
Am 27.09.20 um 19:22 schrieb Ben Greiner:
Thanks! the font(:lang=en) specification looks like it is perfect to directly include it into libqt5-qtwebengine. Meh, that just creates "unresolvable: have choice ..." with a large
Am 26.09.20 um 12:56 schrieb Ben Greiner: list of possible font choices for all packages depending on libqt5-qtwebengine. We cannot demand to set a `Prefer:` for every project. Or `#!BuildIgnore` for every package.
This would "just" need to be done for all "Top Level" projects, e.g. openSUSE:Factory, openSUSE:Leap:15.2, ... and would be inherited from there.
I would suggest that we either do this at the top-level projects or, alternatively, create new meta-packages called "default-serif-font", "default-sans-font", and "default-mono-font" each of which would simply "Requires:" the appropriate font package providing a single font of the respective style (serif/sans/mono). There are, I suspect, other packages that require at least one font during building, without caring for any particular font specifically.
So back to `BuildRequires:` an arbitrary font package. `free-ttf-fonts` may be not the perfect choice, but nobody sees the content produced during unit testing anyway.
If it is just needed for unit tests, then requiring a specific font might get you more deterministic results anyway.
Yes, but free-ttf-fonts is a wrong choice for this purpose as it provides not one, not two, but ~350 different font families/styles! If a single font is need for an application to build, I would recommend using a package that provides a single font --- for example, "font(freeserif)" or "font(freesans)" as suggested earlier. Cheers, -- Atri Bhattacharya Mon 28 Sep 01:12:18 CEST 2020 Sent from openSUSE Tumbleweed on my laptop. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
Hi, Sorry for the delayed response. On 9/17/20 12:11 AM, Ben Greiner wrote:
Hi,
Because I run into "Trace/breakpoint trap" crashes with Python packages using PyQt5 a lot lately, I asked a question at [1] and found out that the culprit is a missing default font for the bundled chromium in libqt5-webengine.
What is the best way to require a default font and into which package should the requirement declaration go? Obvious choices would be libqt5-webengine or python-pytest-qt. For the latter it wouldn't matter much which font to choose, but installing a default with libqt5-webengine or fontconfig has an effect on a lot of systems. Which font package would be the right one? Or is there a meta package?
There is no meta package at this time, noto-sans-fonts are the default fonts at the moment, the graphical patterns recommend it and i'm pretty sure parts of Yast require it so just using that package at the moment is probably the best solution. -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B
Am Mo, 28. Sep, 2020 um 9:58 A. M. schrieb Simon Lees <sflees@suse.de>:
There is no meta package at this time, noto-sans-fonts are the default fonts at the moment, the graphical patterns recommend it and i'm pretty sure parts of Yast require it so just using that package at the moment is probably the best solution.
Only required by a branding package which we may not be installing by default (I honestly don't remember), and isn't necessary for YaST to work, and also only with openSUSE-branding. Not to mention YaST isn't necessary for a system to work either ;) LCP [Stasiek] https://lcp.world -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On 9/28/20 10:02 AM, Stasiek Michalski wrote:
Am Mo, 28. Sep, 2020 um 9:58 A. M. schrieb Simon Lees <sflees@suse.de>:
There is no meta package at this time, noto-sans-fonts are the default fonts at the moment, the graphical patterns recommend it and i'm pretty sure parts of Yast require it so just using that package at the moment is probably the best solution.
Only required by a branding package which we may not be installing by default (I honestly don't remember), and isn't necessary for YaST to work, and also only with openSUSE-branding. Not to mention YaST isn't necessary for a system to work either ;)
Yeah, i'm just making the general assumption that any system capable of running pytest-qt will most likely already have one of those things, I am well aware of how small we can make a system I tend to get assigned all the we have too many uneccesary dependency bugs. -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B
participants (5)
-
Atri Bhattacharya -
Ben Greiner -
Simon Lees -
Stasiek Michalski -
Stefan Seyfried