https://bugzilla.redhat.com/show_bug.cgi?id=1806272
Hans de Goede <hdegoede(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|weasyprint |dejavu-fonts
Assignee|spacewar(a)gmail.com |nicolas.mailhot(a)laposte.net
--- Comment #8 from Hans de Goede <hdegoede(a)redhat.com> ---
Ugh, I just noticed that widelands (another game) is hit by the Dejavu
font-file path changes in F32+ too. I'm fixing this now, but this made my
wonder if others are affected to, a dnf repoquery --whatrequires dejavu-*-fonts
results in the following list:
0ad-data-0:0.0.23b-4.fc32.noarch
dejavu-fonts-all-0:2.37-5.fc32.noarch
devedeng-0:4.16.0-2.fc32.noarch
e16-0:1.0.19-4.fc32.x86_64
e16-docs-0:0.16.8.0.2-18.fc32.noarch
emacs-1:26.3-2.fc32.x86_64
ember-media-0:0.7.2.1-11.fc32.noarch
enigma-0:1.21-17.20160222git0027b3b8e694.fc32.x86_64
fbida-0:2.14-8.fc32.x86_64
feh-0:3.2.1-2.fc32.x86_64
foobillard-0:3.0a-33.fc32.x86_64
gambas3-gb-sdl-0:3.14.3-2.fc32.x86_64
glob2-0:0.9.4.4-49.fc32.x86_64
gnubg-1:1.06.001-9.fc32.x86_64
gnuplot-0:5.2.8-2.fc32.x86_64
gravity-beams-and-evaporating-stars-0:1.0-4.fc32.x86_64
hedgewars-0:1.0.0-4.fc32.x86_64
htmldoc-0:1.9.7-2.fc32.x86_64
hyperrogue-0:10.0-9.d.fc32.x86_64
impressive-0:0.13.0-0.2.20190902svn275.fc32.noarch
kodi-common-0:18.5-2.fc32.x86_64
kosmtik-0:0.0.17-6.fc32.noarch
langpacks-core-font-af-0:3.0-2.fc32.noarch
<snip many more langpacks-core-font-*>
libprojectM-0:3.1.1-0.9.rc7.fc32.x86_64
libreoffice-core-1:6.4.1.2-1.fc32.x86_64
lincity-ng-data-0:2.9-0.20.20160605git7f266b1.fc32.noarch
mapnik-0:3.0.23-1.fc32.x86_64
mapserver-0:7.2.2-3.git7fe9b2b.fc31.x86_64
marsshooter-data-0:0.7.6-14.fc32.noarch
munin-0:2.0.54-3.fc32.noarch
mygui-0:3.2.2-13.fc32.x86_64
neverball-neverball-0:1.6.0-20.fc32.x86_64
neverball-neverputt-0:1.6.0-20.fc32.x86_64
perl-PDF-API2-0:2.037-1.fc32.noarch
php-tcpdf-dejavu-sans-fonts-0:6.3.5-1.fc32.noarch
php-tcpdf-dejavu-sans-mono-fonts-0:6.3.5-1.fc32.noarch
php-tcpdf-dejavu-serif-fonts-0:6.3.5-1.fc32.noarch
pioneer-data-0:20200203-1.fc32.noarch
pokerth-0:1.1.2-9.fc32.x86_64
python3-iep-0:3.7-16.fc32.noarch
python3-matplotlib-0:3.1.2-1.fc32.1.x86_64
python3-reportlab-0:3.5.34-3.fc32.x86_64
python3-tilestache-0:1.51.14-3.fc32.noarch
python3-weasyprint-0:51-2.fc32.noarch
python3-weasyprint-0:51-3.fc32.noarch
qcad-0:3.24.2.6-2.fc32.x86_64
retroarch-assets-0:1.8.4-4.fc32.noarch
retroarch-freeworld-assets-0:1.8.4-3.fc32.noarch
rrdtool-0:1.7.2-7.fc32.x86_64
scorched3d-0:44-21.fc32.x86_64
simspark-0:0.3.0-16.fc32.x86_64
sumwars-data-0:0.5.8-19.fc32.noarch
teeworlds-data-0:0.7.4-3.fc32.noarch
trackballs-0:1.1.4-36.fc32.x86_64
vdr-burn-0:0.3.0-16.fc32.x86_64
vdr-graphlcd-0:1.0.1-7.fc32.x86_64
vlc-1:3.0.9-33.fc32.x86_64
vodovod-0:1.10r22-15.fc32.x86_64
wesnoth-data-0:1.15.2-2.fc32.noarch
widelands-0:0-0.73.build20.fc32.x86_64
xblast-0:2.10.4-30.fc32.x86_64
xfce4-terminal-0:0.8.9.1-2.fc32.x86_64
xmoto-0:0.5.11-19.fc32.x86_64
xpilot-ng-data-0:4.7.3-20.fc32.noarch
zabbix-web-1:4.0.16-2.fc32.noarch
And I'm pretty sure various of these (at least most of the games in there) will
likely have hardcoded paths, typically the game data includes a copy of some
Dejavu*.ttf file and we replace it with a symlink which are now all broken.
Looking at this entire list, I really believe that we need to fix this at the
dejavu packaging level, fixing all other packages is going to be a lot of work,
esp. since it seems that there is no guarantee that this will not happen again
in the future! So I'm changing the component back to dejavu-fonts for now.
One possible solution would be to do something like the following in %build of
the fonts packages (example for the dejavu-sans-fonts pkg):
mkdir -p $RPM_BUILD_ROOT%{_datadir}/fonts/dejavu
for j in $(ls $RPM_BUILD_ROOT%{_datadir}/fonts/dejavu-sans-fonts); do
ln -s /usr/share/fonts/dejavu-sans-fonts/$i
$RPM_BUILD_ROOT%{_datadir}/fonts/dejavu
done
So that we get symlinks with the old filepath-s to the new locations, that
seems like a much saner solution then patching all consumers of the old
file-paths.
--
You are receiving this mail because:
You are on the CC list for the bug.