[gentoo-user] gvim emerge problems

[gentoo-user] gvim emerge problems

[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 without vim
would be ....
This same issue happened last week but the solution was to bring
vim-core into ~* this week I have no where to go with that.
I imagine that I could also follow the instruction given in the output
but it seem strange that that would be required to achevie a simple
update, if I am slotted or have multiple installs it is not by design
so I would prefer to revert to a simple install.
Any help gratefully accepted

Cheers
    stu

genstu stuart # emerge -aDuvN world

These are the packages that would be merged, in order:

Calculating world dependencies |
!!! 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')

('ebuild', '/', 'app-editors/vim-core-7.0.174', 'nomerge') pulled in by
  ('ebuild', '/', 'app-editors/vim-7.0.174', 'nomerge')

It may be possible to solve this problem by using package.mask to
prevent one of those packages from being selected. However, it is also
possible that conflicting dependencies exist such that they are
impossible to satisfy simultaneously. If such a conflict exists in the
dependencies of two different packages, then those packages can not be
installed simultaneously.

For more information, see MASKED PACKAGES section in the emerge man page
or refer to the Gentoo Handbook.

!!! Depgraph creation failed.

genstu stuart # grep vim /var/lib/portage/world
app-vim/vimpython
app-vim/vimbuddy
app-editors/gvim
app-vim/info
app-vim/vimcommander
app-vim/calendar
app-vim/cvsmenu
app-vim/locateopen
app-editors/vim
app-vim/svncommand
app-vim/taglist

genstu stuart # grep vim /etc/portage/package.keywords
app-editors/vim-core ~*
app-editors/gvim ~*


-- 
"There are 10 types of people in this world: those who understand
binary, those who don't"

--Unknown
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] gvim emerge problems

[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')
> 
> ('ebuild', '/', 'app-editors/vim-core-7.0.174', 'nomerge') pulled in by
>  ('ebuild', '/', 'app-editors/vim-7.0.174', 'nomerge')

You can't have gvim-7.0.201 and vim-7.0.174 installed simultaneously
because they depend on different versions of vim-core.  The solution
is to either mask gvim-7.0.201 and vim-core-7.0.201 or unmask
vim-7.0.201:

echo app-editors/vim >> /etc/portage/package.keywords

Zac
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.2 (GNU/Linux)

iD8DBQFF4qoF/ejvha5XGaMRAm0kAKDimUDPkcfyr9NkJq58r2kEILcPJgCg1dbB
C3GZneO5nO8Ab210DfHCWzE=
=VnRl
-----END PGP SIGNATURE-----
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] gvim emerge problems

[Stuart Howard]

On 26/02/07, Zac Medico <zmedico@gentoo.org> 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
> >  ('ebuild', '/', 'app-editors/gvim-7.0.201', 'merge')
> >
> > ('ebuild', '/', 'app-editors/vim-core-7.0.174', 'nomerge') pulled in by
> >  ('ebuild', '/', 'app-editors/vim-7.0.174', 'nomerge')
>
> You can't have gvim-7.0.201 and vim-7.0.174 installed simultaneously
> because they depend on different versions of vim-core.  The solution
> is to either mask gvim-7.0.201 and vim-core-7.0.201 or unmask
> vim-7.0.201:

Agreed

>
> echo app-editors/vim >> /etc/portage/package.keywords
>
> Zac

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.
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] gvim emerge problems

[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 gvim and vim in your world file.  If you want the
latest ~* versions of gvim, then you'll also need the latest ~*
version of vim.  Alternatively, you could uninstall vim.

Zac
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.2 (GNU/Linux)

iD8DBQFF4rwm/ejvha5XGaMRAjmcAJ0SiBP5zjpTmOdgiGbgEw4hMYastQCggbRA
hITgcOI5TbvqzMWrlh9mjfA=
=g8eM
-----END PGP SIGNATURE-----
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] gvim emerge problems

[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 appropriate vim-core, it turns out that I
had stable but it was calling ~* due to the package,keywords file
though I dont understand quite why the stable versions could not be
updated to include all matching versions of gvim vim vimcore in
testing?
No matter really as so long as I have a working vim from work and a
gvim at home I am happy, thanks for the responses.

stu

On 26/02/07, Zac Medico <zmedico@gentoo.org> wrote:
> -----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 gvim and vim in your world file.  If you want the
> latest ~* versions of gvim, then you'll also need the latest ~*
> version of vim.  Alternatively, you could uninstall vim.
>
> Zac
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.2 (GNU/Linux)
>
> iD8DBQFF4rwm/ejvha5XGaMRAjmcAJ0SiBP5zjpTmOdgiGbgEw4hMYastQCggbRA
> hITgcOI5TbvqzMWrlh9mjfA=
> =g8eM
> -----END PGP SIGNATURE-----
> --
> gentoo-user@gentoo.org mailing list
>
>


-- 
"There are 10 types of people in this world: those who understand
binary, those who don't"

--Unknown
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] gvim emerge problems

[Bo Ørsted Andresen]

[-- Attachment #1: Type: text/plain, Size: 1199 bytes --]

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 latest ~* versions of both gvim and
> vim installed along with the appropriate vim-core, it turns out that I
> had stable but it was calling ~* due to the package,keywords file
> though I dont understand quite why the stable versions could not be
> updated to include all matching versions of gvim vim vimcore in
> testing?

It's not exactly clear to me what's so hard to understand here. You had gvim 
and vim-core in your package.keywords in effect requesting version 7.0.201 of 
both of those. You didn't have vim in package.keywords in effect requesting 
7.0.174 of that. vim-7.0.174 depends on vim-core-7.0.174 which cannot coexist 
with vim-core-7.0.201 as it isn't slotted.

That leaves two possible solutions. 1) Removing gvim and vim-core from 
package.keywords as you seem to have done. 2) Adding vim to package.keywords.

PS: Please don't top-post.

-- 
Bo Andresen

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]