Comment 33 for bug 104553

The debian bug claims that the problem is fixed in the current fontconfig. If someone can come up with a way to reproduce the problem (preferable in a chroot) that would be much appreciated. I would like to fix the problem in fontconfig itself instead of in the postinst script because we would have to duplicate the fix in the postinst script for every font package.

If you look for a way to reproduce it, then pythons "os.utime()" may be useful to set mtime and atime of dirs/files. Best if probably to try to reproduce it on feisty or edgy first and then we can check if it affects newer versions still.

Thanks,
 Michael