| Summary: | Loop In Portage? | ||
|---|---|---|---|
| Product: | Portage Development | Reporter: | Simon Watson <simon> |
| Component: | Unclassified | Assignee: | Daniel Robbins (RETIRED) <drobbins> |
| Status: | RESOLVED INVALID | ||
| Severity: | normal | CC: | simon, vapier |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
In order to fix this bug, I need the *full* traceback, not just a snippet. I'm guessing that it's due to some kind of circular symlink issue and an os.stat() call. Incomplete bug report, marking as invalid. |
When I emerge certain packages, the following message repeats itself over and over again: File "/usr/lib/python2.2/site-packages/portage.py", line 3609, in mergeme self.mergeme(srcroot,destroot,outfile,secondhand,offset+x+"/",cfgfiledict,thismtime) Then at the end it says: File "/usr/lib/python2.2/site-packages/portage.py", line 3558, in mergeme if S_ISLNK(mymode): File "/usr/lib/python2.2/stat.py", line 61, in S_ISLNK return S_IFMT(mode) == S_IFLNK RuntimeError: maximum recursion depth exceeded This appears to happen whenever I run emerge -e evolution, and sometimes with other applications. Also, I have lots of duplicate dependencies when I run emerge -ep evolution. e.g.: [ebuild N ] gnome-base/control-center-2.0.0 to / [ebuild N ] gnome-base/control-center-1.4.0.5-r1 to /