Refer to "Steps to Reproduce" Reproducible: Always Steps to Reproduce: 1. emerge -v okteta (triggers update of kdelibs) 2. wait for kdelibs-4.3.5 to finish compile and install and begin merge 3. This also happens when I do an emerge /usr/portage/kde-base/kdelibs/kdelibs-4.3.5.ebuild merge Actual Results: - emerge (or ebuild) reports package collisions for huge numbers of files, all under /usr/share/doc/kdelibs-4.3.5/HTML/en/kdelibs-apidox - emerge (or ebuild) puts out a message stating "Searching all installed packages for file collisions..." - a python2.6 process is running using a CPU 100% of the time - wait for about an hour and it's still going (Ctrl-C will stop the emerge) Expected Results: Not sure whether I should expect the package collisions to begin with. Definitely merge should complete within an hour (after compile and install are done)
Created attachment 218323 [details] emerge info emerge --info
You might have some circular symlink in there. In general, /usr/share/doc/kde-*/HTML/${LANG} tended to be completely broken with KDE3. Can't check with KDE4 as I don't use KDE any more.
File collision with what package? This is with USE="doc" enabled? Also such hanging could be any of... bad memory, corrupted file system :-/
(In reply to comment #3) > File collision with what package? I think that's exactly what it's spinning on the CPU to try to find out. It sees files already on the file system and is trying to find out which package it belongs to. In this case, I think there was a previous installation the failed due to the /usr filling up. Then I grew the file system (lvextend and resize_reiserfs) and ran the install again. So I think the end result is that it should have found no packages claiming to own those files and then installed over them. >This is with USE="doc" enabled? Also such yes > hanging could be any of... bad memory, corrupted file system :-/ > I don't think that's likely. By the way, I worked around this problem somehow. I don't remember whether I updated portage, hand-deleted all the files or what. So I can't reproduce it or provide any more data. I do think it's a valid bug though.
Closing since we don't really have enough info on what happens...
