| View previous topic :: View next topic |
| Author |
Message |
Jean C.
Guest
|
 Posted: Thu May 02, 2002 3:19 am Post subject: Emerge error |
 |
|
Please help. Today when I went to use emerge I got the following error message.
!!! Invalid token (not "=") SYNC
Traceback (most recent call last):
File "/usr/bin/emerge", line 6, in ?
import output
File "/usr/lib/python2.2/site-packages/output.py", line 4, in ?
import portage;
File "/usr/lib/python2.2/site-packages/portage.py", line 3193, in ?
db["/"]["porttree"]=portagetree("/",virts)
File "/usr/lib/python2.2/site-packages/portage.py", line 2375, in __init__
self.portroot=settings["PORTDIR"]
File "/usr/lib/python2.2/site-packages/portage.py", line 631, in __getitem__
self.populate()
File "/usr/lib/python2.2/site-packages/portage.py", line 620, in populate
useorder=self["USE_ORDER"]
File "/usr/lib/python2.2/site-packages/portage.py", line 638, in __getitem__
if x.has_key(mykey):
AttributeError: 'NoneType' object has no attribute 'has_key'
I have no idea happened or how to fix it. I have been trying to fix things that broke when I did a system update a day or so ago. Everything is now working except "localhost" . I know I didn't touch any of the above files or emerge itself.  |
|
| Back to top |
|
 |
Malakin
Veteran
Joined: 14 Apr 2002
Posts: 1692
Location: Victoria BC Canada
|
| Posted: Thu May 02, 2002 7:44 am Post subject: |
|
|
Well I suppose to state the obvious, that's python having the errors, so did you try something like this?
"emerge rsync"
"emerge portage"
"emerge python"
and see if it still happens. |
|
| Back to top |
|
|
Jean C.
Guest
|
| Posted: Thu May 02, 2002 12:45 pm Post subject: Emerge Error |
|
|
I can't do "emerge rsync" because I get the error quoted in the first post.
Jean |
|
| Back to top |
|
|
Jean C
Guest
|
| Posted: Thu May 02, 2002 2:50 pm Post subject: Emerge error |
|
|
I solved the problem by using the answer to another post - which was reading README.RESCUE in /usr/portage/sys-apps/portage/files/, and following instructions. Emerge works again.
Jean
 |
