1 |
Thanks Alan, |
2 |
Sorry for top posting. I noticed these very old machine have only |
3 |
8GB drives in them. Looks like I'm actually going to replace the |
4 |
drives and then do new installs from scratch. |
5 |
|
6 |
Thanks for your help! |
7 |
|
8 |
Cheers, |
9 |
Mark |
10 |
|
11 |
On Fri, Apr 25, 2008 at 2:59 PM, Alan McKinnon <alan.mckinnon@×××××.com> wrote: |
12 |
> On Friday 25 April 2008, Mark Knecht wrote: |
13 |
> > Hi, |
14 |
> > OK, so this machine I Was speaking of earlier seems ot have a |
15 |
> > number of issues created by a profile update. I'm attempting to move |
16 |
> > from 2005.0 to 2007.0. I'm using these documents as reference: |
17 |
> |
18 |
> Ooooh, this is gonna be fun! |
19 |
> |
20 |
> |
21 |
> > http://www.gentoo.org/doc/en/gentoo-upgrading.xml#doc_chap3 |
22 |
> > http://www.gentoo.org/proj/en/portage/doc/manually-fixing-portage.xml |
23 |
> > |
24 |
> > The second document is referenced because no version of portage in |
25 |
> > the library matches up with the version of python on this system. |
26 |
> > I've followed the instructions and now portage seems to work except I |
27 |
> > see this message which looks more like a warning than anything. Can I |
28 |
> > safely ignore it? |
29 |
> > |
30 |
> > myth11 ~ # emerge -pv system >>EmergeSystem.txt |
31 |
> > !!! Problem with sandbox binary. Disabling... |
32 |
> > |
33 |
> > !!! Problem with sandbox binary. Disabling... |
34 |
> |
35 |
> Yeah, I think you can disable it for long enough so that you can remerge |
36 |
> sandbox. Or just take it out of FEATURES till the upgrade is complete |
37 |
> |
38 |
> |
39 |
> |
40 |
> > myth11 ~ # |
41 |
> > |
42 |
> > |
43 |
> > More important are some blocking issues. From the text file I saved |
44 |
> > in the step above I have these blocks: |
45 |
> > |
46 |
> > |
47 |
> > These are the packages that would be merged, in order: |
48 |
> > |
49 |
> > Calculating system dependencies .^H^H... done! |
50 |
> > [blocks B ] <dev-lang/python-2.3.6-r2 (is blocking |
51 |
> > app-admin/python-updater-0.2) |
52 |
> > [blocks B ] <sys-apps/util-linux-2.13 (is blocking |
53 |
> > sys-apps/coreutils-6.10-r2) |
54 |
> > [blocks B ] sys-apps/pam-login (is blocking |
55 |
> > sys-apps/shadow-4.0.18.2) |
56 |
> > |
57 |
> > |
58 |
> > Are these blocks safe to remove? I assume they are system stuff and |
59 |
> > hence the system might break. |
60 |
> |
61 |
> Here's a mail I sent to my colleagues about the python blocks. I'm sure |
62 |
> there's any easier way, I just didn't find it at the time: |
63 |
> |
64 |
> ===================== |
65 |
> Upgrading python on stable x86 boxes is a pain in the you know what. |
66 |
> This time it is worse than usual. Just like the usual bootstrap problem |
67 |
> of "you need a compiled compiler to compile a compiler so how do you |
68 |
> compile a compiler?" on Gentoo portage is written in python so if you |
69 |
> unmerge python to resolve a blocker, how do you then update python? |
70 |
> |
71 |
> Most of our boxes will have python in SLOTS 2.2 and 2.3 and 2.4 |
72 |
> This is a waste, you only need one. Hence the existence of |
73 |
> python-updater. It works like revdep-rebuild, and finds stuff using |
74 |
> python then rebuilds then to link to the most recent version. Latest |
75 |
> python DEPENDS on python-updater. |
76 |
> |
77 |
> However, python-updater blocks <=python-2.3.something, so portage is |
78 |
> going to bitch about those SLOTS. I can think of 2 procedures to |
79 |
> resolve this, only one is tested (credit to Stef for this) |
80 |
> |
81 |
> run 'emerge --nodeps python-updater' |
82 |
> run 'python-updater' |
83 |
> This will take a while usually. |
84 |
> Use eix to find all merged versions of python. Unmerge all SLOTS <2.4. |
85 |
> DO NOT UNMERGE PYTHON-2.4!!!! |
86 |
> Now run any portage tool. It will fail with "/usr/bin/python - no such |
87 |
> file". Mwahahaha. |
88 |
> Relax, python is not borked. The last unmerge will have deleted a |
89 |
> symlink. Put it back: |
90 |
> |
91 |
> ln -s /usr/bin/python2.4 /usr/bin/python |
92 |
> |
93 |
> Portage will now work again. |
94 |
> ================= |
95 |
> |
96 |
> |
97 |
> util-linux needs to be removed to build coreutils as there is duplicate |
98 |
> functionality. |
99 |
> |
100 |
> DO NOT UNMERGE COREUTILS!!!!!!!! Just don't even try.... |
101 |
> |
102 |
> emerge -C util-linux ; emerge coreutils ; emerge util-linux |
103 |
> |
104 |
> I prefer to get these done and out of the way asap, rather than |
105 |
> unmerging a blocker and hoping emerge world will fix stuff as it runs |
106 |
> it's course. What is it doesn't and the box is left inconsistent? |
107 |
> |
108 |
> pam-login no longer exists and it's functionality is replaced by shadow: |
109 |
> |
110 |
> emerge -C pam-login ; emerge shadow |
111 |
> |
112 |
> While doing this, keep a second root shell open. After the merge, |
113 |
> confirm you can log out of the original shell and correctly log back |
114 |
> in. If the shadow merged went wrong somehow, or your pam is funny, you |
115 |
> still have a working shell running to fix it. Otherwise, time to fetch |
116 |
> the trusty LiveCD |
117 |
> |
118 |
> > thanks in advance, |
119 |
> > Mark |
120 |
> |
121 |
> |
122 |
> |
123 |
> -- |
124 |
> Alan McKinnon |
125 |
> alan dot mckinnon at gmail dot com |
126 |
> |
127 |
> -- |
128 |
> gentoo-user@l.g.o mailing list |
129 |
> |
130 |
> |
131 |
-- |
132 |
gentoo-user@l.g.o mailing list |