I upgraded to KDE plasma using the guide at https://wiki.gentoo.org/wiki/KDE/Plasma_5_upgrade . However, digikam blocks the upgrade. There are two problems. First, digikam requires baloo 4, which is incompatible with Plasma 5. This can be fixed by setting USE="-semantic-desktop". The second one has to do with LINGUAS. I don't understand where the dependency is specified, but digikam required kde4-l10n. This blocks Plasma 5, too. However, it's possible to use LINGUAS with Plasma 5 - see e.g. the krusader package. Maybe whatever it is that is required here could be specified in the way it is done in krusader ebuild, and then things would work? I still have the digikam-4.12. installed from before I did the Plasma 5 upgrade, and it works fine even though I could not now re-emerge it because of the block. Reproducible: Always
Actually, the krusader ebuild doesn't work with Plasma 5 either... Not sure what apps it are actually supported by it at this point!
Please use the plasma profile, it makes things considerably easier. For example, the two baloos _are_ coinstallable using the minimal flag. kde4-l10n and kde-l10n are coinstallable using the minimal flag. What's the problem with krusader?
Please add emerge --info too.
OK, I saw that plasma desktop profile had set the use flag "minimal", but with this description, I didn't want a "minimal" build so I added USE="-minimal" in make.conf. minimal: "Install a very minimal build (disables, for example, plugins, fonts, most drivers, non-critical features)" I mean, a system without plugins, fonts and most drivers - that just sounds bad. On which packages do I have to use the "minimal" setting to be able to install kde4-l10n side-by-side with plasma? kde4-l10n seems to be one of them, but is it ok to have "-minimal" on all the other packages that have such a USE flag?
Created attachment 411282 [details] emerge --info output is attached
There are file collisions between kde4-l10n USE="-minimal" and the following packages: * kde-plasma/systemsettings-5.4.0:5::gentoo * /usr/share/doc/HTML/nl/systemsettings/index.cache.bz2 * /usr/share/doc/HTML/nl/systemsettings/index.docbook * /usr/share/doc/HTML/sv/systemsettings/index.cache.bz2 * /usr/share/doc/HTML/sv/systemsettings/index.docbook * * kde-plasma/ksysguard-5.4.0:5::gentoo * /usr/share/doc/HTML/nl/ksysguard/index.cache.bz2 * /usr/share/doc/HTML/nl/ksysguard/index.docbook * /usr/share/doc/HTML/sv/ksysguard/index.cache.bz2 * /usr/share/doc/HTML/sv/ksysguard/index.docbook * * kde-plasma/plasma-desktop-5.4.0:5::gentoo * /usr/share/doc/HTML/nl/plasma-desktop/index.cache.bz2 * /usr/share/doc/HTML/nl/plasma-desktop/index.docbook * * kde-plasma/kmenuedit-5.4.0:5::gentoo * /usr/share/doc/HTML/nl/kmenuedit/index.cache.bz2 * /usr/share/doc/HTML/nl/kmenuedit/index.docbook * /usr/share/doc/HTML/sv/kmenuedit/index.cache.bz2 * /usr/share/doc/HTML/sv/kmenuedit/index.docbook * * kde-plasma/khelpcenter-5.4.0:5::gentoo * /usr/share/doc/HTML/nl/khelpcenter/index.cache.bz2 * /usr/share/doc/HTML/nl/khelpcenter/index.docbook * /usr/share/doc/HTML/sv/khelpcenter/index.cache.bz2 * /usr/share/doc/HTML/sv/khelpcenter/index.docbook * * kde-plasma/kinfocenter-5.4.0:5::gentoo * /usr/share/doc/HTML/nl/kinfocenter/index.cache.bz2 * /usr/share/doc/HTML/nl/kinfocenter/index.docbook
If I emerge kde4-l10n with USE="minimal -handbook", I still get file collisions: * Searching all installed packages for file collisions... * * Press Ctrl-C to Stop * * kde-plasma/kgamma-5.4.0:5::gentoo * /usr/share/locale/ca/LC_MESSAGES/kcmkgamma.mo * /usr/share/locale/da/LC_MESSAGES/kcmkgamma.mo * /usr/share/locale/de/LC_MESSAGES/kcmkgamma.mo * /usr/share/locale/el/LC_MESSAGES/kcmkgamma.mo * /usr/share/locale/en_GB/LC_MESSAGES/kcmkgamma.mo * /usr/share/locale/es/LC_MESSAGES/kcmkgamma.mo * /usr/share/locale/fi/LC_MESSAGES/kcmkgamma.mo * /usr/share/locale/fr/LC_MESSAGES/kcmkgamma.mo * /usr/share/locale/is/LC_MESSAGES/kcmkgamma.mo * /usr/share/locale/it/LC_MESSAGES/kcmkgamma.mo * /usr/share/locale/ja/LC_MESSAGES/kcmkgamma.mo * /usr/share/locale/nl/LC_MESSAGES/kcmkgamma.mo * /usr/share/locale/sv/LC_MESSAGES/kcmkgamma.mo * /usr/share/locale/uk/LC_MESSAGES/kcmkgamma.mo * /usr/share/locale/zh_CN/LC_MESSAGES/kcmkgamma.mo * /usr/share/locale/zh_TW/LC_MESSAGES/kcmkgamma.mo *
Only =kde4-l10n-4.14.3* would fail because it wasn't updated anymore to fix the blockers with kde-plasma-5.4/kde-frameworks-5.13. You only hit that error because (it seems) you are running a stable system. kde4-l10n-15.08.0-r1 is ready for you to fix that file collision, and older versions of kde4-l10n should be blocked soon in your case. Plasma profile sets USE=minimal wherever it is needed on certain kde-apps/ and kde-base/ packages, nothing more.
Thanks for the answer! I unmasked the kde4-l10n-15.08.01-r1 and now kde4-l10n was updated to that version and I could install digikam. With these file collisions, would it make sense for one of the plasma packages to either block the older kde4-l10n version or to explicitly require a version newer than 4.14.3? It sounds as if kde4-l10n-4.14.3 cannot be co-installed with Plasma 5, but Portage appears to be unaware of that.
Incompatible kde4-l10n versions are now blocked. This can be closed?
Great thanks! Yes, it's done.
