1640 – portage 1.8.19 borken with a trace back error

Bug 1640 - portage 1.8.19 borken with a trace back error

Summary: portage 1.8.19 borken with a trace back error

Status:	RESOLVED FIXED

Alias:	None

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

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

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2002-04-10 03:23 UTC by Chris Arndt
Modified:	2011-10-30 22:22 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 Chris Arndt 2002-04-10 03:23:31 UTC

updated to portage 1.8.19, and now i can't emerge any packages.
this happens for all ebuilds, and here is an example for portage.
also this happens with our without --pretend



# emerge sys-apps/portage --pretend

These are the packages that I would merge, in order.

Calculating dependencies \Traceback (most recent call last):
  File "/usr/sbin/emerge", line 1309, in ?
    mydepgraph.create(mytype+" "+portage.root+" "+mykey,None,"--onlydeps" not in
myopts)
  File "/usr/sbin/emerge", line 400, in create
    mydb=open(mydbkey,"r")
IOError: [Errno 2] No such file or directory:
'/var/cache/edb/dep/dep-portage-1.8.19.ebuild'

Comment 1 Chris Arndt 2002-04-10 06:48:39 UTC

doing the follwing fixes the problem

mkdir /var/cache/edb/dep


thanks to verwilst and bevin for pointing this out.