1 |
Hello all, |
2 |
|
3 |
I am using the same topic as Rafael Barrera Oro the 6th of September 2007 |
4 |
|
5 |
I updated portage |
6 |
from sys-apps/portage-2.0.54-r2 |
7 |
to sys-apps/portage-2.1.3.19 |
8 |
And the unmerging of sys-apps/portage-2.0.54-r2 |
9 |
ended like this : |
10 |
---------------------------------------------------------------------- |
11 |
* |
12 |
* FEATURES="userfetch" is now enabled by default. Depending on your ${DISTDIR} |
13 |
* permissions, this may result in Permission Denied errors. If you would like |
14 |
* to fetch with superuser privileges, add FEATURES="-userfetch" to make.conf. |
15 |
* |
16 |
* The world file now supports slot atoms such as 'sys-devel/gcc:3.4'. In some |
17 |
* cases, emerge --depclean may remove slots that it would not have removed |
18 |
* in the past. The emerge --noreplace command can be used to add an atom to |
19 |
* the world file and prevent matching packages from being removed. A slot |
20 |
* atom will be recorded in the world file for any atom that is precise enough |
21 |
* to identify a specific slot. |
22 |
* |
23 |
* For help with using portage please consult the Gentoo Handbook |
24 |
* at http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=3 |
25 |
* |
26 |
>>> Regenerating /etc/ld.so.cache... |
27 |
>>> sys-apps/portage-2.1.3.19 merged. |
28 |
|
29 |
sys-apps/portage |
30 |
selected: 2.0.54-r2 |
31 |
protected: 2.1.3.19 |
32 |
omitted: none |
33 |
|
34 |
>>> 'Selected' packages are slated for removal. |
35 |
>>> 'Protected' and 'omitted' packages will not be removed. |
36 |
|
37 |
>>> Waiting 5 seconds before starting... |
38 |
>>> (Control-C to abort)... |
39 |
>>> Unmerging in: 5 4 3 2 1 |
40 |
>>> Unmerging sys-apps/portage-2.0.54-r2... |
41 |
No package files given... Grabbing a set. |
42 |
--- !mtime obj /usr/share/man/man5/portage.5.gz |
43 |
--- !mtime obj /usr/share/man/man5/make.conf.5.gz |
44 |
--- !mtime obj /usr/share/man/man5/ebuild.5.gz |
45 |
--- !mtime obj /usr/share/man/man1/repoman.1.gz |
46 |
--- !mtime obj /usr/share/man/man1/quickpkg.1.gz |
47 |
--- !mtime obj /usr/share/man/man1/etc-update.1.gz |
48 |
--- !mtime obj /usr/share/man/man1/env-update.1.gz |
49 |
--- !mtime obj /usr/share/man/man1/emerge.1.gz |
50 |
--- !mtime obj /usr/share/man/man1/ebuild.1.gz |
51 |
--- !mtime obj /usr/share/man/man1/dispatch-conf.1.gz |
52 |
[... lines snipped ...] |
53 |
--- !empty dir /usr/share/man/man5 |
54 |
--- !empty dir /usr/share/man/man1 |
55 |
--- !empty dir /usr/share/man |
56 |
--- !empty dir /usr/share/doc |
57 |
--- !empty dir /usr/share |
58 |
--- !empty dir /usr/sbin |
59 |
--- !empty dir /usr/lib/python2.4/site-packages |
60 |
--- !empty dir /usr/lib/python2.4 |
61 |
--- !empty dir /usr/lib/portage/pym |
62 |
--- !empty dir /usr/lib/portage |
63 |
--- !empty dir /usr/lib |
64 |
--- !empty dir /usr/bin |
65 |
--- !empty dir /usr |
66 |
--- !empty dir /etc |
67 |
--- !targe sym /usr/sbin/regenworld |
68 |
--- !targe sym /usr/sbin/quickpkg |
69 |
--- !targe sym /usr/sbin/fixpackages |
70 |
--- !targe sym /usr/sbin/etc-update |
71 |
--- !targe sym /usr/sbin/env-update |
72 |
--- !targe sym /usr/sbin/emerge-webrsync |
73 |
--- !targe sym /usr/sbin/emaint |
74 |
--- !targe sym /usr/sbin/dispatch-conf |
75 |
--- !targe sym /usr/sbin/archive-conf |
76 |
--- !targe sym /usr/bin/xpak |
77 |
--- !targe sym /usr/bin/tbz2tool |
78 |
--- !targe sym /usr/bin/repoman |
79 |
--- !targe sym /usr/bin/portageq |
80 |
--- !targe sym /usr/bin/emerge |
81 |
--- !targe sym /usr/bin/ebuild |
82 |
[portage-2.0.54-r2] bash: /usr/lib/portage/bin/ebuild.sh: No such file or directory |
83 |
!!! FAILED postrm: 127 |
84 |
---------------------------------------------------------------------- |
85 |
|
86 |
|
87 |
|
88 |
|
89 |
|
90 |
Ok now everytime I try to use emerge I get this : |
91 |
root ~ # emerge -s alfred |
92 |
Traceback (most recent call last): |
93 |
File "/usr/bin/emerge", line 37, in ? |
94 |
from output import blue, bold, colorize, darkblue, darkgreen, darkred, green, \ |
95 |
ImportError: cannot import name colorize |
96 |
|
97 |
|
98 |
and I guess I found the source and have to reinstall portage manually |
99 |
The fact is that i changed the make.profile to a 64 bits profile since |
100 |
the server I use is said to be 64 bits . |
101 |
but it's a : |
102 |
vendor_id : GenuineIntel |
103 |
model name : Intel(R) Core(TM)2 Duo CPU E6750 @ 2.66GHz |
104 |
clflush size : 64 |
105 |
vendor_id : GenuineIntel |
106 |
model name : Intel(R) Core(TM)2 Duo CPU E6750 @ 2.66GHz |
107 |
clflush size : 64 |
108 |
|
109 |
So now when I get : |
110 |
root ~ # ls -l $(whereis emerge) 2>> /dev/null |
111 |
lrwxrwxrwx 1 root root 27 déc 18 16:22 /usr/bin/emerge -> ../lib64/portage/bin/emerge |
112 |
-rw-r--r-- 1 root root 11305 déc 18 16:22 /usr/share/man/man1/emerge.1.gz |
113 |
|
114 |
So I suppose my Intel can't execute that lib64 portage binary !!!! |
115 |
So I'll link my make.profile back to a normal x86 arch |
116 |
and reinstall portage manually... |
117 |
|
118 |
Anyone any better suggestion ? |
119 |
|
120 |
Thanks in advance, |
121 |
|
122 |
-- |
123 |
Redouane BOUMGHAR |
124 |
Physics, Remote Sensing and Digital Imagery |
125 |
|
126 |
-- |
127 |
gentoo-user@g.o mailing list |