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