On 03/07/17 14:34, Andrew J. Buehler wrote: > On 2017-07-02 at 20:37, Tomasz Nitecki wrote: >> This fix worked fine for me (as far as I can tell). > > I tried this with /etc/fonts/local.conf (since that's the directory > where fonts.conf, which mentions local.conf as the file in which local > modifications to the configuration should be made, is located on my > machine), and it seems to have worked.
Ouch, I could have sworn that I've used /etc/fontconfig/local.conf but my own /etc git repository log confirms that I've added /etc/fonts/local.conf. Sorry for the confusion! > This doesn't invalidate the bug, in that either this change should not > happen (the default behavior should be the same after upgrade as before) > or the fact of the change should be announced - with a pointer to where > to find this information on how to revert it - at upgrade time, but it > does seem to mean that my own problem is now resolved. Yup I do agree that it would be nice to announce this change and add a note on how to revert it. Adding this information inside NEWS.Debian file should be an easy fix. I'd only wait for a few confirmations so that we are sure that this fix doesn't break anything and works fine. > Hopefully the existence of this filed report will make it easier for > other people to find the issue and this solution in the future, even if > no change to the upgrade-time behavior is ever made. Ok, so just two quick additions: 1. Correct local.conf location for the system wide configuration is /etc/fonts/local.conf 2. You can use Terry`s configuration [A] as it is cleaner (with proper xml structure) and works just as well. Regards, T. [A] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866950#10
signature.asc
Description: OpenPGP digital signature
