kdebase4-runtime and hicolor-icon-theme both claim ${prefix}/share/icons/hicolor/index.theme

[ryandesign (Ryan Carsten Schmidt)]

kdebase4-runtime and hicolor-icon-theme both want to install ${prefix}/share/icons/hicolor/index.theme:

--->  Fetching hicolor-icon-theme
--->  Verifying checksum(s) for hicolor-icon-theme
--->  Extracting hicolor-icon-theme
--->  Configuring hicolor-icon-theme
--->  Building hicolor-icon-theme
--->  Staging hicolor-icon-theme into destroot
--->  Installing hicolor-icon-theme @0.10_0
--->  Activating hicolor-icon-theme @0.10_0
Error: Target org.macports.activate returned: Image error: /mp/share/icons/hicolor/index.theme is being used by the active kdebase4-runtime port.  Please deactivate this port first, or use the -f flag to force the activation.
Error: The following dependencies failed to build: libgnomeui gnome-icon-theme hicolor-icon-theme icon-naming-utils p5-xml-simple p5-xml-namespacesupport p5-xml-sax libgphoto2
Error: Status 1 encountered during processing.

What should I do?

[illogic-al@…]

deactivate kdebase4-runtime? force the install? your choice really. The gnome stuff and kde stuff seems not to play together nicely.

[(none)]

Milestone Port Bugs deleted

[jeremy.laine@…]

kdebase4-runtime is the one at fault here, it should not be install the index.theme file. This is confirmed by the following comment in the Debian packaging for kdebase4-runtime:

# Files not installed because they conflict with hicolor-icon-theme: ./usr/share/icons/hicolor/index.theme

I will post a patch to fix this issue as soon as I have finished rebuilding.

[mf2k (Frank Schima)]

Committed revision r59011. Thanks!