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 1ModYl-000235-Uo for garchives@archives.gentoo.org; Fri, 18 Sep 2009 13:31:40 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id B6C12E0954; Fri, 18 Sep 2009 13:31:34 +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 74336E0954 for ; Fri, 18 Sep 2009 13:31:34 +0000 (UTC) Received: by fg-out-1718.google.com with SMTP id d23so420812fga.10 for ; Fri, 18 Sep 2009 06:31:34 -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=etkGpTMzSRiXAWMLdhtx2erQOS5bqyiBicWhvA4VW/8=; b=MvTcSsIJlnFMDW9XjUuGvh6rGVMGlc8Q6rfwEEKAaIN2lFYltGcAlN1cRyvwAioI06 mA/5a6zZpoIkPdlT4XyLJ73FG5IzS8VN8trvwzaBcojNTDW1vqL1Olip5P7Args4IfQZ qYmuQ8cBkANMXAs4oAKN4GRzpsbST7BR2EZw8= 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=hS9hu8kQG5v/S+ynqBT5FeWy5xejSZw/9RSEs7j/Wn9/Cu/o8WAZSDXaCZiy9H7XIU bODZQSuQtrZqiDGGjFSm30J9MjfoM+fXzB5ESsZFlEa91MLEA+ZOP0QFk3tX1E3TkywI sNPPHD9uPVT+HrtAtUCRFFM/9w8+0NqN034XA= Received: by 10.86.8.36 with SMTP id 36mr1801424fgh.7.1253280693805; Fri, 18 Sep 2009 06:31:33 -0700 (PDT) Received: from energy.localnet (energy.heim10.tu-clausthal.de [139.174.197.94]) by mx.google.com with ESMTPS id 4sm498071fge.14.2009.09.18.06.31.32 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 18 Sep 2009 06:31:32 -0700 (PDT) From: Volker Armin Hemmann To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Question about a strange emerge warning Date: Fri, 18 Sep 2009 15:31:28 +0200 User-Agent: KMail/1.12.1 (Linux/2.6.31r4; KDE/4.3.1; x86_64; ; ) References: <445a8b100909180558x4adba19dp50735dcecc0771ba@mail.gmail.com> In-Reply-To: <445a8b100909180558x4adba19dp50735dcecc0771ba@mail.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="iso-8859-15" Content-Transfer-Encoding: quoted-printable Message-Id: <200909181531.28279.volkerarmin@googlemail.com> X-Archives-Salt: 53753c0c-20e0-4d3b-9ffa-bdf6b43de5e1 X-Archives-Hash: af36e5a40f0f18e0acc594f0719269e5 On Freitag 18 September 2009, Massimiliano Ziccardi wrote: > Hi all. >=20 > Thanks to your support, I think I got a little bit of knowledge of how > emerge works, so I started cleaning my USE flags (I had lot of useless > stuff...). > To perform such cleaning, I started with USE=3D-* and than added everythi= ng I > needed. >=20 > It hasn't been very hard (but quite long :-) )to make things working: > emerge is a really cool tool. > However, I got this strange message: >=20 > * Detected file collision(s): > * > * /usr/lib/mozilla-firefox/defaults/autoconfig/prefcalls.js > * /usr/lib/mozilla-firefox/defaults/autoconfig/platform.js > * > * Searching all installed packages for file collisions... > * > * Press Ctrl-C to Stop > * > * net-libs/xulrunner-1.9.0.14 > * /usr/lib/mozilla-firefox/defaults/autoconfig/platform.js > * /usr/lib/mozilla-firefox/defaults/autoconfig/prefcalls.js > * > * Package 'www-client/mozilla-firefox-3.0.14' NOT merged due to file > * collisions. If necessary, refer to your elog messages for the whole > * content of the above message. >=20 > If I understood, it seems that xulrunner and firefox package contains the > same files (prefcalls.js and platform.js) in the same directory. that is correct. > Is it normal? Should I worry? Or I simply have to ignore it? it is not normal and considered a bug. Should you worry - see that is hard= to=20 answer - in most cases I have met, it is save to remove the already install= ed=20 files, because the following app is providing exactly the same stuff. But sometimes that breaks. In your case - I would move the two files into a= =20 backup dir in /root or somewhere else far away and save and retry. If=20 everything works as expected (firefox is working, nothing is especially cra= shy)=20 you can remove them. >=20 > One more question : what is the difference between > www-client/mozilla-firefox and www-client/mozilla-firefox-bin ? =2Dbin is already compiled. It is a binary package just like mozilla is=20 distributing them. Advantage: instant joy. Disadvantage: sometimes slower,= =20 sometimes depending on stuff you really don't want to install. Gl=FCck Auf Volker