Bug 480878 - fc-cache says that it writes to /var/tmp/${localstatedir}/cache/${PACKAGE} and it does - literally
Summary: fc-cache says that it writes to /var/tmp/${localstatedir}/cache/${PACKAGE} an...
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: fontconfig
Version: 10
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Behdad Esfahbod
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-01-21 02:08 UTC by Michal Jaegermann
Modified: 2009-01-29 22:00 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-01-29 22:00:43 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Michal Jaegermann 2009-01-21 02:08:18 UTC 
Description of problem:

Look at this:

# fc-cache -v /usr/share/fonts/dejavu
/usr/share/fonts/dejavu: skipping, existing cache is valid: 42 fonts, 0 dirs
/var/tmp/${localstatedir}/cache/${PACKAGE}: cleaning cache directory
/root/.fontconfig: not cleaning non-existent cache directory
fc-cache: succeeded

As a result I have a '/var/tmp/${localstatedir}/cache/${PACKAGE}/' directory, full of newly created cache files, but in /var/cache/fontconfig/ the newest
file is from 2009-01-09. That with three "liberation-fonts*" packages just
installed by yum.

Version-Release number of selected component (if applicable):
fontconfig-2.6.91-1.git.64.g9feaf34.fc11

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