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

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

Dear packager,

At 20091122T202901Z, your “liberation-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#     t5  t19
1      ‧   4
2      1   4
3      ‧   4
Total  1   12

P#  Maintainer  SRPM              RPM                     EVR                       Arch
1   cchance     liberation-fonts  liberation-mono-fonts   0:  noarch
2   cchance     liberation-fonts  liberation-sans-fonts   0:  noarch
3   cchance     liberation-fonts  liberation-serif-fonts  0:  noarch

Test explanation:

t5. Error: font faces duplicated by different packages

  ☛ Packager task, eventual upstream task
  Several packages duplicate font files with the same face name. This
  needlessly wastes resources infrastructure and user side and makes font
  maintenance problematic:
  1. Very often an upstream that copied some fonts will forget to keep them
  up to date, and the duplication will result in the distribution of old
  buggy data.
  2. Shipping the same font in different formats is also problematic:
  different font formats have different features, and are processed by
  different font libraries. It is almost impossible to create a font in
  multiple formats that will all behave the same. Users hate fonts that do
  not behave consistently everywhere.
  3. Most of our applications use fontconfig to access fonts, and fontconfig
  uses font names to identify files. Naming collisions make font selection
  unreliable. So even genuine forks with different features from the
  original are a problem if not renamed.
  A repository should always include only one version of a font face.
  This test can not discriminate between packages and identity the correct
  owner of the font face. His maintainer will be blamed with others. If
  you're not him it is therefore unfriendly not to fix this error as soon as
  you can.
  It is always possible to reuse a font file packaged separately by adding a
  dependency on the other package providing it, and accessing the font
  through fontconfig.
  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). However it can workarounded by the packager with
  symlinks (that will need maintenance).
  If an application can not use a modern font format and forces the
  re-packaging in an older format of an exiting font this is an application
  bug that should be reported to the application upstream. In that case
  these is no good solution possible baring the fixing of the application.
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 “liberation-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: liberation-fonts.tar.xz
Type: application/x-xz-compressed-tar
Size: 26608 bytes
Desc: not available
Url : http://lists.fedoraproject.org/pipermail/fonts-bugs/attachments/20091123/24520e6d/attachment.bin 

More information about the fonts-bugs mailing list