1 |
On 06/23/2010 01:56 AM, Alex Schuster wrote: |
2 |
> Mick writes: |
3 |
>> Checking for file ownership gives me: |
4 |
>> |
5 |
>> # portageq owners / /usr/bin/neon-config |
6 |
>> net-misc/neon-0.29.3 |
7 |
>> /usr/bin/neon-config |
8 |
>> |
9 |
>> # portageq owners / /usr/include/neon/ne_207.h |
10 |
>> net-misc/neon-0.29.3 |
11 |
>> /usr/include/neon/ne_207.h |
12 |
>> |
13 |
>> and so on. How come that I cannot install net-misc/neon-0.29.3 due to |
14 |
>> file collisions, when it is this package which owns the files in the |
15 |
>> first place? |
16 |
> |
17 |
> Strange! So it is installed already? Did you chaneg USE flags, so it gets |
18 |
> emerged again? Or did something go wrong when installing it the last time? |
19 |
> |
20 |
> I have no idea, I wouldn't think what you see is possible at all. |
21 |
|
22 |
neon got moved from net-misc to net-libs. It's just that the maintainer |
23 |
forgot to rename the package if already installed. In those cases, you |
24 |
either wait till the maintainer renames it, which will be picked up in |
25 |
the next sync, or you just unmerge and then update again. |