I don't know if it was > 40 config-files I rushed through way too quick, or the crash while compiling glibc, but everything portage-related is broken now :'-( Even env-update doesn't work anymore now, giving me this: Traceback (most recent call last): File "/usr/sbin/env-update", line 3, in ? import portage File "/usr/lib/python2.2/site-packages/portage.py", line 4040, in ? mtimedb["old"]=grabints(root+"var/cache/edb/mtimes") File "/usr/lib/python2.2/site-packages/portage.py", line 449, in grabints newdict[myline[0]]=string.atoi(myline[1]) File "/usr/lib/python2.2/string.py", line 220, in atoi return _int(s, base) ValueError: invalid literal for int(): PATH='/usr/local/bin:/opt/bin:/opt/modeltech/bin:/opt/intel/compiler60/ia32/bin:/opt/ICAClient:/opt/opera/bin:/opt/rar/bin:/opt/RealPlayer8:/usr/X11R6/bin:/opt/eclipse:/opt/sun-jdk-1.4.1_rc1/bin:/opt/ It looks like my PATH-variable is too big to handle ? Regards, Rigo
cd / tar -jxvf /usr/portage/sys-apps/portage/files/portage-rescue-2.0.43-x86.tbz2
Thanks for the tip Vapier (Very good to know the rescue-file is there =), but it doesn't work...When I use python direct (and import portage) it isn't working too (Could it be the _ or . in PATH ? Rigo
well try setting your PATH to a 'sane' value and then running emerge ... by 'sane' i mean: export PATH="/sbin:/bin:/usr/sbin:/usr/bin"
It seems that portage's using a different 'version' of PATH then I do :( echo $PATH gives a correct (sane =) setting though... Rigo
so setting the path to a 'sane' value did not fix the problem ?
Nope....I found out it reads the PATH in var/cache/edb/mtimes, and then crashes. Changing the PATH-variable overthere gives me the same error....
delete it. Post your whole path, if it's still a problem. (Line wrap it too)
Sigh, that I didn't try that before.... Thanx a lot, Rigo
