| 1 |
Sorry about top posting but I'm on the Kindle. How are you set for |
| 2 |
disk space? Consider creating a new partition and building a new |
| 3 |
install in a chroot. When it works then change grub and boot it for |
| 4 |
real. At least that won't hurt your working install. |
| 5 |
|
| 6 |
Cheers, |
| 7 |
Mark |
| 8 |
|
| 9 |
On 1/22/12, Grant <emailgrant@×××××.com> wrote: |
| 10 |
>>> Ok, looks as though it's time for a manually-installed version of |
| 11 |
>>> python to upgrade portage, then a portage-installed python:2.6 to |
| 12 |
>>> bootstrap your way towards modernity. |
| 13 |
>>> |
| 14 |
>>> This is all explained here: |
| 15 |
>>> http://www.gentoo.org/proj/en/portage/doc/manually-fixing-portage.xml |
| 16 |
>>> |
| 17 |
>>> This may also help |
| 18 |
>>> http://forums.gentoo.org/viewtopic-p-5578709.html |
| 19 |
>> |
| 20 |
>> That last one mentioned --nodeps which gave me an idea. I did 'emerge |
| 21 |
>> -pv python' then emerged all of the packages listed with --nodeps so |
| 22 |
>> portage wouldn't complain. Portage wouldn't work after that until I |
| 23 |
>> switched back to python:2.5 with eselect. Then I emerged portage to |
| 24 |
>> the latest version (which switched back to python:2.6) and I'm hoping |
| 25 |
>> I can make some good progress before I come crying back to you guys |
| 26 |
>> again. |
| 27 |
>> |
| 28 |
>> - Grant |
| 29 |
> |
| 30 |
> I just did a 'ls -ltr /var/log/portage' and this thing hasn't been |
| 31 |
> updated in over 3 years. Wow. |
| 32 |
> |
| 33 |
> - Grant |
| 34 |
> |
| 35 |
> |
Archives