Bug 481423 - [OpenJDK] Adapt to F11 fonts packaging changes
[OpenJDK] Adapt to F11 fonts packaging changes
Product: Fedora
Classification: Fedora
Component: java-1.6.0-openjdk (Show other bugs)
All Linux
low Severity medium
: ---
: ---
Assigned To: Lillian Angel
Fedora Extras Quality Assurance
Depends On:
Blocks: F11-new-font-rules
  Show dependency treegraph
Reported: 2009-01-24 11:15 EST by Nicolas Mailhot
Modified: 2009-05-11 13:07 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-05-11 13:07:16 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Nicolas Mailhot 2009-01-24 11:15:47 EST
A huge font repackaging operation is ongoing in Rawhide.

IIRC java is still not 100% fontconfig-ified and depends on font files location.

Please check before each Alpha/Beta/Test releases the distro font changes have not broken something openjdk-side
Comment 1 Nicolas Mailhot 2009-02-18 14:33:35 EST
This is a reminder for all the packagers that still have bugs open about adapting to font packaging guidelines there is only one month left before Fedora 11 beta:

A week of this month will see the Fedora 11 mass rebuild, that will load the build farm:

As already converted packages showed it is quite possible to make mistakes during the conversion. Please make releng and QA happy and don't wait till the last minute to do your changes (avoid pre-beta panic). If possible start before the mass rebuild so we don't burn cycles on incorrect packages.

The PackageKit enhancements stated for Fedora 11 assume fonts and font-using packages are sane (basically respect packaging guidelines). It is quite possible that not-converted packages will interact with the F11 font autoinstall feature in "interesting" ways.

We don't want that

There is extensive documentation on the wiki and most of your questions have likely already been answered there. Please do read the FAQ before making more work for the support team by asking questions answered there.

Note You need to log in before you can comment on or make changes to this bug.