public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Stuart Howard" <stuart.g.howard@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] gvim emerge problems
Date: Mon, 26 Feb 2007 10:19:10 +0000	[thread overview]
Message-ID: <d5d1857a0702260219g68b1ed52i36d177e5b6a1e80e@mail.gmail.com> (raw)
In-Reply-To: <45E2AA07.9010306@gentoo.org>

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



  reply	other threads:[~2007-02-26 10:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-26  7:54 [gentoo-user] gvim emerge problems Stuart Howard
2007-02-26  9:36 ` Zac Medico
2007-02-26 10:19   ` Stuart Howard [this message]
2007-02-26 10:53     ` Zac Medico
2007-02-26 11:47       ` Stuart Howard
2007-02-26 12:24         ` Bo Ørsted Andresen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=d5d1857a0702260219g68b1ed52i36d177e5b6a1e80e@mail.gmail.com \
    --to=stuart.g.howard@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox