I recently upgraded from portage-1.8.9.4 to 1.8.15, then 1.8.16. In both 1.8.15 and 1.8.16, i get the following output at the end of any emerge attempt: --begin output-- !!! Invalid token (not "=") PATH Traceback (most recent call last): File "/usr/sbin/emerge", line 1263, in ? mydepgraph.merge(mydepgraph.altlist()) File "/usr/sbin/emerge", line 569, in merge retval=portage.doebuild(y,"merge",myroot,edebug) File "/usr/lib/python2.2/site-packages/portage.py", line 1003, in doebuild return merge(settings["CATEGORY"],settings["PF"],settings["D"],settings["BUILDDIR"]+"/build-info",myroot,myebuild=settings["EBUILD"]) File "/usr/lib/python2.2/site-packages/portage.py", line 1258, in merge mylink.merge(pkgloc,infloc,myroot,myebuild) File "/usr/lib/python2.2/site-packages/portage.py", line 2991, in merge self.treewalk(mergeroot,myroot,inforoot,myebuild) File "/usr/lib/python2.2/site-packages/portage.py", line 2815, in treewalk env_update() File "/usr/lib/python2.2/site-packages/portage.py", line 244, in env_update if myconfig.has_key(myspec): AttributeError: 'NoneType' object has no attribute 'has_key' --end output-- The reason this is strange is because after emerge exits, the package seems to have merged successfully.
*** Bug 1536 has been marked as a duplicate of this bug. ***
You have a file in /etc/env.d that is causing a parsing error. Have you been modifying any files in there? If not, then we have a package on cvs that is installing incorrectly-formatted data in there.
I haven't touched anything in there. I could look at the files to see if there's anything out of the ordinary, but I don't know what to look for.
could you tar up your /etc/env.d directory and attach here or simply email it to me? (drobbins@gentoo.org)
Seemant: do you happen to know if karl has fixed his java-config and thus fixed this bug?
According to bug #1577 karl fixed this. And now java-config is at 0.2.2 with even more improvements, so I imagine this fix is in the relatively distant past.
<karltk> seemant: it might be that the newer portages barf of the java directory in env.d <karltk> seemant: ie, that it is a dir, not a file
Is this still an issue, by the way? Portage is at 1.8.19 for a while now.
All I can say is that since the bug was fixed in java-config, everything has been working fine for me.
Great