On Wed, 2007-11-14 at 07:51 +0100, Sven Luther wrote:
> Hi Keith, ...
> 
> The bug was supposed to be an etch bug, so i wonder how a fontconfig
> upload to uunstable could have fixed it. Or does this mean that since
> etch is stable, this bug cannot be fixed, and thus you are closing the
> bug ? 

Oh. Oops. It's not possible to fix this in etch without updating to the
newer fontconfig. Looks like I didn't check the bug closely enough
before marking it closed.

> Was it reproducible on your side ? 

Yes, this would be caused by almost any kind of file system clock skew,
or even a very fast installer. 2.5.0 fixes this by eliminating the
comparison between two file mod times.

-- 
[EMAIL PROTECTED]

Attachment: signature.asc
Description: This is a digitally signed message part

Reply via email to