| 1 |
On Tuesday 22 July 2003 14:50, Yannick Koehler wrote: |
| 2 |
> Performing Global Updates: /usr/portage/profiles/updates/1Q-2003 |
| 3 |
> (Could take a couple minutes if you have a lot of binary packages.) |
| 4 |
> .='update pass' *='binary update' @='/var/db move' |
| 5 |
> .!!! Invalid binary package: kdelibs-3.1.tbz2 |
| 6 |
> .................!!! Cannot update binary: Destination exists. |
| 7 |
> !!! sys-apps/bash-2.05a-r3 -> app-shells/bash-2.05a-r3 |
| 8 |
> !!! Cannot update binary: Destination exists. |
| 9 |
> !!! sys-apps/bash-2.05b-r3 -> app-shells/bash-2.05b-r3 |
| 10 |
> ...!!! Cannot update binary: Destination exists. |
| 11 |
> !!! sys-apps/iptables-1.2.7a-r2 -> net-firewall/iptables-1.2.7a-r2 |
| 12 |
> !!! Cannot update binary: Destination exists. |
| 13 |
> !!! sys-apps/iptables-1.2.7a-r3 -> net-firewall/iptables-1.2.7a-r3 |
| 14 |
> .......... |
| 15 |
> |
| 16 |
> I'd like to get more information on how I can figure out what this means |
| 17 |
> and how to resolve it. |
| 18 |
> |
| 19 |
|
| 20 |
Well, portage packages are installed in the ALL directory with a symlink from |
| 21 |
the category. There is no real need for all category/symlink dirs, but |
| 22 |
basically that's what's causing it. I believe the newest portage fixes this. |
| 23 |
In any case do not worry, it is more anoying than a problem. |
| 24 |
|
| 25 |
Paul |
| 26 |
|
| 27 |
-- |
| 28 |
Paul de Vrieze |
| 29 |
Researcher |
| 30 |
Mail: pauldv@××××××.nl |
| 31 |
Homepage: http://www.cs.kun.nl/~pauldv |
Archives