| Summary: | portage 2.0.4 errors doing updates | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Mark Guertin <mguertin> |
| Component: | Current packages | Assignee: | Daniel Robbins (RETIRED) <drobbins> |
| Status: | RESOLVED FIXED | ||
| Severity: | major | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
Will be fixed in the next (after 2.0.4) portage release. |
Twice now today I hve had this problem while doing emerge -u. The first one was with gnome2, this one pasted below was doing -u world. It seems that the second pkg in the update fails right away (no deps file exists). If you rerun it works perfectly the second time. Snippet below: >>> emerge sys-devel/autoconf-2.53a to / Traceback (most recent call last): File "/usr/bin/emerge", line 1231, in ? mydepgraph.display(mydepgraph.altlist()) File "/usr/bin/emerge", line 610, in merge retval=portage.doebuild(y,"merge",myroot,edebug) File "/usr/lib/python2.2/site-packages/portage.py", line 1058, in doebuild returnme.append(mysplit[0]) IOError: [Errno 2] No such file or directory: '/var/cache/edb/dep/dep-autoconf-2.53a.ebuild'