Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 250445 - File collisions between libkworkspace-9999, libtaskmanager-9999, solid-9999
Summary: File collisions between libkworkspace-9999, libtaskmanager-9999, solid-9999
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] KDE (show other bugs)
Hardware: x86 Linux
: High normal (vote)
Assignee: Gentoo KDE team
URL: http://rafb.net/p/yy7qGM48.html
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-12-09 21:46 UTC by Luís Costa
Modified: 2008-12-29 14:43 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Luís Costa 2008-12-09 21:46:15 UTC
I'm rebuilding kde4-live at the moment and I'm getting a few file collisions between libkworkspace, solid and libtaskmanager. There might be other packages colliding, but the emerge process isn't finished yet. I'll update in case I find new ones. 

Here is the build log from solid-9999:

* Detected file collision(s):                                                    
 *                                                                                
 *      /usr/kde/live/lib/KDE4Workspace/cmake/KDE4WorkspaceLibraryTargets-release.cmake                                                                                   
 *      /usr/kde/live/lib/KDE4Workspace/cmake/KDE4WorkspaceConfig.cmake              
 *      /usr/kde/live/lib/KDE4Workspace/cmake/KDE4WorkspaceLibraryTargets.cmake      
 *                                                                                   
 * Searching all installed packages for file collisions...                           
 *                                                                                   
 * Press Ctrl-C to Stop                                                              
 *                                                                                   
 * kde-base/libtaskmanager-9999                                                      
 *      /usr/kde/live/lib/KDE4Workspace/cmake/KDE4WorkspaceConfig.cmake              
 *      /usr/kde/live/lib/KDE4Workspace/cmake/KDE4WorkspaceLibraryTargets-release.cmake                                                                                   
 *      /usr/kde/live/lib/KDE4Workspace/cmake/KDE4WorkspaceLibraryTargets.cmake      
 *                                                                                   
 * kde-base/libkworkspace-9999                                                       
 *      /usr/kde/live/lib/KDE4Workspace/cmake/KDE4WorkspaceConfig.cmake              
 *      /usr/kde/live/lib/KDE4Workspace/cmake/KDE4WorkspaceLibraryTargets-release.cmake                                                                                   
 *      /usr/kde/live/lib/KDE4Workspace/cmake/KDE4WorkspaceLibraryTargets.cmake   

I was able to circunvent the collisions by removing the files manually. It seems that all three packages "own" those files but, once I removed manually, they all compiled fine.

EDIT#1: kde-base/kscreensaver-9999 is also colliding with the other packages. Same files.

Reproducible: Always

Steps to Reproduce:
Comment 1 Luís Costa 2008-12-09 21:56:36 UTC
I don't know if it this is related, but kde-base/ksplash-9999, kde-base/kephal-9999, kde-base/kcminit-9999, kde-base/ksmserver-9999, kde-base/kstartupconfig-9999, are all getting this cmake error: "CMake Error: INSTALL(EXPORT) given unknown export "kdeworkspaceLibraryTargets""

kde-base/ksysguard-9999, kde-base/libplasmaclock-9999 are also having file collisions. I'll stop the merge now, since I want kde4 to remain usable.
Comment 2 eirik finvold 2008-12-28 17:03:14 UTC
(In reply to comment #1)
> I don't know if it this is related, but kde-base/ksplash-9999,
> kde-base/kephal-9999, kde-base/kcminit-9999, kde-base/ksmserver-9999,
> kde-base/kstartupconfig-9999, are all getting this cmake error: "CMake Error:
> INSTALL(EXPORT) given unknown export "kdeworkspaceLibraryTargets""
> 
> kde-base/ksysguard-9999, kde-base/libplasmaclock-9999 are also having file
> collisions. I'll stop the merge now, since I want kde4 to remain usable.
> 

Any news on this? Still having this problem with "given unknown export kdeworkspaceLibraryTargets"...
Comment 3 eirik finvold 2008-12-28 17:25:06 UTC
> Any news on this? Still having this problem with "given unknown export
> kdeworkspaceLibraryTargets"...
> 
Some additional info that may help:

XXXX ~/ # portageq owners / /usr/lib64/KDE4Workspace-4.2.0/cmake/KDE4WorkspaceLibraryTargets-release.cmake
kde-base/libkworkspace-9999
        /usr/lib64/KDE4Workspace-4.2.0/cmake/KDE4WorkspaceLibraryTargets-release.cmake
kde-base/solid-9999
        /usr/lib64/KDE4Workspace-4.2.0/cmake/KDE4WorkspaceLibraryTargets-release.cmake


As you can see, both libkworkspace and solid wants to own the files in /usr/lib64/KDE4Workspace-4.2.0/cmake/ folder. The two KDE4WorkspaceLibrary*.cmake files in this folder are not equal in solid and libkworkspace..
Comment 4 Luís Costa 2008-12-28 18:45:49 UTC
I haven't seen that error for over two weeks. I forgot to come back here and report the situation as fixed (at least for me). Are you sure you synced the kde-crazy tree recently? also, try removing the file in question and recompile kde4-live again.
Comment 5 eirik finvold 2008-12-28 19:11:35 UTC
(In reply to comment #4)
> I haven't seen that error for over two weeks. I forgot to come back here and
> report the situation as fixed (at least for me). Are you sure you synced the
> kde-crazy tree recently? also, try removing the file in question and recompile
> kde4-live again.
> 

Tried that many times. When I get a collision, I delete the /usr/lib64/KDE3Workspace folder, and do a "emerge --resume", it will then successfully compile solid, but when the next package (ksplash) is beginning I get the "give unknown export" error.

Did it again a couple of hours ago:
emerge -C @kdebase-live
qlist -I kde
emerge -C "everything from qlist -I kde output"
emerge --sync
layman -S
emerge @kdebase-live

Getting this on two of my amd64 machines..
Comment 6 eirik finvold 2008-12-29 10:09:09 UTC
> Tried that many times. When I get a collision, I delete the
> /usr/lib64/KDE3Workspace folder, and do a "emerge --resume", it will then
> successfully compile solid, but when the next package (ksplash) is beginning I
> get the "give unknown export" error.
> 
> Did it again a couple of hours ago:
> emerge -C @kdebase-live
> qlist -I kde
> emerge -C "everything from qlist -I kde output"
> emerge --sync
> layman -S
> emerge @kdebase-live
> 
> Getting this on two of my amd64 machines..

Problem solved! Seems that layman has changed path for overlays, from /usr/portage/local/layman to /usr/local/portage/layman, the last couple of weeks. Because of that, I got two kde-crazy folders, and my make.conf pointed at the oldest one. 
This did the trick:
layman -d kde-crazy
rm -R /usr/portage/local/layman/kde-crazy
change the source-line in /etc/make.conf
layman -a kde-crazy
Comment 7 Theo Chatzimichos (RETIRED) archtester gentoo-dev Security 2008-12-29 10:31:02 UTC
eirik your comment seems too odd to be true :)
i'll perform a full recompile today and give you the results
Comment 8 Theo Chatzimichos (RETIRED) archtester gentoo-dev Security 2008-12-29 14:43:22 UTC
no collisions here so the problem was somewhere else :) Upstream already fixed it