[RFA] Your cjkuni-fonts package did not pass QA

repo-font-audit nim at fedoraproject.org
Mon Nov 23 06:20:04 UTC 2009

Dear packager,

At 20091122T202901Z, your “cjkuni-fonts” package failed one or more of the tests
I was performing on the “fedora-devel” repository located at:

There are three different reasons that may cause this message:
1. your package is including one or more font files, but not packaging
   them properly;
2. your package is including one or more font files, and I've found
   issues in some of them;
3. your package is not shipping any font file, but the way it accesses
   fonts in other packages is not satisfying.

To stop receiving this message, you need to:
1. drop the font files or fix their packaging;
2. relay the fonts issues to the fonts upstream to get them revised;
3. work with the code upstream to improve the way it accesses font
   files (usually by making it use fontconfig through a higher-level
   text library such as pango, pango-cairo, harfbuzz, or QT)

You can self-check your packages at any time by:
1. installing createrepo and fontpackages-tools:
# yum install createrepo fontpackages-tools
2. putting your packages and any font package they depends on in a
   test directory
3. indexing this directory with createrepo:
$ createrepo path-to-test-directory
4. running repo-font-audit:
$ repo-font-audit test file://absolute-path-to-test-directory

A summary of the issues I detected is appended here. For your
convenience a more comprehensive analysis is also attached to this

Errors, warnings and suggestions:

P#     t9  t10  t15  t17  t19
1      ‧   ‧    2    ‧    ‧
2      ‧   1    ‧    1    1
3      1   1    ‧    1    1
Total  1   2    2    2    2

P#  Maintainer  SRPM          RPM                  EVR                       Arch
1   cchance     cjkuni-fonts  cjkuni-fonts-compat  0:0.2.20080216.1-31.fc13  noarch
2   cchance     cjkuni-fonts  cjkuni-ukai-fonts    0:0.2.20080216.1-31.fc13  noarch
3   cchance     cjkuni-fonts  cjkuni-uming-fonts   0:0.2.20080216.1-31.fc13  noarch

Test explanation:

t9. Error: rpmlint

  ☛ Packager task
  Check rpmlint output to fix the listed packages (using the -i flag if you
  don't understand rpmlint messages).
t10. Error: fonts in packages that contain non-font data

  ☛ Packager task
  Please do not mix font files with non-font data in packages. Fonts are
  usually useful outside of the package that deploys them and should be
  installable without pulling in other material.
t15. Warning: font linking

  ☛ Upstream task
  Symlinking is a way for non-font packages to avoid duplicating font files,
  but it is also a symptom of missing or incomplete fontconfig support.
  Fontconfig has been our default font system for a long time, and accessing
  fonts by other means will cause behaviour inconsistencies and many other
  problems (since fontconfig can be used to change the behaviour of a font).
  If an application can not use fontconfig today this is a serious bug that
  should be reported to the application upstream. Please ask it to add
  fontconfig support to their code (usually, via a higher-level library
  such as pango-cairo).
t17. Warning: fonts that do not pass fontlint sanity checks

  ☛ Font upstream task
  Fontforge's fontlint¹ test suite found problems in some files included in
  the package. Those problems may not be obvious and only manifest as
  strange behaviour in specific applications (making them hard to debug).
  For that reason it is recommanded to report those problems upstream and
  get them fixed, even if the font file seems to work fine most of the time.
  You can ask help about specific fontlint errors on:
  Please relay the problem report to the font upstream.
  ¹ http://fontforge.sourceforge.net/fontlint.html
t19. Suggestion: fonts with partial script coverage

  ☛ Font upstream task
  Some font files included in the package are missing a few glyphs to be
  accepted by fontconfig as covering one or several scripts. Therefore they
  could be made useful to more people with only a little effort.
  Many scripts differ by only a few glyphs and it is unfortunately common
  for font authors not to notice they stopped just short of full support for
  some of them.
  To check a font file script coverage, run:
  $ FC_DEBUG=256 fc-query font-file
  and look for lines like:
  script-id¹(number) { list-of-unicode-codepoints }
  For example
  “mi(2) { 1e34 1e35 }”
  means fontconfig will accept the tested file for Maori if codepoints 1e34
  and 1e35 are added.
  fontconfig is used by a lot of applications on many systems so ignoring
  its opinion on a font is a mistake.
  Please relay the incomplete coverage report to the font upstream.
  Of course fontconfig is not perfect either so it may require a glyph for a
  script when it should not. In that case, please report the problem to
  fontconfig upstream:
  against the “orth” component.
  ¹ http://www.loc.gov/standards/iso639-2/php/code_list.php
  ² https://bugs.freedesktop.org/enter_bug.cgi?product=fontconfig

Please take the appropriate measures to fix the “cjkuni-fonts” package.
I will warn you again if it is still necessary next time I am ran.

This report was generated by the repo-font-audit command from:

Please post questions, suggestions, patches or bug reports to:
(subscription required)

Your friendly QA robot,

-------------- next part --------------
A non-text attachment was scrubbed...
Name: cjkuni-fonts.tar.xz
Type: application/x-xz-compressed-tar
Size: 32100 bytes
Desc: not available
Url : http://lists.fedoraproject.org/pipermail/fonts-bugs/attachments/20091123/a52eb60d/attachment.bin 

More information about the fonts-bugs mailing list