Steve Langasek says: "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."
But a few messages up a way to reproduce the bug is given in detail. Specifically: " I have had this problem (unable to write cache) on a clean install of etch from a full cd image via jigdo (20061009)." He goes on to say: "These are the consequences that the admin must accept responsibility for when deviating from the Debian-provided conffile." I find it very frustrating when people claim that this must be the result of custom config or old software. The only software on that install was from etch. There were no manual mods to any config files. I have not deviated from Debian-provided anything! I realise it may not occur in upgrades from sarge but it _does_ occur on a clean install (every single install I have done on my test system). The fact that it does not happen in upgrades does not mean it does not exist. This bug prevents openoffice.org from installing in a clean etch install. This bug should be release critical on the grounds that it prevents ttf-opensymbol from installing. I would be a little concerned if the release notes for etch said: 1) install sarge 2) upgrade to etch. ----- Joel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
