1 |
On Monday 25 April 2011 13:11:53 Alan Mackenzie wrote: |
2 |
> Hi, Mick. |
3 |
> |
4 |
> On Sun, Apr 24, 2011 at 04:44:05PM +0100, Mick wrote: |
5 |
> > On Sunday 24 April 2011 14:25:58 Alan Mackenzie wrote: |
6 |
> > > Hi, Mick. |
7 |
> > > |
8 |
> > > On Sun, Apr 24, 2011 at 09:17:45AM +0100, Mick wrote: |
9 |
> > > > On Saturday 23 April 2011 21:06:25 Alan Mackenzie wrote: |
10 |
> > > > > On Sat, Apr 23, 2011 at 08:46:30PM +0100, Mick wrote: |
11 |
> > > > python-updater -v -p |
12 |
> > > > |
13 |
> > > > to get a list of these. |
14 |
> > > |
15 |
> > > That gives me a list of 24 packages. Am I meant to actually run |
16 |
> > > python-updater without the -p, here? |
17 |
> > |
18 |
> > That's correct. As the man emerge say -p stands for --pretend. Just |
19 |
> > to give a chance to see what it wants to do and think about it before |
20 |
> > you run it again without it for execution. |
21 |
> > |
22 |
> > You need to do this next. |
23 |
> |
24 |
> DONE. |
25 |
> |
26 |
> > > > When you finish all this you can run: |
27 |
> > > > |
28 |
> > > > emerge --depclean -v -p |
29 |
> > > > |
30 |
> > > > It should now ask you to remove the old python, but check carefully |
31 |
> > > > the remaining packages in case something important is in the list |
32 |
> > > > and breaks your system. |
33 |
> > > |
34 |
> > > I do emerge --depclean -v -p. It says I should run emerge -uDN |
35 |
> > > @world first. I'm a bit apprehensive about this, since the world |
36 |
> > > update says it would reemerge 138 packages (I'm not sure whether this |
37 |
> > > is top-level (whatever that means) packages or the real total). In |
38 |
> > > that list are 3 blockages I don't know wha do do with. My experience |
39 |
> > > suggests this will not work smoothly, and I'll likely be left with a |
40 |
> > > non-working (or even a non-bootable) system. |
41 |
> > |
42 |
> > At this stage you should only run: |
43 |
> > |
44 |
> > python-updater -v |
45 |
> > |
46 |
> > Nothing else. |
47 |
> > |
48 |
> > Once it completes you can run --depclean which will ask you to remove |
49 |
> > the older 2.6 python package. |
50 |
> |
51 |
> I had to (or, at least, did) run emerge -uND @world. Funnily enough, it |
52 |
> ran to completion without manual intervention. :-) I'd like to run |
53 |
> --depclean, but it's threatening to remove my 2.6.31-r6 kernel sources, |
54 |
> which correspond to my working kernel. What's the easiest way to protect |
55 |
> these from --depclean? |
56 |
|
57 |
Aha! That's why I said first look at what it wants to remove - you don't want |
58 |
to cripple your system. In this case of course it won't cripple anything, |
59 |
because it won't remove the kernel image from /boot/ |
60 |
|
61 |
If you look in /usr/src/linux/ you will see a number of kernel sources listed |
62 |
in there. If you've run update world there should be a more up-to-date kernel |
63 |
awaiting for you to configure and compile it. Do that first; copy the |
64 |
necessary files into /boot; configure grub.conf to boot with you latest |
65 |
kernel; and after you boot into it and check that all is good you can allow -- |
66 |
depclean to remove older kernel source files. |
67 |
|
68 |
PS. You may need to manually remove older source files left in |
69 |
/usr/src/linux/ when depclean completes its job. |
70 |
-- |
71 |
Regards, |
72 |
Mick |