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 1M7LXe-0006on-Dq for garchives@archives.gentoo.org; Fri, 22 May 2009 03:35:30 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id D1C90E0292; Fri, 22 May 2009 03:35:28 +0000 (UTC) Received: from yx-out-1718.google.com (yx-out-1718.google.com [74.125.44.152]) by pigeon.gentoo.org (Postfix) with ESMTP id B68FBE0292 for ; Fri, 22 May 2009 03:35:28 +0000 (UTC) Received: by yx-out-1718.google.com with SMTP id 36so4857828yxh.46 for ; Thu, 21 May 2009 20:35:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=oyDaEmXYIDo2aPQ6A8JmqVA95hRtN0sQdXviLaVqvBw=; b=m5KoqdK0/6FfltjUubg7gGs2q6hyK2tbEGPEtGx4g5t/Ke1LDIJoz1cCakHds94Wtz X4Vzhj3kWoGIYkst5N2euAHKbCps6R1mLdCAXcXSbSPzx/SX875318xf26E9CHw301bk BpVEwDJay5r+4TNdYULMvP5FFvj1CNuvD8iwQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=OBQ3vohTX8A9ISx19ULl+fmYPUZpzvSY+py7CmYa9ewr5W0u0S+5pFvGPQC8IySzFr xpg+lCgkS6T20AdjJAgAfOsSwaIVg+Wog/V9V0BsXyBAIqGzsZ4MXIF4tQsBsp/NUKbP HeN/vtGvq3pXW3Du4W5OLsx1jDW1+pkkHQSSU= 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 Received: by 10.100.123.12 with SMTP id v12mr6380748anc.21.1242963321008; Thu, 21 May 2009 20:35:21 -0700 (PDT) In-Reply-To: <9acccfe50905212020k2ace76b9l5c9fe33bccd5f7c@mail.gmail.com> References: <9acccfe50905211746s2db29c38vbd3122256c43b116@mail.gmail.com> <200905220306.42711.volkerarmin@googlemail.com> <200905220317.15084.wonko@wonkology.org> <9acccfe50905212020k2ace76b9l5c9fe33bccd5f7c@mail.gmail.com> Date: Thu, 21 May 2009 20:35:20 -0700 Message-ID: <9acccfe50905212035o5048f2c4vce3ed60693334390@mail.gmail.com> Subject: Re: [gentoo-user] x11-base/xorg-server-1.5.3-r5 with x11-drivers/ati-drivers-8.552-r2 -- file conflict From: "Kevin O'Gorman" To: gentoo-user@lists.gentoo.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Archives-Salt: 7fd563e5-4ba9-4b4f-b9c0-cd4130ff0bce X-Archives-Hash: 13a521b8b2e8ddf6dc5a98ecc574b06e On Thu, May 21, 2009 at 8:20 PM, Kevin O'Gorman wrote: > On Thu, May 21, 2009 at 6:17 PM, Alex Schuster wrot= e: >> Volker Armin Hemmann writes: >> >>> On Freitag 22 Mai 2009, Kevin O'Gorman wrote: >>> > x11-drivers/ati-drivers-8.552-r2 won't compile due to a file conflict= , >>> > but portageq does not see it. >> >> Probably because the ati-drivers you already have installed do not have = this >> file, either because they are an older version, or they did not create i= t >> when compiling against the old x.org. >> >>> > Anybody know how to work around this? >> >>> yes, remove /usr/lib/opengl/ati/extensions/libglx.so it should be owned >>> by ati-drivers, if not, some screw up happened. >> >> Or use 'FEATURES=3D-collision-protect emerge ati-drivers'. I think I had= the >> same collision. >> >>> /me wonders why there is still a stone old buggy ebuild/driver in >>> 'stable'. >> >> I was not able to compile newer ati-drivers with tuxonice-sources-2.6.28= -r3. >> Or ANY ati-drivers with a newer tuxonice kernel. >> > > I thank you for the expert advice. =A0I'm doing the emerge now, but even > if it succeeds, I'm worried that the xorg-server will still own this > file, since portageq seems to see that it does. =A0This seems inherently > wrong. > > Sigh. =A0I'm too far along to flinch now, so if this emerges, I'll > probably restart X. > > Wish me luck. Hmm. Even with the FEATURES option from the suggestion, I get exactly the same error message. I cut-and-pasted it, but I wonder if it's spelled right? I'm going to try just deleting (well, renaming) the file, hoping that this will work... --=20 Kevin O'Gorman, PhD