#1525 BLOC Update.: fontconfig cache is invalidated too easily on mtime check

[Zarro Boogs per Child]

#1525: fontconfig cache is invalidated too easily on mtime check
----------------------+-----------------------------------------------------
  Reporter:  jg       |       Owner:  sayamindu
      Type:  defect   |      Status:  new      
  Priority:  blocker  |   Milestone:  Update.1 
 Component:  distro   |     Version:           
Resolution:           |    Keywords:  upstream 
  Verified:  0        |  
----------------------+-----------------------------------------------------

Comment(by sayamindu):

 I noticed that the mtime for all the *.cache-2 files in
 /var/cache/fontconfig in joyride-327 (which was built on  21st November)
 is set to 2nd November 2007. Is it possible that the old cache files are
 still lying around ? That would probably confuse fontconfig since the RPM
 included in this build expects the font directory mtime to be stored in
 the cache file itself.

 I'm not very familiar with the build system (no first hand experience
 here) - but is it possible that old files may be lying around ?

 In what may also be related, I looked at the spec file carefully, and
 there seems to be a small mistake in the %post part (this is also in the
 original Fedora SPEC). The %post part has

 {{{
 rm -f
 %{_localstatedir}/cache/fontconfig/????????????????????????????????.cache-2
 }}}

 This won't work, since the caches are named like <md5sum>-x86.cache-2.
 The correct line would be

 {{{
 rm -f
 %{_localstatedir}/cache/fontconfig/????????????????????????????????????.cache-2
 }}}

-- 
Ticket URL: <http://dev.laptop.org/ticket/1525#comment:17>
One Laptop Per Child <http://dev.laptop.org>
OLPC bug tracking system