Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 578010

Summary: [kde overlay] kde-plasma/plasma-desktop-5.6.0 file collision with kde-plasma/kactivitymanagerd-5.6.0
Product: Gentoo Linux Reporter: Marco Napetti <marco.napetti>
Component: [OLD] KDEAssignee: Gentoo KDE team <kde>
Status: RESOLVED FIXED    
Severity: normal CC: fabio.coatti, gentoo, thomas.masper
Priority: Normal    
Version: unspecified   
Hardware: All   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---

Description Marco Napetti 2016-03-22 17:47:44 UTC 
When upgrading kde-plasma/plasma-desktop from version 5.5.5 to 5.6.0, 

 * checking 487 files for package collisions
 * 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/it/LC_MESSAGES/kactivities5.mo
 * 
 * Searching all installed packages for file collisions...
 * 
 * Press Ctrl-C to Stop
 * 
 * kde-plasma/kactivitymanagerd-5.6.0:5::kde
 *      /usr/share/locale/it/LC_MESSAGES/kactivities5.mo
 * 
 * Package 'kde-plasma/plasma-desktop-5.6.0' NOT merged due to file
 * collisions. If necessary, refer to your elog messages for the whole
 * content of the above message.