From: Markos Chandras <markos.chandras@gmail.com>
To: gentoo-user@lists.gentoo.org
Cc: "Paul Hartman" <paul.hartman+gentoo@gmail.com>
Subject: Re: [gentoo-user] portage-2.2 + collision protect
Date: Sat, 15 Nov 2008 01:20:07 +0200 [thread overview]
Message-ID: <200811150120.08306.markos.chandras@gmail.com> (raw)
In-Reply-To: <58965d8a0811141507r1a574f6cvd3f8ee05e09aa8b7@mail.gmail.com>
On Saturday 15 November 2008 01:07:33 Paul Hartman wrote:
> On Fri, Nov 14, 2008 at 4:46 PM, Markos Chandras
>
> <markos.chandras@gmail.com> wrote:
> > Hello,
> >
> > I ve upgraded to portage-2.2 . From that time i am having a problem.
When
> > portage finds a collision between two files during the merge time , it
> > complains and doesnt merge the new package. The weird thing is that i
do
> > not have collision-protect under FEATURES on /etc/make.conf file
> >
> > Any idea how to deal with that?
>
> Check to see which other package owns the collided file. If none, it's
> probably safe to delete it & emerge the new package (which will
> replace that file anyway). That's what I do.
>
> Paul
This usually happens when I am trying to install slotted packages like
amarok-1.94
I am using amarok-1.4.10 and I am trying to install amarok-1.94. They are on
different slots but portage keeps complaining about collisions. Since I do not
have collision-protect on FEATURES, portage MUST merge the package even if
it warns me...
--
Markos Chandras
next prev parent reply other threads:[~2008-11-14 23:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-14 22:46 [gentoo-user] portage-2.2 + collision protect Markos Chandras
2008-11-14 23:07 ` Paul Hartman
2008-11-14 23:20 ` Markos Chandras [this message]
2008-11-14 23:24 ` Paul Hartman
2008-11-15 8:40 ` Markos Chandras
2008-11-15 12:27 ` Neil Bothwick
2008-11-15 14:05 ` Markos Chandras
-- strict thread matches above, loose matches on Subject: below --
2008-11-15 14:23 Neil Bothwick
2008-11-15 14:39 ` Markos Chandras
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=200811150120.08306.markos.chandras@gmail.com \
--to=markos.chandras@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
--cc=paul.hartman+gentoo@gmail.com \
/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