Bug #844

Пакеты kde-l10n и kde4-l10n конфликтуют в CLSK 15 KDE5

Added by Святослав Ворона over 3 years ago.

Status:New Start:11/28/2015
Priority:Normal Due date:
Assignee:- % Done:

0%

Category:Calculate Linux Scratch Spent time: -
Target version:15.12
Votes: 0

Description

В связи с этим невозможно сделать такие программы например как KRDC, Gwenview, Yakuake русифицированными. emerge сообщает о том что конфликтуют файлы, есть ли какой-то способ избежать подобного и установить правильную локализацию для KDE4 приложений?

Вывод терминала:

calculate ~ # emerge kde4-l10n
Calculating dependencies... done!

Emerging binary (1 of 1) kde-apps/kde4-l10n-15.08.3-r1::gentoo
Installing (1 of 1) kde-apps/kde4-l10n-15.08.3-r1::gentoo
Failed to install kde-apps/kde4-l10n-15.08.3-r1, Log file:
'/var/calculate/tmp/portage/kde-apps/kde4-l10n-15.08.3-r1/temp/build.log'
Jobs: 0 of 1 complete, 1 failed Load avg: 1.91, 2.72, 2.52
Extracting info

* Package: kde-apps/kde4-l10n-15.08.3-r1 * Repository: gentoo * USE: linguas_de abi_x86_64 amd64 linguas_ru linguas_fr linguas_bg linguas_nl linguas_pl linguas_pt kernel_linux minimal linguas_ro elibc_glibc linguas_pt_BR linguas_es handbook userland_GNU linguas_uk linguas_it * FEATURES: preserve-libs sandbox usersandbox

Extracting kde-apps/kde4-l10n-15.08.3-r1

* This package will overwrite one or more files that may belong to other * packages (see list below). You can use a command such as `portageq * owners / <filename>` to identify the installed package that owns a * file. If portageq reports that only one package owns a file then do * NOT file a bug report. A bug report is only useful if it identifies at * least two or more packages that are known to install the same file(s). * If a collision occurs and you can not explain where the file came from * then you should simply ignore the collision since there is not enough * information to determine if a real problem exists. Please do NOT file * a bug report at http://bugs.gentoo.org unless you report exactly which * two packages install the same file(s). See * http://wiki.gentoo.org/wiki/Knowledge_Base:Blockers for tips on how to * solve the problem. And once again, please do NOT file a bug report * unless you have completely understood the above message. * * Detected file collision(s): * * /usr/share/locale/nl/LC_MESSAGES/org.kde.kteatime.appdata.mo * * Searching all installed packages for file collisions... * * Press Ctrl-C to Stop * * kde-apps/kde-l10n-15.08.3:5::gentoo * /usr/share/locale/nl/LC_MESSAGES/org.kde.kteatime.appdata.mo * * Package 'kde-apps/kde4-l10n-15.08.3-r1' NOT merged due to file * collisions. If necessary, refer to your elog messages for the whole * content of the above message. * Messages for package kde-apps/kde4-l10n-15.08.3-r1: * This package will overwrite one or more files that may belong to other * packages (see list below). You can use a command such as `portageq * owners / <filename>` to identify the installed package that owns a * file. If portageq reports that only one package owns a file then do * NOT file a bug report. A bug report is only useful if it identifies at * least two or more packages that are known to install the same file(s). * If a collision occurs and you can not explain where the file came from * then you should simply ignore the collision since there is not enough * information to determine if a real problem exists. Please do NOT file * a bug report at http://bugs.gentoo.org unless you report exactly which * two packages install the same file(s). See * http://wiki.gentoo.org/wiki/Knowledge_Base:Blockers for tips on how to * solve the problem. And once again, please do NOT file a bug report * unless you have completely understood the above message. * * Detected file collision(s): * * /usr/share/locale/nl/LC_MESSAGES/org.kde.kteatime.appdata.mo * * Searching all installed packages for file collisions... * * Press Ctrl-C to Stop * * kde-apps/kde-l10n-15.08.3:5::gentoo * /usr/share/locale/nl/LC_MESSAGES/org.kde.kteatime.appdata.mo * * Package 'kde-apps/kde4-l10n-15.08.3-r1' NOT merged due to file * collisions. If necessary, refer to your elog messages for the whole * content of the above message. * GNU info directory index is up-to-date.

Also available in: Atom PDF

Thank you!