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 1MreOi-0004S9-G6 for garchives@archives.gentoo.org; Sat, 26 Sep 2009 21:01:40 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 3DBDDE07CD; Sat, 26 Sep 2009 21:01:37 +0000 (UTC) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.157]) by pigeon.gentoo.org (Postfix) with ESMTP id EF5C0E07CD for ; Sat, 26 Sep 2009 21:01:36 +0000 (UTC) Received: by fg-out-1718.google.com with SMTP id e21so464949fga.10 for ; Sat, 26 Sep 2009 14:01:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.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=9/e8deOfkaxXe22S2aUGVwwBWKhFlyvgOZTuRw8OzyM=; b=Viexea2cQv/K9mjBsjYEWzq6TyHKTNlxZ+GQk7WxfrecuF0HCEO7KvrW2RUJaq44nj cC7Ls8IVaKr3DQdksFremGEa/zooF0k96+aERk53hzhBWSoy3ReBD6dxdOSDwSqIMk1a dVw03dXdg0iRaa72ecnIQf1M97xfeCZ4fxC/w= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=from:to:subject:date:user-agent:references:in-reply-to:mime-version :content-type:content-transfer-encoding:message-id; b=cUHKwK1btMzxXhmDg0I6iNWiJFo/MdMN3iBeI7VvEPqhEcga+ore4Mt7PzPke+qwh5 0o1L4SBffeehBszAywlnZEWPbvAFTnGm+YaJ4Tn2zvC6IY+LnMYhSUjVzjXaz8xPFy4Z joyvNdHMhQC2WUJfB4IDoOYistW8kun+q25pY= Received: by 10.86.208.2 with SMTP id f2mr2099242fgg.16.1253998896347; Sat, 26 Sep 2009 14:01:36 -0700 (PDT) Received: from energy.localnet (energy.heim10.tu-clausthal.de [139.174.197.94]) by mx.google.com with ESMTPS id d6sm2409414fga.1.2009.09.26.14.01.35 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sat, 26 Sep 2009 14:01:35 -0700 (PDT) From: Volker Armin Hemmann To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Re: What causes a package to be brought in during a big emerge? Date: Sat, 26 Sep 2009 23:01:31 +0200 User-Agent: KMail/1.12.1 (Linux/2.6.31r4; KDE/4.3.1; x86_64; ; ) References: <4ABD68BD.7070806@wht.com.au> <200909261522.30726.volkerarmin@googlemail.com> <20090926215502.11e1c38b@krikkit.digimed.co.uk> In-Reply-To: <20090926215502.11e1c38b@krikkit.digimed.co.uk> 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="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <200909262301.32047.volkerarmin@googlemail.com> X-Archives-Salt: 8ea8db68-a332-4937-8b14-d89455360249 X-Archives-Hash: e6439782c73f8744f702128407e81ec4 On Samstag 26 September 2009, Neil Bothwick wrote: > On Sat, 26 Sep 2009 15:22:30 +0200, Volker Armin Hemmann wrote: > > > emerge -C should remove it from the world file. If it does not, > > > something is broken that requires more than editing world. > > > > > > You can also check this with emaint -c world. > > > > well sometimes an app appears more than once in world and after an > > removal instances remain - yes, it should not happen. > > If that because the world file was hand edited, or you you mean one entry > for cat/pkg and one for cat/pkg-ver? > > emaint should still find and fix it. > the second. And then cat/pkg-ver (cat/pkg:slot) stayed around after an unmerge and forced stuff back in. emaint should find it, but in my experience it failes once in a while.