Re: Processed: reassign 675791 to libgtk2.0-bin,libgtk-3-bin
On Sun, 2012-06-03 at 23:26:55 +0200, Michael Biebl wrote:
> could you please elaborate why you think this is a bug in libgtk2.0-bin
> resp. libgtk-3-bin?
As stated on my reply to the original report, I only reassigned
because it seems to be a (small) issue in update-icon-caches and
certainly not in dpkg, but if there's a rationale for that behaviour
then I guess you can just close it.
> We do have file based triggers installed e.g. in gnome-icon-theme for
> /usr/share/icons/gnome and we clean up the cache file in preinst on
> "remove" via "rm -f /usr/share/icons/gnome/icon-theme.cache".
> I'm having a hard time seeing the bug in update-icon-caches you are
> talking about, so it would be great if you could explain what you mean
> in more detail.
As mentioned in my reply, the only (minor) issue here is that dpkg is
left thinking it owns some directories after remove that do not exist
anymore, because update-icon-caches removes the parent directories
after having removed the icon cache files:
# No more index.theme, remove the cache if it exists
rm -f "$dir"/icon-theme.cache
rmdir -p --ignore-fail-on-non-empty "$dir"
On both the gtk2 and gtk3 versions of the script.