Yes, I have to unmerge both, then I type 'emerge -u xfreewhatever, and it emerges XFT along with it, then the conflict is back again. Quite irritating:)
I'll try umerging xft, but in past experiance, that produces a new block to the effect of "[blocks B ] x11-base/xfreewhatever" *shrug*.. I'll try again and post my results. On Thu, 2003-10-09 at 12:27, Alan wrote: > On Thu, Oct 09, 2003 at 12:15:47PM -0400, Paul K. Dickson wrote: > > > > I'm always getting this, and the only way around is to unmerge xfree and > > xft, then it disapears, but, then it will remerge them again on it's > > own. Anyone know how to find out what else is doing this? > > > > > > [blocks B ] x11-libs/xft (from pkg x11-base/xfree-4.3.0-r3) > > Do you mean you unmerge xfree and xft and then when you re-emerge them > both? Sorry, I'm not totally understanding :) > > Basically the above means that having xfree installed is blocking your > emerge of xft (which is odd, because you shouldn't need xft, as the > latest xfree has it built in). > > You should be able to get rid of this just by unmerging xft. -- [EMAIL PROTECTED] mailing list
