Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 9: reading configurations from ~/.fonts.conf is deprecated what about fix this file instead overwrite already fixed on yum-updates while bailing at the same moment that is deprecated as also while opening ANY graphical application in a terminal?
So what would you suggest? that encourage you to move them from the deprecated place to new one. you can find it out from the release notes: http://docs.fedoraproject.org/en-US/Fedora/18/html/Release_Notes/sect-Release_Notes-Changes_for_Desktop.html#idm33339648
How about simply not deprecating the old place, by dropping the deprecated="yes" part from the 50-user.conf config file, and otherwise just leaving it alone? What absolute requirement exists to force users to change their working setup?
whatever - but i expect as user that package-maintainers read such messages which i face due the update, permanently by startign any graphical app from a konsole in the development cycle and fix such issues
Well, maintaining multiple places to customize makes complicated and hard to track issues down when something happened. the way to shut it up is indeed simple. but investigating issues isn't simple then. one who is responsible/helping your issues always needs to care about both places. that's why old one *is* deprecated. Aside from that, there are no way to fix that with scriptlet in the package once it has been completely gone. in fact it's not a part of file in the package. you have to manage it yourself. I see it's not an user-friendly reminder since it doesn't mention where is new place. so that is what only thing I can improve, I think so far.
(In reply to comment #4) > [...] one who is responsible/helping your issues always needs to care about > both places. that's why old one *is* deprecated. [...] Can you give an example of a problem (maybe a bz?) where helping someone with a font issue was made simpler by saying "check some $XDG_FOO subdirectory under $HOME", but where adding "... or $HOME/.fonts" would have been too complicated?
You are just assuming one knows something broken in fontconfig recipes. there should be some possibilities in other areas if an issue is just "rendering is broken" say. and also assuming one knows fontconfig deals with both places. reporter may says "I don't have any custom recipes in my $HOME" but any tools or something like that may care.
Isn't this a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=882267 ?
Yes. *** This bug has been marked as a duplicate of bug 882267 ***