| 1 |
On Sunday 24 April 2011 14:25:58 Alan Mackenzie wrote: |
| 2 |
> Hi, Mick. |
| 3 |
> |
| 4 |
> On Sun, Apr 24, 2011 at 09:17:45AM +0100, Mick wrote: |
| 5 |
> > On Saturday 23 April 2011 21:06:25 Alan Mackenzie wrote: |
| 6 |
> > > On Sat, Apr 23, 2011 at 08:46:30PM +0100, Mick wrote: |
| 7 |
> > > > What do you get when you run: |
| 8 |
> > > > |
| 9 |
> > > > # eselect python list |
| 10 |
> > > |
| 11 |
> > > Available Python interpreters: |
| 12 |
> > > [1] python2.6 * |
| 13 |
> > > [2] python2.7 |
| 14 |
> > > [3] python3.1 |
| 15 |
> > |
| 16 |
> > OK, the next stage would be to change your python to the latest stable: |
| 17 |
> > |
| 18 |
> > eselect python set 2 |
| 19 |
> |
| 20 |
> DONE. |
| 21 |
> |
| 22 |
> > and then remerge those packages that were linked against the old |
| 23 |
> > python: |
| 24 |
> > |
| 25 |
> > python-updater -v -p |
| 26 |
> > |
| 27 |
> > to get a list of these. |
| 28 |
> |
| 29 |
> That gives me a list of 24 packages. Am I meant to actually run |
| 30 |
> python-updater without the -p, here? |
| 31 |
|
| 32 |
That's correct. As the man emerge say -p stands for --pretend. Just to give |
| 33 |
a chance to see what it wants to do and think about it before you run it again |
| 34 |
without it for execution. |
| 35 |
|
| 36 |
You need to do this next. |
| 37 |
|
| 38 |
|
| 39 |
> > When you finish all this you can run: |
| 40 |
> > |
| 41 |
> > emerge --depclean -v -p |
| 42 |
> > |
| 43 |
> > It should now ask you to remove the old python, but check carefully the |
| 44 |
> > remaining packages in case something important is in the list and |
| 45 |
> > breaks your system. |
| 46 |
> |
| 47 |
> I do emerge --depclean -v -p. It says I should run emerge -uDN @world |
| 48 |
> first. I'm a bit apprehensive about this, since the world update says it |
| 49 |
> would reemerge 138 packages (I'm not sure whether this is top-level |
| 50 |
> (whatever that means) packages or the real total). In that list are 3 |
| 51 |
> blockages I don't know wha do do with. My experience suggests this will |
| 52 |
> not work smoothly, and I'll likely be left with a non-working (or even a |
| 53 |
> non-bootable) system. |
| 54 |
|
| 55 |
At this stage you should only run: |
| 56 |
|
| 57 |
python-updater -v |
| 58 |
|
| 59 |
Nothing else. |
| 60 |
|
| 61 |
Once it completes you can run --depclean which will ask you to remove the |
| 62 |
older 2.6 python package. |
| 63 |
|
| 64 |
|
| 65 |
> How come? Well, I started my installation in February 2010, and with one |
| 66 |
> thing and another, didn't get it finished, so it went into cold storage |
| 67 |
> until a month ago. I've had so much trouble trying to get updated, that |
| 68 |
> it might be better to start again from scratch with a new stage3 (or even |
| 69 |
> a new installation CD). This would surely leave my home directory and |
| 70 |
> suchlike untouched. What do you think? |
| 71 |
|
| 72 |
Adding the -N flag will remerge any packages that are affected by changes to |
| 73 |
USE flags that you have made since they were first installed. So the list |
| 74 |
will be longer than without it. |
| 75 |
-- |
| 76 |
Regards, |
| 77 |
Mick |
Archives