[gentoo-user] gvim emerge problems

2007-02-26 Thread Stuart Howard
Good morning all I am getting this following message when attempting to update world, since there has been no traffic on here I guess the issue is specific to my setup. I imagine that the solution would be to -aC gvim then re-emerge but I would appreciate some guidance before I do that as to be w

Re: [gentoo-user] gvim emerge problems

2007-02-26 Thread Zac Medico
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Stuart Howard wrote: > !!! Multiple versions within a single package slot have been > !!! pulled into the dependency graph: > > ('ebuild', '/', 'app-editors/vim-core-7.0.201', 'merge') pulled in by > ('ebuild', '/', 'app-editors/gvim-7.0.201', 'merge

Re: [gentoo-user] gvim emerge problems

2007-02-26 Thread Stuart Howard
On 26/02/07, Zac Medico <[EMAIL PROTECTED]> wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Stuart Howard wrote: > !!! Multiple versions within a single package slot have been > !!! pulled into the dependency graph: > > ('ebuild', '/', 'app-editors/vim-core-7.0.201', 'merge') pulled in by >

Re: [gentoo-user] gvim emerge problems

2007-02-26 Thread Zac Medico
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Stuart Howard wrote: > My issue is more though why is portage trying and failing to install > two versions of vim at all as so far as I am aware I have never made > such a request of it. > Just the latest ~* version will be fine for me. You have both

Re: [gentoo-user] gvim emerge problems

2007-02-26 Thread Stuart Howard
I have commented out the ~* from /etc/portage/package,keywords on both gvim and vim, and the issue has gone away and all is well again. Though I admit I am a tad confuzzeled as to what the issue was. I thought wrongly that I had the latest ~* versions of both gvim and vim installed along with the

Re: [gentoo-user] gvim emerge problems

2007-02-26 Thread Bo Ørsted Andresen
On Monday 26 February 2007 12:47:12 Stuart Howard wrote: > I have commented out the ~* from /etc/portage/package,keywords on both > gvim and vim, and the issue has gone away and all is well again. > Though I admit I am a tad confuzzeled as to what the issue was. > I thought wrongly that I had the l