Red Hat Bugzilla – Bug 491510
[Tracker] rpm font autoprovides are missing some font types
Last modified: 2009-03-25 01:49:26 EDT
The new font autoprovides are working well for some font formats but are not processing others:
1. ttc files: http://koji.fedoraproject.org/koji/rpminfo?rpmID=1026593
2. pfa files: http://koji.fedoraproject.org/koji/rpminfo?rpmID=1126190
3. compressed pcf fonts: http://koji.fedoraproject.org/koji/rpminfo?rpmID=1054305
(and probably plain pcf fonts though I could not locate a pcf package that was properly converted yet)
Also, it seems to fail even for plain ttf files, when they have a space in their name: http://koji.fedoraproject.org/koji/rpminfo?rpmID=1055798
The problem with .ttc and .pfa is that neither is seen as font data by libmagic:
[pmatilai@localhost cjkuni-ukai-fonts-0.2.20080216.1]$ file ukai.ttc
[pmatilai@localhost culmus-0.102]$ file YehudaCLM-Bold.pfa
YehudaCLM-Bold.pfa: PostScript document text
These should be treated filed against "file" (libmagic), rpm will recognize them as fonts as soon as libmagic does.
Compressed files aren't currently being looked into. I initially enabled it when enabling the font provide stuff but it blew up at least openoffice.org build due to leaking file descriptors someplace (probably libmagic but haven't had a chance to look at it).
Spaces in filenames causing issues is likely to be something entirely different, lets not pile things up.
Ok, let's split this
For some reason this still does not work for culmus-fonts pfa files, even though file now correctly identifies them
$ file /usr/share/fonts/culmus/MiriamMonoCLM-BookOblique.pfa
/usr/share/fonts/culmus/MiriamMonoCLM-BookOblique.pfa: PostScript Type 1 font text
rpm used to have a private copy of /usr/share/magic,
so it may not be enough to fix file*(1).
Same patch to rpm's version of /usr/share/magic is all
that is needed.
Space in file paths is just ho-hum tedium yes ...
Oh I see, " text" happens to be before " [Ff]ont" in the matching order so "foo font text" gets classified as text. PFA isn't the only font type affected by this either. Will fix...
...and fixed in rpm-4.7.0-0.beta1.7.fc11.
AFAICS we're all done here...