| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
On 21.01.2012 00:09, Grant wrote: |
| 5 |
>>> I have an old Gentoo system that hasn't been updated or used at |
| 6 |
>>> all in at least 2 years. It's remote but I have SSH access. |
| 7 |
>>> I've updated portage but I thought I should check with you guys |
| 8 |
>>> before I plow ahead with emerge -DuN world. It won't be used |
| 9 |
>>> for anything until I bring it up to speed and someone can |
| 10 |
>>> physically log in and issue commands a couple times per week so |
| 11 |
>>> an outage isn't the end of the world. Any advice? |
| 12 |
>> |
| 13 |
>> Take small steps. emerge -pv @system first and be prepared to |
| 14 |
>> emerge packages a few at a time. |
| 15 |
> |
| 16 |
> Weird, it looks like portage didn't update to the latest version. |
| 17 |
> emerging it again seems to want to update it again. I get this: |
| 18 |
> |
| 19 |
> # emerge -pv portage [snip] [ebuild NS ] |
| 20 |
> dev-lang/python-2.7.2-r3 [2.5.2-r7] USE="gdbm ncurses readline ssl |
| 21 |
> threads (wide-unicode) xml -berkdb -build -doc -examples -ipv6 |
| 22 |
> -sqlite -tk -wininst" 11,494 kB [ebuild U ] |
| 23 |
> sys-apps/portage-2.1.10.41 [2.1.6.13] USE="(ipc%*) -build -doc |
| 24 |
> -epydoc -python2% -python3% (-selinux) (-less%*)" LINGUAS="-pl" 899 |
| 25 |
> kB [blocks B ] dev-lang/python:2.7 ("dev-lang/python:2.7" is |
| 26 |
> blocking sys-apps/portage-2.1.6.13) [blocks B ] |
| 27 |
> <sys-apps/portage-2.1.9 ("<sys-apps/portage-2.1.9" is blocking |
| 28 |
> dev-lang/python-2.7.2-r3) |
| 29 |
> |
| 30 |
> I think I'll be able to resolve most stuff myself but this one is |
| 31 |
> tricking me. I don't want to mess around unmerging python or |
| 32 |
> portage. |
| 33 |
> |
| 34 |
> - Grant |
| 35 |
> |
| 36 |
|
| 37 |
You could do: |
| 38 |
|
| 39 |
emerge =dev-lang/python-2.6.7-r2 |
| 40 |
|
| 41 |
You should disable "threads" if it doesn't work (there is something |
| 42 |
related to it in the portage ebuild). After that, switch to python 2.6 |
| 43 |
via eselect and try to update portage. |
| 44 |
If I read the ebuilds correctly, that should work. |
| 45 |
|
| 46 |
Another possibility would be to install a 3.x version of python and |
| 47 |
switch portage to that (via the python3 useflag). |
| 48 |
|
| 49 |
I'd try the python3 approach first, since it could spare you a 2.6 |
| 50 |
install. |
| 51 |
Don't forget to run python-updater after updating everything or if you |
| 52 |
get strange (python related) errorrs in between... |
| 53 |
|
| 54 |
Good luck |
| 55 |
|
| 56 |
Hinnerk |
| 57 |
-----BEGIN PGP SIGNATURE----- |
| 58 |
Version: GnuPG v2.0.18 (GNU/Linux) |
| 59 |
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ |
| 60 |
|
| 61 |
iQEcBAEBAgAGBQJPGfkPAAoJEJwwOFaNFkYcr48H/iAVc/K6gOkGZ/wFewkoggWZ |
| 62 |
gKS5bRiuwWRRLBL3nRPraIlYvnfzqTTG/PLkYasFgcEeCpKE70mMcKqIvFFzt3Ab |
| 63 |
UVc5Xly8qaYUR4XUYNzz5ww9TAs6BrmYyJvxCSXdp+oiZx6RmeyuXuwFU6v04v1I |
| 64 |
QkWrVkOIOtq9YVFxgu096KiQeRzZ2m5iURgkipl8rBYNXSaKBVktuKlnS0loFUAZ |
| 65 |
rqNLs3qUuAsEmlua7KLV8LHWVfnBICuXwrgCssy+cBHJGeTUEQIyIc4lnI7Mwe2d |
| 66 |
7GWuMTkxKfyWtChiW/hWxYv5c4lQFkP+5GIyQT64rJ7cjkufkPkkNZx7wQtszjs= |
| 67 |
=ASiv |
| 68 |
-----END PGP SIGNATURE----- |
Archives