When ever i am running the following command i get error subbu-gentoo root # emerge -Up world >>> --upgradeonly implies --update... adding --update to options. These are the packages that I would merge, in order: Calculating world dependencies |Traceback (most recent call last): File "/usr/bin/emerge", line 2517, in ? if not mydepgraph.xcreate(myaction): File "/usr/bin/emerge", line 1135, in xcreate if not self.create(myk): File "/usr/bin/emerge", line 825, in create if not self.select_dep("/",mydep["/"],myparent=mp,myuse=myuse): File "/usr/bin/emerge", line 936, in select_dep mycheck=portage.dep_check(depstring,self.mydbapi[myroot],self.pkgsettings,my use=myuse) File "/usr/lib/portage/pym/portage.py", line 3292, in dep_check mysplit=dep_virtual(mysplit) File "/usr/lib/portage/pym/portage.py", line 2952, in dep_virtual for x in mysplit: TypeError: iteration over non-sequence Reproducible: Always Steps to Reproduce: 1. emerge -Up world 2. 3. Actual Results: >>> --upgradeonly implies --update... adding --update to options. These are the packages that I would merge, in order: Calculating world dependencies |Traceback (most recent call last): File "/usr/bin/emerge", line 2517, in ? if not mydepgraph.xcreate(myaction): File "/usr/bin/emerge", line 1135, in xcreate if not self.create(myk): File "/usr/bin/emerge", line 825, in create if not self.select_dep("/",mydep["/"],myparent=mp,myuse=myuse): File "/usr/bin/emerge", line 936, in select_dep mycheck=portage.dep_check(depstring,self.mydbapi[myroot],self.pkgsettings,my use=myuse) File "/usr/lib/portage/pym/portage.py", line 3292, in dep_check mysplit=dep_virtual(mysplit) File "/usr/lib/portage/pym/portage.py", line 2952, in dep_virtual for x in mysplit: TypeError: iteration over non-sequence
*** Bug 47145 has been marked as a duplicate of this bug. ***
How I solved this: 1) unmasking portage-2.0.50-r4 (adding =sys-apps/portage-2.0.50-r4 to /etc/portage/package.unmask) 2) emerge =portage-2.0.50-r4 3) emerge -p world 4) wait for a while (strange messages may appear) 5) Problem solved. Can anyone verify that using portage-2.0.50-r4 solves this?
The problem has been fixed in -r4. But -r4 is UNMASKED version now. It includes other fixes and some new features. You should know that if you use it.
*** Bug 47182 has been marked as a duplicate of this bug. ***
*** Bug 24695 has been marked as a duplicate of this bug. ***
*** Bug 47181 has been marked as a duplicate of this bug. ***
*** Bug 47225 has been marked as a duplicate of this bug. ***
I got this too after rsyncing last night, but rsyncing today made it go away.
If you can reproduce this with a stable version of portage, please re-open.
reproduced on sys-apps/portage-2.0.51.22-r2 on 2 different PC's, one ~x86 and one x86.
Fixed! After an update of I think, shadow, the default PATH after su'ing was set to /bin:/usr/bin:/usr/ucb:/usr/local/bin After adding /usr/sbin to the path variable, portage worked fine again.