|
| Back to top |
|
|
chadh
Moderator
Joined: 21 Apr 2002
Posts: 137
Location: Atlanta, GA
|
| Posted: Thu May 02, 2002 3:38 pm Post subject: |
|
|
For future reference the problem was most certainly either a typo in your /etc/make.conf, or somehow you got a make.conf from a version of portage more recent than you were actually running.
_________________
Chad |
|
| Back to top |
|
|
Stalione
Guru
Joined: 21 Apr 2002
Posts: 335
|
| Posted: Thu May 02, 2002 5:41 pm Post subject: New problem |
|
|
I get the following output after I followed the README.RESCUE .
| Quote: |
t-rex files # tar xjpUvf portage-rescue-1.8.19.tbz2 -C /
etc/
tar: etc: Cannot unlink: Directory not empty
etc/make.globals
etc/make.conf
usr/
tar: usr: Cannot unlink: Device or resource busy
usr/lib/
tar: usr/lib: Cannot unlink: Directory not empty
usr/lib/python2.2/
tar: usr/lib/python2.2: Cannot unlink: Directory not empty
usr/lib/python2.2/site-packages/
tar: usr/lib/python2.2/site-packages: Cannot unlink: Directory not empty
usr/lib/python2.2/site-packages/missingos.so
usr/lib/python2.2/site-packages/xpak.py
usr/lib/python2.2/site-packages/portage.py
usr/lib/python2.2/site-packages/output.py
usr/lib/python2.2/site-packages/output.pyc
usr/lib/python2.2/site-packages/portage.pyc
usr/lib/python2.2/site-packages/xpak.pyc
usr/lib/python2.2/site-packages/output.pyo
usr/lib/python2.2/site-packages/portage.pyo
usr/lib/python2.2/site-packages/xpak.pyo
usr/lib/portage/
tar: usr/lib/portage: Cannot unlink: Directory not empty
usr/lib/portage/bin/
tar: usr/lib/portage/bin: Cannot unlink: Directory not empty
usr/lib/portage/bin/chkcontents
usr/lib/portage/bin/db-update.py
usr/lib/portage/bin/dobin
usr/lib/portage/bin/dodir
usr/lib/portage/bin/dodoc
usr/lib/portage/bin/doexe
usr/lib/portage/bin/dohard
usr/lib/portage/bin/dohtml
usr/lib/portage/bin/doinfo
usr/lib/portage/bin/doins
usr/lib/portage/bin/dojar
usr/lib/portage/bin/dolib
usr/lib/portage/bin/dolib.a
usr/lib/portage/bin/dolib.so
usr/lib/portage/bin/doman
usr/lib/portage/bin/domo
usr/lib/portage/bin/dopython
usr/lib/portage/bin/dosbin
usr/lib/portage/bin/dosed
usr/lib/portage/bin/dosym
usr/lib/portage/bin/ebuild
usr/lib/portage/bin/ebuild.sh
usr/lib/portage/bin/emake
usr/lib/portage/bin/emerge
usr/lib/portage/bin/env-update
usr/lib/portage/bin/find-packages
usr/lib/portage/bin/find-requires
usr/lib/portage/bin/fowners
usr/lib/portage/bin/fperms
usr/lib/portage/bin/megadigest
usr/lib/portage/bin/megadownload
usr/lib/portage/bin/megatouch
usr/lib/portage/bin/newbin
usr/lib/portage/bin/newdoc
usr/lib/portage/bin/newexe
usr/lib/portage/bin/newins
usr/lib/portage/bin/newlib.a
usr/lib/portage/bin/newlib.so
usr/lib/portage/bin/newman
usr/lib/portage/bin/newsbin
usr/lib/portage/bin/pdb
usr/lib/portage/bin/pdb.cgi
usr/lib/portage/bin/pkglist
usr/lib/portage/bin/pkgmerge
usr/lib/portage/bin/pkgmerge.new
usr/lib/portage/bin/pkgname
usr/lib/portage/bin/pkgsearch
usr/lib/portage/bin/prepall
usr/lib/portage/bin/prepalldocs
usr/lib/portage/bin/prepallinfo
usr/lib/portage/bin/prepallman
usr/lib/portage/bin/prepallstrip
usr/lib/portage/bin/prepinfo
usr/lib/portage/bin/preplib
usr/lib/portage/bin/preplib.so
usr/lib/portage/bin/prepman
usr/lib/portage/bin/prepstrip
usr/lib/portage/bin/queryhost.sh
usr/lib/portage/bin/quickpkg
usr/lib/portage/bin/use
usr/lib/portage/bin/xpak
usr/lib/portage/bin/pmake
usr/lib/portage/bin/tbz2tool
usr/lib/portage/bin/sandbox
usr/lib/portage/bin/donewins
usr/lib/portage/lib/
tar: usr/lib/portage/lib: Cannot unlink: Directory not empty
usr/lib/portage/lib/libsandbox.so
usr/lib/portage/lib/sandbox.bashrc
usr/bin/
tar: usr/bin: Cannot unlink: Directory not empty
usr/bin/emerge
usr/bin/xpak
usr/bin/tbz2tool
usr/sbin/
tar: usr/sbin: Cannot unlink: Directory not empty
usr/sbin/pkgmerge
usr/sbin/ebuild
usr/sbin/ebuild.sh
usr/sbin/env-update
usr/share/
tar: usr/share: Cannot unlink: Directory not empty
usr/share/man/
tar: usr/share/man: Cannot unlink: Directory not empty
usr/share/man/man1/
tar: usr/share/man/man1: Cannot unlink: Directory not empty
usr/share/man/man1/chkcontents.1.gz
usr/share/man/man1/ebuild.1.gz
usr/share/man/man1/emerge.1.gz
usr/share/man/man1/pkglist.1.gz
usr/share/man/man1/pkgsearch.1.gz
usr/share/man/man5/
tar: usr/share/man/man5: Cannot unlink: Directory not empty
usr/share/man/man5/ebuild.5.gz
usr/share/man/man5/make.conf.5.gz
usr/share/man/man5/make.defaults.5.gz
usr/share/doc/
tar: usr/share/doc: Cannot unlink: Directory not empty
usr/share/doc/portage-1.8.19/
tar: usr/share/doc/portage-1.8.19: Cannot unlink: Directory not empty
usr/share/doc/portage-1.8.19/ChangeLog.gz
bzip2: (stdin): trailing garbage after EOF ignored
var/
tar: var: Cannot unlink: Directory not empty
var/tmp/
tar: var/tmp: Cannot unlink: Directory not empty
var/tmp/.keep
tar: Error exit delayed from previous errors
t-rex files # emerge --pretend gaim
These are the packages that I would merge, in order.
Calculating dependencies \Traceback (most recent call last):
File "/usr/bin/emerge", line 1309, in ?
mydepgraph.create(mytype+" "+portage.root+" "+mykey,None,"--onlydeps" not in myopts)
File "/usr/bin/emerge", line 400, in create
mydb=open(mydbkey,"r")
IOError: [Errno 2] No such file or directory: '/var/cache/edb/dep/dep-gaim-0.57.ebuild'
t-rex files #
|
I also tried to do emerge --clean and then emerge rsyn but still i get the same error. Did i screw up?? |
|
| Back to top |
|
|
Jean C
Guest
|
| Posted: Thu May 02, 2002 8:03 pm Post subject: Emerge error |
|
|
Thank you Chad. It probably got mixed up when I got the "2 config files need updating" message. I have since installed the gentoolkit, for etc-update - which makes it easier to deal with figuring out what to ditch and what to keep.
Jean C. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Portage & Programming
