commit db62fb95bbba3d41c0c58b919a680cf1e487bb7f Author: Adam Williamson awilliam@redhat.com Date: Wed Nov 4 12:56:21 2015 -0800

drop forced fontconfig cache generation, should not be needed

Per discussion on #1169979, fontconfig upstream think they have the bugs licked, so this shouldn't be needed any more. We need to check the nightly lives after this and see if their caches are now correct.

fedora-live-base.ks | 6 ------ 1 files changed, 0 insertions(+), 6 deletions(-) --- diff --git a/fedora-live-base.ks b/fedora-live-base.ks index 2a22a6d..fb201d3 100644 --- a/fedora-live-base.ks +++ b/fedora-live-base.ks @@ -313,12 +313,6 @@ rm -f /core* # convince readahead not to collect # FIXME: for systemd

-# forcibly regenerate fontconfig cache (so long as this live image has -# fontconfig) - see #1169979 -if [ -x /usr/bin/fc-cache ] ; then - fc-cache -f -fi - echo 'File created by kickstart. See systemd-update-done.service(8).' \ | tee /etc/.updated >/var/.updated