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 1NHz03-0001YY-1w for garchives@archives.gentoo.org; Tue, 08 Dec 2009 12:17:09 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 66D96E07D2; Tue, 8 Dec 2009 12:16:40 +0000 (UTC) Received: from mail-ew0-f214.google.com (mail-ew0-f214.google.com [209.85.219.214]) by pigeon.gentoo.org (Postfix) with ESMTP id 28CA8E07D2 for ; Tue, 8 Dec 2009 12:16:40 +0000 (UTC) Received: by ewy6 with SMTP id 6so643214ewy.29 for ; Tue, 08 Dec 2009 04:16:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:subject:date :user-agent:references:in-reply-to:mime-version:content-type :content-transfer-encoding:message-id; bh=qBtu/gB0l+c5jIBmw5HJl5o/Wd4nixTzY+ZOhk+t5k4=; b=a72m8LYdUcB9F7NkmgW6X9jC688fh3Cy5OMc9Stii/qIkLLOe0sRzgb5P5IBhmnrZ/ IgfMI90nYFIdMaK9IMqwQc8OzkIZKPwOCh38MZedRw4XtjUSUGkbGsXDjHJ2acB/ERih XcEWN0ipJDji5oa+ze/JfNDo2CFo+gv5EXS0E= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:subject:date:user-agent:references:in-reply-to:mime-version :content-type:content-transfer-encoding:message-id; b=xKTUJCpEQQseqKG2ITsqCi55Ol0904AiYVdTczLK3PIUm/zUmNHbMzatG/pr6YWuIF zH3NvtV+c8zTWXRbkkb875TsWSOf6kJ4RZS76toCycwl43xZrT6/G2xoF7AZq4y0fj8c k8X7NfSCSOZ41pi7k/TXxplkNWz5S9nk4mQyo= Received: by 10.213.109.69 with SMTP id i5mr8564344ebp.11.1260274597546; Tue, 08 Dec 2009 04:16:37 -0800 (PST) Received: from nazgul.localnet (dustpuppy.is.co.za [196.14.169.11]) by mx.google.com with ESMTPS id 16sm3926686ewy.10.2009.12.08.04.16.36 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 08 Dec 2009 04:16:37 -0800 (PST) From: Alan McKinnon To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] How can I solve "emerge @preserved-rebuild" loop? Date: Tue, 8 Dec 2009 14:15:25 +0200 User-Agent: KMail/1.12.4 (Linux/2.6.31-zen9; KDE/4.3.4; x86_64; ; ) References: <4B1D4517.2010506@gmail.com> <200912081318.27928.alan.mckinnon@gmail.com> <4B1E41CF.2060904@gmail.com> In-Reply-To: <4B1E41CF.2060904@gmail.com> 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="utf-8" Content-Transfer-Encoding: 7bit Message-Id: <200912081415.25559.alan.mckinnon@gmail.com> X-Archives-Salt: d7012122-adb4-481d-a30f-6d21af922cce X-Archives-Hash: 0ecf8ae2c815e75737cbd88248278094 On Tuesday 08 December 2009 14:08:47 Dale wrote: > >> I have the same problem, but the "emerge -av1 util-linux" has blocking > >> issues with sys-fs/e2fsprogs. Whenever I remove sys-fs stuff I usually > >> regret it. > >> > > > > You must remove the e2fsprogs* packages, emerge util-linux and re-emerge > > e2fsprogs* > > > > This is safe as long as you don't log out, reboot, kill bash or do other > > weird and wonderful things that require a working e2fsprogs. > > > > Think of it this way: > > > > delete your kernel image in /boot, do all kinds of stuff and put back a > > different kernel image named the same as the original. Nothing will go > > wrong unless you reboot|restart. Same with e2fprogs. > > > > Is this the one where you need to fetch the files first, then un-emerge > and emerge? I recall one being that way but not sure if it is this one. No, that was a while ago. This is simply a conflict involving e2fsprogs-libs Doesn't remove wget -- alan dot mckinnon at gmail dot com