On Fri, May 22, 2009 at 2:40 AM, Alex Schuster <wo...@wonkology.org> wrote: > Kevin O'Gorman writes: > >> On Thu, May 21, 2009 at 8:20 PM, Kevin O'Gorman <kogor...@gmail.com> > wrote: > >> > I thank you for the expert advice. I'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. This seems inherently >> > wrong. > > Well, it is indeed. > >> > Sigh. I'm too far along to flinch now, so if this emerges, I'll >> > probably restart X. >> > >> > Wish me luck. > > I do, but I do not believe bad things might happen. > >> 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? > > It is. But I forgot about the protect-owned feature. I thought -collision- > protect would act stronger and imply it, but apparently it does not. So, > 'FEATURES=-protect-owned emerge ati-drivers' might have worked better. If > not, 'FEATURES="-collision-protect -protect-owned" emerge ati-drivers' would > have worked in any case. > >> I'm going to try just deleting (well, renaming) the file, hoping that >> this will work... > > Yes, that's okay. After all, the file is still there, it's just now being > generated by the ati-driver. I wouldn't worry too much. > > Wonko
well, it emerged this time. I'm going to restart X over the weekend, when I'll have time to clean up the mess that I half expect. ++ kevin -- Kevin O'Gorman, PhD
