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