| Summary: | icon theme cache not removed on uninstall | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Jean-François Fortin Tam <nekohayo> |
| Component: | distribution | Assignee: | Rex Dieter <rdieter> |
| Status: | CLOSED WONTFIX | QA Contact: | Bill Nottingham <notting> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 16 | CC: | dennis, jreznik, kevin, ltinkl, mclasen, rdieter, rnovacek, rvokal, than |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-02-13 21:30:02 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Jean-François Fortin Tam
2012-01-03 21:27:05 UTC
the package contains our standard fedora rpm icon scriptlets:
%post
touch --no-create %{_kde4_iconsdir}/oxygen &> /dev/null || :
%posttrans
gtk-update-icon-cache %{_kde4_iconsdir}/oxygen &> /dev/null || :
%postun
if [ $1 -eq 0 ] ; then
touch --no-create %{_kde4_iconsdir}/oxygen &> /dev/null || :
gtk-update-icon-cache %{_kde4_iconsdir}/oxygen &> /dev/null || :
fi
I'd have expected the latter, %postun one to clean up the .cache alright.
But, as it turns out, it doesn't, grr, since gtk-update-icon-cache won't process a icon directory with no index.theme file.
this same problem should affect any/all packaged icon themes. :(
gtk folks, mind making gtk-update-icon-cache smarter to remove an existing and obviously invalid icon-theme.cache in this case? or come up with some better way to handle it (preferably without having to change scriptlets in <n> different icon packages)?
I have %ghosted the cache files in my icon theme packages. Sure, that's an option. Seems to me this is a problem only for the main icon theme package, the one that provides the index.theme file. So, the impact shouldn't be large. I guess we can go with that. I'll look into fixing guidelines and affected icon theme packages. I suppose in a perfect world these icon-theme.cache files would all go under /var/cache/ somewhere (similar to how fontconfig cache files eventually ended up in /var/cache/fontconfig). Would that merely require toolkit changes? I naively assumed so, but the move to use /var/cache would likely be more work than my original suggestion of simply removing the icon-theme.cache file when it's obviously invalid (as in the case of a missing index.theme) This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '16'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. |