Summary: | Emerging of xfs-sources-2.4.20-r2 fails | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Benjamin Judas (RETIRED) <beejay> |
Component: | [OLD] Core system | Assignee: | Nicholas Jones (RETIRED) <carpaski> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | ||
Priority: | High | ||
Version: | 1.4_rc2 | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Benjamin Judas (RETIRED)
2003-03-25 07:13:03 UTC
Ok - This is _not_ an error of those sources -- in fact it's a portage problem -- looks like Portage is looking for something which doesn't exist. I experienced the same while trying to update glibc: Traceback (most recent call last): File "/usr/lib/portage/bin/xpak", line 11, in ? xpak.xpak(sys.argv[1],sys.argv[2]) File "/usr/lib/python2.2/site-packages/xpak.py", line 32, in xpak os.chdir(rootdir) OSError: [Errno 2] No such file or directory: 'build-info' tbz2tool: inf.xpak doesn't exist mv: Aufruf von stat f Ok - This is _not_ an error of those sources -- in fact it's a portage problem -- looks like Portage is looking for something which doesn't exist. I experienced the same while trying to update glibc: Traceback (most recent call last): File "/usr/lib/portage/bin/xpak", line 11, in ? xpak.xpak(sys.argv[1],sys.argv[2]) File "/usr/lib/python2.2/site-packages/xpak.py", line 32, in xpak os.chdir(rootdir) OSError: [Errno 2] No such file or directory: 'build-info' tbz2tool: inf.xpak doesn't exist mv: Aufruf von stat für »glibc-2.3.1-r4.tbz2« nicht mö glich: Datei oder Verzeichnis nicht gefunden //rem : Means "File or Directory not found" >>> Done. Traceback (most recent call last): File "/usr/bin/emerge", line 1862, in ? mydepgraph.merge(mydepgraph.altlist()) File "/usr/bin/emerge", line 1122, in merge retval=portage.pkgmerge(mytbz2,myroot) File "/usr/lib/python2.2/site-packages/portage.py", line 4241, in pkgmerge mycat=xptbz2.getfile("CATEGORY") File "/usr/lib/python2.2/site-packages/xpak.py", lin e 183, in getfile self.scan() File "/usr/lib/python2.2/site-packages/xpak.py", lin e 160, in scan a=open(self.file,"r") IOError: [Errno 2] No such file or directory: '/usr/portage/packages/All/glibc-2.3.1-r4.tbz2' Thanks to carpaski - workaround for this : removed buildpkg from FEATURES-list in /etc/make.conf no more problems for now, but I think that this is just a workaround, something has to be fixed here. What makes me curious is that portage-2.0.47-r10 worked all times, and suddenly - BANG! Got Portage back up and running - here is how I've done this: 1.) disabled buildpkg in make.conf 2.) reemerged the installed portage 3.) run regenworld 4.) run emerge sync 5.) enabled buildpkg in make.conf It seems now everything is like it was before. |