| 1 |
>> I have an old Gentoo system that hasn't been updated or used at all in |
| 2 |
>> at least 2 years. It's remote but I have SSH access. I've updated |
| 3 |
>> portage but I thought I should check with you guys before I plow ahead |
| 4 |
>> with emerge -DuN world. It won't be used for anything until I bring |
| 5 |
>> it up to speed and someone can physically log in and issue commands a |
| 6 |
>> couple times per week so an outage isn't the end of the world. Any |
| 7 |
>> advice? |
| 8 |
> |
| 9 |
> Take small steps. emerge -pv @system first and be prepared to emerge |
| 10 |
> packages a few at a time. |
| 11 |
|
| 12 |
Weird, it looks like portage didn't update to the latest version. |
| 13 |
emerging it again seems to want to update it again. I get this: |
| 14 |
|
| 15 |
# emerge -pv portage |
| 16 |
[snip] |
| 17 |
[ebuild NS ] dev-lang/python-2.7.2-r3 [2.5.2-r7] USE="gdbm ncurses |
| 18 |
readline ssl threads (wide-unicode) xml -berkdb -build -doc -examples |
| 19 |
-ipv6 -sqlite -tk -wininst" 11,494 kB |
| 20 |
[ebuild U ] sys-apps/portage-2.1.10.41 [2.1.6.13] USE="(ipc%*) |
| 21 |
-build -doc -epydoc -python2% -python3% (-selinux) (-less%*)" |
| 22 |
LINGUAS="-pl" 899 kB |
| 23 |
[blocks B ] dev-lang/python:2.7 ("dev-lang/python:2.7" is blocking |
| 24 |
sys-apps/portage-2.1.6.13) |
| 25 |
[blocks B ] <sys-apps/portage-2.1.9 ("<sys-apps/portage-2.1.9" is |
| 26 |
blocking dev-lang/python-2.7.2-r3) |
| 27 |
|
| 28 |
I think I'll be able to resolve most stuff myself but this one is |
| 29 |
tricking me. I don't want to mess around unmerging python or portage. |
| 30 |
|
| 31 |
- Grant |
Archives