I have gnome-icon-theme-3.0.0 installed, and collision-protect doesn't allow openoffice-bin or libreoffice-bin to be installed because of some icon files. Reproducible: Always Steps to Reproduce: 1. Enable collision-protect 2. Install gnome-icon-theme-3.0.0 3. Try installing libreoffice-bin-3.3.2 or openoffice-bin-3.3.0 Actual Results: Can't install because of file collision Expected Results: Successfull install with the right icons (not sure which are the good ones, from gnome or libreoffice/openoffice)
Created attachment 269125 [details] emerge --info
Created attachment 269127 [details] Error from libreoffice-3.3.2 install The ebuild collides with other icons, but those must be old leftovers that can be safely removed, the problematic colliding ones are the ones from gnome-icon-theme-3.0.0.
Hmmm, weird. I have both gnome-icon-theme-3 and libreoffice-bin 3.3.2 installed on one of my machines - and no conflict whatsoever. Will have to take another look here later.
Me neither
Which of the two should install those files then? I could look and try to find why I have the issue with the other ebuild.
Well this should definitely not be installed by gnome-icon-theme...
gnome-icon-theme uses the command /usr/libexec/icon-name-mapping during installation to create symlinks for icons. (for backwards compatibility with desktop icon themes not compliant with the freedesktop.org icon naming spec) This command uses /usr/share/icon-naming-utils/legacy-icon-mapping.xml and the two are part of x11-misc/icon-naming-utils (currently 0.8.90). This xml file contains the following entries, for example. All those files are created as symlinks (since icon-naming-utils 0.5.0). I'm just wondering why nobody had a problem with this before. <icon name="x-office-document"> <link>application-vnd.ms-word.document.macroEnabled.12</link> <link>application-vnd.openxmlformats-officedocument.wordprocessingml.document</link> <link>gnome-mime-application-msword</link> <link>gnome-mime-application-pdf</link> <link>gnome-mime-application-postscript</link> <link>gnome-mime-application-rtf</link> <link>gnome-mime-application-vnd.oasis.opendocument.text</link> <link>gnome-mime-application-vnd.stardivision.writer</link> <link>gnome-mime-application-vnd.sun.xml.writer</link> <link>gnome-mime-application-wordperfect</link> <link>gnome-mime-application-x-abiword</link> <link>gnome-mime-application-x-applix-word</link> <link>gnome-mime-application-x-dvi</link> <link>gnome-mime-application-x-gzpostscript</link> <link>gnome-mime-application-x-kword</link> <link>gnome-mime-application-x-scribus</link> <link>gnome-mime-application-x-tex</link> <link>document</link> <link>package_wordprocessing</link> <link>wordprocessing</link> </icon>
I've just checked icon-naming-utils handling has not changed in gnome-icon-theme-3, then, this is not a regression. But probably the problem is in x11-misc/icon-naming-utils generating that symlinks
Looks like I had a symlink hicolor -> gnome in /usr/share/icons/. So the thing is, gnome-icon-theme should not install icons in /usr/share/icons/hicolor/, which is usually the case but this was broken for me because /usr/share/icons/hicolor/ was /usr/share/icons/gnome/ because of my symlink. I removed the symlink, restored the real folder, and now everything works again! The issue was really on my side. Thank you for your help, and sorry for the noise here! :/
