From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.43) id 1DtyX7-0006Ij-RW for garchives@archives.gentoo.org; Sun, 17 Jul 2005 02:05:34 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.4/8.13.4) with SMTP id j6H23d9p023715; Sun, 17 Jul 2005 02:03:39 GMT Received: from smtp15.wxs.nl (smtp15.wxs.nl [195.121.6.54]) by robin.gentoo.org (8.13.4/8.13.4) with ESMTP id j6H1vCVG025095 for ; Sun, 17 Jul 2005 01:57:12 GMT Received: from [10.0.0.150] (ip3e83ab52.speed.planet.nl [62.131.171.82]) by smtp15.wxs.nl (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004)) with ESMTP id <0IJR00K9G1G9QT@smtp15.wxs.nl> for gentoo-user@lists.gentoo.org; Sun, 17 Jul 2005 03:57:45 +0200 (CEST) Date: Sun, 17 Jul 2005 03:57:14 +0200 From: Holly Bostick Subject: Re: [gentoo-user] most of /usr/portage gone--why? and what now} In-reply-to: <1121556666.8138.25.camel@rattus.localdomain> To: gentoo-user@lists.gentoo.org Message-id: <42D9BAFA.2040003@planet.nl> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-15 Content-transfer-encoding: 7BIT X-Accept-Language: nl-NL, nl, en User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050624) X-Enigmail-Version: 0.92.0.0 References: <1121556666.8138.25.camel@rattus.localdomain> X-Archives-Salt: efbc44a6-b8e5-4195-8372-9cd91e7d8562 X-Archives-Hash: 63311dcd71a42d83ad2ea20ba6dcf8b2 William Kenworthy schreef: > If files have gone missing first step is fsck the disk just in case. > Next emerge sync if it works. (dont use the fancy options until its > working again.) Whats "esync" ?? I wouldnt trust it until you know > what happened. Esync is a part of gentoolkit-- it runs emerge sync and outputs or mails you the updated package list (new and upgradeable packages). It's really not dangerous in and of itself. Isn't what happened that the sync failed before it was able to import the new portage tree, but after it had removed the old one? I could be wrong-- although I've had several failures to sync in the past few days myself (but I didn't check /usr/portage afterwards, since I knew it would be borked, but it does support some kind of weird server issue), but it seems to me that all that's needed is a successful sync to re-populate the Portage tree. Afaics, this is one of those "head wound" kinda problems (bleeds a lot and looks very scary, but not as serious as it seems at first glance). But I could be mistaken. Holly -- gentoo-user@gentoo.org mailing list