From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1PjOfr-0005Zc-Qq for garchives@archives.gentoo.org; Sun, 30 Jan 2011 04:14:04 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id CB55EE06AF; Sun, 30 Jan 2011 04:12:34 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id 81F97E06AF for ; Sun, 30 Jan 2011 04:12:34 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp.gentoo.org (Postfix) with ESMTP id D78201B4003 for ; Sun, 30 Jan 2011 04:12:33 +0000 (UTC) X-Virus-Scanned: by amavisd-new using ClamAV at gentoo.org X-Spam-Score: -2.562 X-Spam-Level: X-Spam-Status: No, score=-2.562 required=5.5 tests=[AWL=0.037, BAYES_00=-2.599] Received: from smtp.gentoo.org ([127.0.0.1]) by localhost (smtp.gentoo.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7JqG9MM6upF3 for ; Sun, 30 Jan 2011 04:12:27 +0000 (UTC) Received: from web39302.mail.mud.yahoo.com (web39302.mail.mud.yahoo.com [66.94.238.169]) by smtp.gentoo.org (Postfix) with SMTP id 63FD31B4045 for ; Sun, 30 Jan 2011 04:12:27 +0000 (UTC) Received: (qmail 37563 invoked by uid 60001); 30 Jan 2011 04:12:26 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1296360746; bh=UgulrRq9Y82mN0rSMfl4eXhqAh0dQiFD23Ov0qsM1F8=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type; b=y4siBNUlgcVPnWCJQPjgOLLWWgx65uD58wuKrp32uQPA6fETQFxSGdIinryXMhelbiuZvG8vw1uKg8LqS1xKu0QpMnk58MkZS4wI3H63CnIkjKngKPIXC+GccV949WFjGMQhBQMhJJ4cfp0MHz+Zp37bJ3RBIp0RVLpXEPXrWVs= DomainKey-Signature:a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type; b=pv2LcxwiGzCeyQbtbA+l8kQGCC7uN6svrOVzxofgWIG4RQ32jGF2CcykRcu0mG3BlbB/blux46TyOTqQ4yhWQUkIjQMPZOGB/BhHslvxUl6kZNeGOvU4WvPFj3UQ3WVy03M0EM815PyR5BIOsjl0bJkC7iCVPHXlrHlKnFROZQg=; Message-ID: <222344.36123.qm@web39302.mail.mud.yahoo.com> X-YMail-OSG: 2bre8SMVM1kUujF59nlQ1MOSxo9T29pYklq.2jEYJMXObKR soIddRi_f1gy_8_TEDHDQDLjP0WS08baYLlJs2xHm.1k15_VPALZ2p.3D.AX R1RRb_jt5M6kNh33.pb11Y59gT.zBPFPpz75mmb9gSVQgZeRqDeon7CHvfsg aKlvO7xq2_GcqOsRtPoC8GTAzlCCItoyoMSeNGM1U5wj0czDVB3gqOxoy2zP gNGc87P47KOaPUV778y_bdlYw514_dcPoIQYSvyocf5VjlOtr77pPV6oxD1R Txd9Q2uqB6IjIJVDBomZdImaAqc_vmxjXthiC.d4Rb_o3vkt1jpO0D2cpANX 7AZG5hiM6si3yj6ni.qyTjWMQU0Nim6awpNyNEaMvmEROvu6TYLc0b27WWql UqatqNGXPoWfS Received: from [98.25.222.156] by web39302.mail.mud.yahoo.com via HTTP; Sat, 29 Jan 2011 20:12:26 PST X-Mailer: YahooMailRC/555 YahooMailWebService/0.8.108.291010 Date: Sat, 29 Jan 2011 20:12:26 -0800 (PST) From: BRM Subject: [gentoo-user] Emerge Problems... To: Users Gentoo Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Archives-Salt: X-Archives-Hash: a7847bb045af17b864b04875214b4516 A little while back my server ran out of hard disk space (due to a failed hard drive) and as a result my local portage mirror got destroyed. Well, I fixed there server - initially by just grabbing a new copy of portage like a new install since it was just completely hosed, and the server is back up and working. However, now my desktop and laptop are both having problems. They sync just fine against the server, but I get a series of errors about not having various ebuilds in the manifest files - so many that I can't emerge anything (even portage). Right now, my laptop is basically hosed - KDE/X won't work on login due to some errors. My desktop at least logs in to the KDE/X. However, on both systems I am having the manifest problem, and I can't edit files either since vim is screwed up due to a change in perl - and I can't run perl-clearner due to the emerge problem. I know both systems can be restored to being fully functional and up-to-date. The question is - how do I get there? I ran across some emails in the list archive on a similar issue - though that was only for 1 ebuild - and it was straight forward enough to fix by just rebuilding the manifest though 'ebuild' or something. I ran across another e-mail suggesting to just resync, and well - I tried that but it didn't work. So my question is - is there a way to automatically fix all these manifest things without having to track down each one by hand and run the 'ebuild' thing on each one individually? I'm completely out of ideas, and I'd really like to get these systems back to full functionality. TIA, Ben