Summary: | fontconfig caches/registers dpkg temporary files instead of ignoring them | ||
---|---|---|---|
Product: | fontconfig | Reporter: | Raphaël Hertzog <raphael> |
Component: | fc-cache | Assignee: | fontconfig-bugs |
Status: | RESOLVED FIXED | QA Contact: | Behdad Esfahbod <freedesktop> |
Severity: | normal | ||
Priority: | medium | CC: | akira |
Version: | 2.11 | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: | Skip over .dpkg-tmp files |
Description
Raphaël Hertzog
2016-07-12 09:36:54 UTC
Ping? We have been using the patch I prepared in Kali Linux and I haven't had any new report since then so I guess it's working. It would be nice to have some comment from you and have this bug fixed upstream. I don't want to include any specific fixes in fontconfig. just to ignore reading certain caches, you could try: <fontconfig> <selectfont> <rejectfont><glob>*.dpkg-tmp</glob></rejectfont> </selectfont> </fontconfig> This would works unless anyone has any <acceptfont> rule there which may matches such temporary file as well. Thanks for the suggestion Akira. I confirm that your configuration snippet has the expected result. I'll make sure it gets included in Debian. You might still want to include that rule in a conf.d/70-dpkg.conf file on the upstream side for example. (In reply to Raphaël Hertzog from comment #3) > Thanks for the suggestion Akira. I confirm that your configuration snippet > has the expected result. > > I'll make sure it gets included in Debian. You might still want to include > that rule in a conf.d/70-dpkg.conf file on the upstream side for example. If this issue affects more widely, perhaps. otherwise it should be added and maintained in their own. for instance, Ubuntu also uses the deb format for packaging though, I suppose they might be also watching the changes in Debian. so I'd suggest maintaining it yourself would be a good option. I'll close this at this moment. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.