Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 47280 - Updating Portage cache fails: no such file or directory
Summary: Updating Portage cache fails: no such file or directory
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: x86 Linux
: High normal (vote)
Assignee: Gentoo X packagers
URL:
Whiteboard:
Keywords:
: 47279 47281 (view as bug list)
Depends on:
Blocks:
 
Reported: 2004-04-08 16:02 UTC by Marc Raphael
Modified: 2004-04-08 16:38 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Marc Raphael 2004-04-08 16:02:58 UTC
>>> Updating Portage cache... //usr/sbin/ebuild.sh: line 1098: /usr/portage/eclass/kmod.eclass: No such file or directory

!!! ERROR: x11-base/xfree-drm-4.3.0-r8 failed.
!!! Function inherit, Line 1099, Exitcode 1
!!! died sourcing /usr/portage/eclass/kmod.eclass in inherit()


aux_get(): (0) Error in x11-base/xfree-drm-4.3.0-r8 ebuild. (1)
               Check for syntax error or corruption in the ebuild. (--debug)


Failed cache update: x11-base/xfree-drm-4.3.0-r8
  ...done!
 
==============================================================================
same error on two gentoo boxes
there is no file /var/cache/edb/dep/x11-base/xfree-drm-4.3.0-r8
Comment 1 Marius Mauch (RETIRED) gentoo-dev 2004-04-08 16:08:45 UTC
Battousai: "in-development" version as x86 ??
Comment 2 Marius Mauch (RETIRED) gentoo-dev 2004-04-08 16:15:03 UTC
*** Bug 47279 has been marked as a duplicate of this bug. ***
Comment 3 Marius Mauch (RETIRED) gentoo-dev 2004-04-08 16:15:46 UTC
nevermind, didn't have the latest package.mask and Donnie fixed it anyway
Comment 4 Donnie Berkholz (RETIRED) gentoo-dev 2004-04-08 16:32:46 UTC
Fixed in CVS as of 23:08 UTC.
Comment 5 Donnie Berkholz (RETIRED) gentoo-dev 2004-04-08 16:38:35 UTC
*** Bug 47281 has been marked as a duplicate of this bug. ***