I tried to emerge the XFS-sources five times and I get varios errors. Sometimes the patches won't be applied "Error, already exists" and sometimes applying patches works, but then I get a "xfs-sources-2.4.20.tbz2 not found". Already tried do delete sources completely (looks like an emerge unmerge xfs- sources isn't enough to deinstall the whole source tree) and reemerging them - no solution. The interesting thing is, that I already emerged them successfully, I even have a kernel built with those sources. But I had a system crash and I am using XFS, the Kernel-Config file was scrambled (or deleted?) and I had to reemerge them. As I already said, I have a working kernel here, and for an extreme emergency, I still have a working gentoo-sources-2.4.19-r5-Kernel here, so I won't in big trouble. Might be that this Bug is related to something else than the sources itself, but I have no idea to what. Reproducible: Always Steps to Reproduce: 1.emerge xfs-sources 2. 3. Actual Results: emerge fails while applying patches Expected Results: emerge should create working sources and put them in /usr/src Will do this tonite - I am on work here and enjoying my lunchbreak ;)
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.
