Re: [gentoo-user] portage-2.2 + collision protect

[Markos Chandras]

On Saturday 15 November 2008 01:24:18 Paul Hartman wrote:
> On Fri, Nov 14, 2008 at 5:20 PM, Markos Chandras
>
> <markos.chandras@×××××.com> wrote:
> > On Saturday 15 November 2008 01:07:33 Paul Hartman wrote:
> >> On Fri, Nov 14, 2008 at 4:46 PM, Markos Chandras
> >>
> >> <markos.chandras@×××××.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...
>
> What about protect-owned, do you have that? It is like
> collision-protect, but it blocks you from overwriting files KNOWN to
> belong to other packages (where collisiion-protect will block any file
> on disk, even if it has no owning-package)
>
> There are also environment variables which explicitly protect/override
> collision detection for directories, regardless of the features
> setting.
>
> Paul
This is my FEATURES line

FEATURES="parallel-fetch buildpkg candy fixpackages ccache sandbox"

Could some of these be responsible for the collision problem?
-- 
Markos Chandras