4860 – emerge broken after emerge -u world and emerge clean (2.0.11)

Bug 4860 - emerge broken after emerge -u world and emerge clean (2.0.11)

Summary: emerge broken after emerge -u world and emerge clean (2.0.11)

Status:	RESOLVED FIXED

Alias:	None

Product:	Portage Development
Classification:	Unclassified
Component:	Unclassified (show other bugs)
Hardware:	All Linux

Importance:	High normal (vote)
Assignee:	Daniel Robbins (RETIRED)

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2002-07-11 07:55 UTC by Alexander Holler
Modified:	2011-10-30 22:20 UTC (History)
CC List:	0 users

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Alexander Holler 2002-07-11 07:55:37 UTC

I've just done an emerge -u portage (to 2.0.11), emerge -u world and an 
afterwards an emerge clean.  
Now I'm getting this on every emerge ...:  
!!! Invalid token (not "=") mein  
Traceback (most recent call last):  
  File "/usr/bin/emerge", line 2, in ?  
    import os,sys,portage,xpak,string,re,commands,time,threading,grp  
  File "/usr/lib/python2.2/site-packages/portage.py", line 3750, in ?  
    settings=config()  
  File "/usr/lib/python2.2/site-packages/portage.py", line 648, in __init__  
    useorder=self["USE_ORDER"]  
  File "/usr/lib/python2.2/site-packages/portage.py", line 714, in __getitem__  
    if x.has_key(mykey):  
AttributeError: 'NoneType' object has no attribute 'has_key'

Comment 1 Alexander Holler 2002-07-11 19:27:19 UTC

Found it by myself. I've forgotten a # bevor that 'mein' and stumbled over  
the error message.