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

2008-11-15 Thread Markos Chandras
On Saturday 15 November 2008 01:24:18 Paul Hartman wrote:
 On Fri, Nov 14, 2008 at 5:20 PM, Markos Chandras

 [EMAIL PROTECTED] wrote:
  On Saturday 15 November 2008 01:07:33 Paul Hartman wrote:
  On Fri, Nov 14, 2008 at 4:46 PM, Markos Chandras
 
  [EMAIL PROTECTED] 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



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

2008-11-15 Thread Neil Bothwick
On Sat, 15 Nov 2008 10:40:25 +0200, Markos Chandras wrote:

   I do not have collision-protect on FEATURES, portage MUST merge the
   package even if it warns me...  

 This is my FEATURES line
 
 FEATURES=parallel-fetch buildpkg candy fixpackages ccache sandbox

You don't have -collision-protect either, so it could be on by default in
your profile. What do you get from

emerge --info | grep FEATURES


-- 
Neil Bothwick

Why is it that when you transport something by car it's called shipment,
but when you transport it by ship it's called cargo?


signature.asc
Description: PGP signature


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

2008-11-15 Thread Markos Chandras
On Saturday 15 November 2008 14:27:49 Neil Bothwick wrote:
 On Sat, 15 Nov 2008 10:40:25 +0200, Markos Chandras wrote:
I do not have collision-protect on FEATURES, portage MUST merge the
package even if it warns me...
 
  This is my FEATURES line
 
  FEATURES=parallel-fetch buildpkg candy fixpackages ccache sandbox

 You don't have -collision-protect either, so it could be on by default in
 your profile. What do you get from

 emerge --info | grep FEATURES

Ah that got me some extra features

FEATURES=buildpkg candy ccache distlocks fixpackages parallel-fetch 
preserve-libs protect-owned sandbox sfperms strict unmerge-orphans userfetch

So , as you can see protect-owned is on as you told me before

What if I add under FEATURES , -protect-owned? . Could this solve my problem?


-- 
Markos Chandras



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

2008-11-15 Thread Neil Bothwick


Yes, in the same way that disconnecting the warning lamp fixes the low oil 
pressure problem in your car :(

-- 
Neil Bothwick
 
On 15 Nov 2008, 2:06 PM, Markos Chandras [EMAIL PROTECTED] 
wrote:

On Saturday 15 November 2008 14:27:49 Neil Bothwick wrote:  On Sat, 15 Nov 
2008 10:40:25 +0200, Mar...
Ah that got me some extra features

FEATURES=buildpkg candy ccache distlocks fixpackages parallel-fetch
preserve-libs protect-owned sandbox sfperms strict unmerge-orphans 
userfetch

So , as you can see protect-owned is on as you told me before

What if I add under FEATURES , -protect-owned? . Could this solve my 
problem?


--
Markos Chandras



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

2008-11-15 Thread Markos Chandras
On Saturday 15 November 2008 16:23:51 Neil Bothwick wrote:
 Yes, in the same way that disconnecting the warning lamp fixes the low oil
 pressure problem in your car :(

I agree that this is a wrong way to fix it. First of all am gonna fill a bug 
about amarok and I ll act accordingly 

Thanks

-- 
Markos Chandras



[gentoo-user] portage-2.2 + collision protect

2008-11-14 Thread Markos Chandras
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?

Thanks
-- 
Markos Chandras



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

2008-11-14 Thread Paul Hartman
On Fri, Nov 14, 2008 at 4:46 PM, Markos Chandras
[EMAIL PROTECTED] 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



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

2008-11-14 Thread Markos Chandras
On Saturday 15 November 2008 01:07:33 Paul Hartman wrote:
 On Fri, Nov 14, 2008 at 4:46 PM, Markos Chandras

 [EMAIL PROTECTED] 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



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

2008-11-14 Thread Paul Hartman
On Fri, Nov 14, 2008 at 5:20 PM, Markos Chandras
[EMAIL PROTECTED] wrote:
 On Saturday 15 November 2008 01:07:33 Paul Hartman wrote:
 On Fri, Nov 14, 2008 at 4:46 PM, Markos Chandras

 [EMAIL PROTECTED] 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