Summary: | edb/dep/app-text/sablotron-0.60 causes emerge to die | ||
---|---|---|---|
Product: | Portage Development | Reporter: | SpanKY <vapier> |
Component: | Unclassified | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | All | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
SpanKY
2002-06-26 00:03:27 UTC
rux0r / # emerge sablotron Calculating dependencies Traceback (most recent call last): File "/usr/bin/emerge", line 1224, in ? mykey=portage.db[portage.root]["porttree"].dep_bestmatch(mypkg) File "/usr/lib/python2.2/site-packages/portage.py", line 2260, in dep_bestmatch mymatch=best(gvisible(visible(match(mydep,self.dbapi)))) File "/usr/lib/python2.2/site-packages/portage.py", line 2222, in gvisible myaux=db["/"]["porttree"].dbapi.aux_get(mycpv, ["KEYWORDS"]) File "/usr/lib/python2.2/site-packages/portage.py", line 2548, in aux_get mycent=open(mydbkey,"r") IOError: [Errno 2] No such file or directory: '/var/cache/edb/dep/app- text/sablotron-0.60' please check your /usr/portage/app-text/sablotron-0.60.ebuild I suspect that a bad rsync mirror (data loss) made it emit broken files . guess i should just have included this too [box w/out sablotron installed] rux0r root # ls -al /var/cache/edb/dep/app-text ls: /var/cache/edb/dep/app-text: No such file or directory [boxes w/sablotron installed] vapier root # ls -al /var/cache/edb/dep/app-text total 40 drwxr-xr-x 2 root root 4096 Jun 26 00:58 . drwxr-xr-x 43 root root 4096 Jun 24 17:33 .. -rw-r--r-- 1 root root 505 Jun 24 17:32 ghostscript-6.50-r2 -rw-r--r-- 1 root root 459 Jun 24 17:32 ghostscript-6.53-r1 -rw-r--r-- 1 root root 429 Jun 24 17:32 ghostscript-6.53-r2 -rw-r--r-- 1 root root 504 Jun 24 17:32 ghostscript-7.00 -rw-r--r-- 1 root root 503 Jun 24 17:32 ghostscript-7.05 -rw-r--r-- 1 root root 276 Jun 26 00:58 sablotron-0.52 -rw-r--r-- 1 root root 276 Jun 26 00:58 sablotron-0.81 -rw-r--r-- 1 root root 276 Jun 26 00:58 sablotron-0.90 home init.d # ls -al /var/cache/edb/dep/app-text total 20 drwxr-xr-x 2 root root 4096 Jun 24 21:43 . drwxr-xr-x 23 root root 4096 Jun 26 00:50 .. -rw-r--r-- 1 root root 276 Jun 24 21:43 sablotron-0.52 -rw-r--r-- 1 root root 276 Jun 24 21:43 sablotron-0.81 -rw-r--r-- 1 root root 276 Jun 24 21:43 sablotron-0.90 sorry spider, i misread your response ... i deleted the ebuild and did `emerge rsync` but the file wasnt replaced the previous emerge cmds did not fail ... do outdated ebuilds get punted from the portage tree after a time ? the cvs only shows sablotron 0.90 http://www.gentoo.org/cgi-bin/viewcvs.cgi/gentoo-x86/app-text/sablotron/ Yes, they are removed not too long after they are superceeded in version. emerge --clean rsync Will keep you in form with the current tree. Closing this bug as it is resolved. |