| 1 |
On Fri, Jan 20, 2012 at 3:09 PM, Grant <emailgrant@×××××.com> wrote: |
| 2 |
>>> I have an old Gentoo system that hasn't been updated or used at all in |
| 3 |
>>> at least 2 years. It's remote but I have SSH access. I've updated |
| 4 |
>>> portage but I thought I should check with you guys before I plow ahead |
| 5 |
>>> with emerge -DuN world. It won't be used for anything until I bring |
| 6 |
>>> it up to speed and someone can physically log in and issue commands a |
| 7 |
>>> couple times per week so an outage isn't the end of the world. Any |
| 8 |
>>> advice? |
| 9 |
>> |
| 10 |
>> Take small steps. emerge -pv @system first and be prepared to emerge |
| 11 |
>> packages a few at a time. |
| 12 |
> |
| 13 |
> Weird, it looks like portage didn't update to the latest version. |
| 14 |
> emerging it again seems to want to update it again. I get this: |
| 15 |
> |
| 16 |
> # emerge -pv portage |
| 17 |
> [snip] |
| 18 |
> [ebuild NS ] dev-lang/python-2.7.2-r3 [2.5.2-r7] USE="gdbm ncurses |
| 19 |
> readline ssl threads (wide-unicode) xml -berkdb -build -doc -examples |
| 20 |
> -ipv6 -sqlite -tk -wininst" 11,494 kB |
| 21 |
> [ebuild U ] sys-apps/portage-2.1.10.41 [2.1.6.13] USE="(ipc%*) |
| 22 |
> -build -doc -epydoc -python2% -python3% (-selinux) (-less%*)" |
| 23 |
> LINGUAS="-pl" 899 kB |
| 24 |
> [blocks B ] dev-lang/python:2.7 ("dev-lang/python:2.7" is blocking |
| 25 |
> sys-apps/portage-2.1.6.13) |
| 26 |
> [blocks B ] <sys-apps/portage-2.1.9 ("<sys-apps/portage-2.1.9" is |
| 27 |
> blocking dev-lang/python-2.7.2-r3) |
| 28 |
> |
| 29 |
> I think I'll be able to resolve most stuff myself but this one is |
| 30 |
> tricking me. I don't want to mess around unmerging python or portage. |
| 31 |
> |
| 32 |
> - Grant |
| 33 |
> |
| 34 |
|
| 35 |
OK, so the install is old and portage has dependencies, right? |
| 36 |
|
| 37 |
emerge -pvDuN portage |
| 38 |
|
| 39 |
will get you closer. However this is probably best covered using |
| 40 |
Neil's suggestion of |
| 41 |
|
| 42 |
emerge -pvDuN @system |
| 43 |
|
| 44 |
which would, if successful, update portage as well as everything else |
| 45 |
that's required to get the machine up and running. |
| 46 |
|
| 47 |
If that does work then don't forget all the eselect python & |
| 48 |
gcc-config type stuff that you'll need to do to tell the system about |
| 49 |
the new environment. |
| 50 |
|
| 51 |
One little area you might want to be careful about here is grub. Best |
| 52 |
IMO if you do not update grub until you have the machine actually |
| 53 |
booting the updated environment, assuming we get that far. |
| 54 |
|
| 55 |
HTH, |
| 56 |
Mark |
Archives