severity 387928 important thanks The only way I am able to reproduce this bug is if I have a fonts.conf without a cache directive, and the only way I am able to get a fonts.conf without a cache directive is by modifying this conffile and then disallowing dpkg to update the conffile on upgrade.
That is not a release-critical bug; there are plenty of cases when keeping an old, custom config around on your system results in a broken package and requires manual intervention to get it working again. These are the consequences that the admin must accept responsibility for when deviating from the Debian-provided conffile. So since no one has shown a way that Debian itself can trigger this bug (a clean sarge chroot+fontconfig, dist-upgraded to etch, does not produce the bug), I believe it should be downgraded. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
