Summary: | fuse ebuild 0.6.1.1 gtk conditional dependency causes emerge -uD world to crash when installed on portage 2.0.50 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Paul Robson <autismuk> |
Component: | Current packages | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED FIXED | ||
Severity: | major | CC: | ooblick, stelu |
Priority: | High | Keywords: | InVCS |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Paul Robson
2004-02-17 01:40:00 UTC
Error report is : Traceback (most recent call last): File "/usr/bin/emerge", line 2520, in ? if not mydepgraph.xcreate(myaction): File "/usr/bin/emerge", line 1138, 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,myuse=myuse) File "/usr/lib/portage/pym/portage.py", line 3309, in dep_check mylist=flatten(dep_listcleanup(dep_zapdeps(mysplit,mysplit2))) File "/usr/lib/portage/pym/portage.py", line 3052, in dep_zapdeps myresult=dep_zapdeps(unreduced[x],reduced[x]) File "/usr/lib/portage/pym/portage.py", line 3019, in dep_zapdeps if not mydbapi.match(y): File "/usr/lib/portage/pym/portage.py", line 4138, in match mydep=dep_expand(origdep,self,use_cache=use_cache) File "/usr/lib/portage/pym/portage.py", line 3255, in dep_expand elif mydep[:1] in "=<>~!": TypeError: 'in <string>' requires string as left operand Clarification of original statement. portage-rescue does work in that the problem disappears and emerge -upD works again *but* the problem returns after updating again. (tried this twice). Fixed in cvs. *** Bug 40697 has been marked as a duplicate of this bug. *** *** Bug 45688 has been marked as a duplicate of this bug. *** I just faced this problem yesterday, having been on portage 2.0.50 for a while now; funny. Is the proposed solution to upgrade to the unstable portage version? Bug has been fixed and released in stable portages on or before 2.0.51-r2 |