1 |
emerge --info |
2 |
Traceback (most recent call last): |
3 |
File "/usr/bin/emerge", line 43, in <module> |
4 |
retval = emerge_main() |
5 |
File "/usr/lib64/portage/pym/_emerge/main.py", line 1879, in emerge_main |
6 |
return action_info(settings, trees, myopts, valid_atoms) |
7 |
File "/usr/lib64/portage/pym/_emerge/actions.py", line 1407, in |
8 |
action_info |
9 |
repo = vardb.aux_get(cpv, ["repository"])[0] |
10 |
File "/usr/lib64/portage/pym/portage/dbapi/vartree.py", line 659, in |
11 |
aux_get |
12 |
self._aux_get(mycpv, aux_keys, st=mydir_stat)): |
13 |
File "/usr/lib64/portage/pym/portage/dbapi/vartree.py", line 690, in |
14 |
_aux_get |
15 |
raise KeyError(mycpv) |
16 |
KeyError: u'dev-lang/python-3.1.4-r3' |
17 |
|
18 |
2011/10/29 co <cuicle@×××××.com> |
19 |
|
20 |
> |
21 |
> |
22 |
> These are the packages that would be merged, in order: |
23 |
> |
24 |
> Calculating dependencies .... done! |
25 |
> [ebuild R ] sys-libs/pam-1.1.5 USE="berkdb cracklib nls vim-syntax |
26 |
> -audit -debug -nis (-selinux) -test" 0 kB |
27 |
> |
28 |
> Total: 1 package (1 reinstall), Size of downloads: 0 kB |
29 |
> |
30 |
> |
31 |
> >>> Verifying ebuild manifests |
32 |
> |
33 |
> >>> Emerging (1 of 1) sys-libs/pam-1.1.5 |
34 |
> * Linux-PAM-1.1.5.tar.bz2 RMD160 SHA1 SHA256 size ;-) ... [ |
35 |
> ok ] |
36 |
> * Linux-PAM-1.1.5-docs.tar.bz2 RMD160 SHA1 SHA256 size ;-) ... [ |
37 |
> ok ] |
38 |
> >>> Unpacking source... |
39 |
> >>> Unpacking Linux-PAM-1.1.5.tar.bz2 to |
40 |
> /var/tmp/portage/sys-libs/pam-1.1.5/work |
41 |
> tar: Linux-PAM-1.1.5/INSTALL: Cannot open: Invalid argument |
42 |
> tar: Linux-PAM-1.1.5/ABOUT-NLS: Cannot open: Invalid argument |
43 |
> tar: Linux-PAM-1.1.5/ChangeLog: Cannot open: Invalid argument |
44 |
> tar: Linux-PAM-1.1.5/COPYING: Cannot open: Invalid argument |
45 |
> tar: Linux-PAM-1.1.5/Make.xml.rules: Cannot open: Invalid argument |
46 |
> tar: Exiting with failure status due to previous errors |
47 |
> /usr/lib64/portage/bin/isolated-functions.sh: line 264: |
48 |
> /var/tmp/portage/sys-libs/pam-1.1.5/temp/logging/unpack: Invalid argument |
49 |
> * ERROR: sys-libs/pam-1.1.5 failed (unpack phase): |
50 |
> /usr/lib64/portage/bin/isolated-functions.sh: line 264: |
51 |
> /var/tmp/portage/sys-libs/pam-1.1.5/temp/logging/unpack: Invalid argument |
52 |
> * failure unpacking Linux-PAM-1.1.5.tar.bz2 |
53 |
> /usr/lib64/portage/bin/isolated-functions.sh: line 264: |
54 |
> /var/tmp/portage/sys-libs/pam-1.1.5/temp/logging/unpack: Invalid argument |
55 |
> * |
56 |
> /usr/lib64/portage/bin/isolated-functions.sh: line 264: |
57 |
> /var/tmp/portage/sys-libs/pam-1.1.5/temp/logging/unpack: Invalid argument |
58 |
> * Call stack: |
59 |
> /usr/lib64/portage/bin/isolated-functions.sh: line 264: |
60 |
> /var/tmp/portage/sys-libs/pam-1.1.5/temp/logging/unpack: Invalid argument |
61 |
> * ebuild.sh, line 56: Called src_unpack |
62 |
> /usr/lib64/portage/bin/isolated-functions.sh: line 264: |
63 |
> /var/tmp/portage/sys-libs/pam-1.1.5/temp/logging/unpack: Invalid argument |
64 |
> * environment, line 3487: Called _eapi0_src_unpack |
65 |
> /usr/lib64/portage/bin/isolated-functions.sh: line 264: |
66 |
> /var/tmp/portage/sys-libs/pam-1.1.5/temp/logging/unpack: Invalid argument |
67 |
> * ebuild.sh, line 622: Called unpack |
68 |
> 'Linux-PAM-1.1.5.tar.bz2' 'Linux-PAM-1.1.5-docs.tar.bz2' |
69 |
> /usr/lib64/portage/bin/isolated-functions.sh: line 264: |
70 |
> /var/tmp/portage/sys-libs/pam-1.1.5/temp/logging/unpack: Invalid argument |
71 |
> * ebuild.sh, line 401: Called _unpack_tar 'bzip2 -d' |
72 |
> /usr/lib64/portage/bin/isolated-functions.sh: line 264: |
73 |
> /var/tmp/portage/sys-libs/pam-1.1.5/temp/logging/unpack: Invalid argument |
74 |
> * ebuild.sh, line 371: Called assert_sigpipe_ok 'failure |
75 |
> unpacking Linux-PAM-1.1.5.tar.bz2' |
76 |
> /usr/lib64/portage/bin/isolated-functions.sh: line 264: |
77 |
> /var/tmp/portage/sys-libs/pam-1.1.5/temp/logging/unpack: Invalid argument |
78 |
> * isolated-functions.sh, line 37: Called die |
79 |
> /usr/lib64/portage/bin/isolated-functions.sh: line 264: |
80 |
> /var/tmp/portage/sys-libs/pam-1.1.5/temp/logging/unpack: Invalid argument |
81 |
> * The specific snippet of code: |
82 |
> /usr/lib64/portage/bin/isolated-functions.sh: line 264: |
83 |
> /var/tmp/portage/sys-libs/pam-1.1.5/temp/logging/unpack: Invalid argument |
84 |
> * [[ $x -ne 0 && $x -ne ${PORTAGE_SIGPIPE_STATUS:-141} ]] && die "$@" |
85 |
> /usr/lib64/portage/bin/isolated-functions.sh: line 264: |
86 |
> /var/tmp/portage/sys-libs/pam-1.1.5/temp/logging/unpack: Invalid argument |
87 |
> * |
88 |
> /usr/lib64/portage/bin/isolated-functions.sh: line 264: |
89 |
> /var/tmp/portage/sys-libs/pam-1.1.5/temp/logging/unpack: Invalid argument |
90 |
> * If you need support, post the output of 'emerge --info |
91 |
> =sys-libs/pam-1.1.5', |
92 |
> /usr/lib64/portage/bin/isolated-functions.sh: line 264: |
93 |
> /var/tmp/portage/sys-libs/pam-1.1.5/temp/logging/unpack: Invalid argument |
94 |
> * the complete build log and the output of 'emerge -pqv |
95 |
> =sys-libs/pam-1.1.5'. |
96 |
> /usr/lib64/portage/bin/isolated-functions.sh: line 211: |
97 |
> /var/tmp/portage/sys-libs/pam-1.1.5/.die_hooks: Invalid argument |
98 |
> /usr/lib64/portage/bin/isolated-functions.sh: line 264: |
99 |
> /var/tmp/portage/sys-libs/pam-1.1.5/temp/logging/unpack: Invalid argument |
100 |
> * The complete build log is located at |
101 |
> '/var/tmp/portage/sys-libs/pam-1.1.5/temp/build.log'. |
102 |
> /usr/lib64/portage/bin/isolated-functions.sh: line 264: |
103 |
> /var/tmp/portage/sys-libs/pam-1.1.5/temp/logging/unpack: Invalid argument |
104 |
> * The ebuild environment file is located at |
105 |
> '/var/tmp/portage/sys-libs/pam-1.1.5/temp/environment'. |
106 |
> /usr/lib64/portage/bin/isolated-functions.sh: line 264: |
107 |
> /var/tmp/portage/sys-libs/pam-1.1.5/temp/logging/unpack: Invalid argument |
108 |
> * S: '/var/tmp/portage/sys-libs/pam-1.1.5/work/Linux-PAM-1.1.5' |
109 |
> Traceback (most recent call last): |
110 |
> File "/usr/lib64/portage/bin/ebuild-ipc.py", line 276, in <module> |
111 |
> sys.exit(ebuild_ipc_main(sys.argv[1:])) |
112 |
> File "/usr/lib64/portage/bin/ebuild-ipc.py", line 273, in ebuild_ipc_main |
113 |
> return ebuild_ipc.communicate(args) |
114 |
> File "/usr/lib64/portage/bin/ebuild-ipc.py", line 63, in communicate |
115 |
> lock_obj = portage.locks.lockfile(self.ipc_lock_file, unlinkfile=True) |
116 |
> File "/usr/lib64/portage/pym/portage/locks.py", line 73, in lockfile |
117 |
> myfd = os.open(lockfilename, os.O_CREAT|os.O_RDWR, 0o660) |
118 |
> File "/usr/lib64/portage/pym/portage/__init__.py", line 215, in __call__ |
119 |
> rval = self._func(*wrapped_args, **wrapped_kwargs) |
120 |
> OSError: [Errno 22] Invalid argument: |
121 |
> '/var/tmp/portage/sys-libs/pam-1.1.5/.ipc_lock' |
122 |
> * The ebuild phase 'unpack' has exited unexpectedly. This type of behavior |
123 |
> * is known to be triggered by things such as failed variable assignments |
124 |
> * (bug #190128) or bad substitution errors (bug #200313). Normally, before |
125 |
> * exiting, bash should have displayed an error message above. If bash did |
126 |
> * not produce an error message above, it's possible that the ebuild has |
127 |
> * called `exit` when it should have called `die` instead. This behavior |
128 |
> * may also be triggered by a corrupt bash binary or a hardware problem |
129 |
> * such as memory or cpu malfunction. If the problem is not reproducible or |
130 |
> * it appears to occur randomly, then it is likely to be triggered by a |
131 |
> * hardware problem. If you suspect a hardware problem then you should try |
132 |
> * some basic hardware diagnostics such as memtest. Please do not report |
133 |
> * this as a bug unless it is consistently reproducible and you are sure |
134 |
> * that your bash binary and hardware are functioning properly. |
135 |
> /usr/lib64/portage/bin/misc-functions.sh: line 978: |
136 |
> /var/tmp/portage/sys-libs/pam-1.1.5/.die_hooks: Invalid argument |
137 |
> Traceback (most recent call last): |
138 |
> File "/usr/lib64/portage/bin/ebuild-ipc.py", line 276, in <module> |
139 |
> sys.exit(ebuild_ipc_main(sys.argv[1:])) |
140 |
> File "/usr/lib64/portage/bin/ebuild-ipc.py", line 273, in ebuild_ipc_main |
141 |
> return ebuild_ipc.communicate(args) |
142 |
> File "/usr/lib64/portage/bin/ebuild-ipc.py", line 63, in communicate |
143 |
> lock_obj = portage.locks.lockfile(self.ipc_lock_file, unlinkfile=True) |
144 |
> File "/usr/lib64/portage/pym/portage/locks.py", line 73, in lockfile |
145 |
> myfd = os.open(lockfilename, os.O_CREAT|os.O_RDWR, 0o660) |
146 |
> File "/usr/lib64/portage/pym/portage/__init__.py", line 215, in __call__ |
147 |
> rval = self._func(*wrapped_args, **wrapped_kwargs) |
148 |
> OSError: [Errno 22] Invalid argument: |
149 |
> '/var/tmp/portage/sys-libs/pam-1.1.5/.ipc_lock' |
150 |
> * The ebuild phase 'die_hooks' has exited unexpectedly. This type of |
151 |
> * behavior is known to be triggered by things such as failed variable |
152 |
> * assignments (bug #190128) or bad substitution errors (bug #200313). |
153 |
> * Normally, before exiting, bash should have displayed an error message |
154 |
> * above. If bash did not produce an error message above, it's possible |
155 |
> * that the ebuild has called `exit` when it should have called `die` |
156 |
> * instead. This behavior may also be triggered by a corrupt bash binary or |
157 |
> * a hardware problem such as memory or cpu malfunction. If the problem is |
158 |
> * not reproducible or it appears to occur randomly, then it is likely to |
159 |
> * be triggered by a hardware problem. If you suspect a hardware problem |
160 |
> * then you should try some basic hardware diagnostics such as memtest. |
161 |
> * Please do not report this as a bug unless it is consistently |
162 |
> * reproducible and you are sure that your bash binary and hardware are |
163 |
> * functioning properly. |
164 |
> |
165 |
> >>> Failed to emerge sys-libs/pam-1.1.5, Log file: |
166 |
> |
167 |
> >>> '/var/tmp/portage/sys-libs/pam-1.1.5/temp/build.log' |
168 |
> |
169 |
> * Messages for package sys-libs/pam-1.1.5: |
170 |
> |
171 |
> 2011/10/29 co <cuicle@×××××.com> |
172 |
> |
173 |
>> #ldd /sbin/rc |
174 |
>> linux-vdso.so.1 => (0x00007fff69fff000) |
175 |
>> libutil.so.1 => /lib64/libutil.so.1 (0x00007f617f00d000) |
176 |
>> librc.so.1 => /lib64/librc.so.1 (0x00007f617ee01000) |
177 |
>> libeinfo.so.1 => /lib64/libeinfo.so.1 (0x00007f617ebfb000) |
178 |
>> libdl.so.2 => /lib64/libdl.so.2 (0x00007f617e9f7000) |
179 |
>> libpam.so.0 => not found |
180 |
>> libc.so.6 => /lib64/libc.so.6 (0x00007f617e691000) |
181 |
>> libncurses.so.5 => /lib64/libncurses.so.5 (0x00007f617e440000) |
182 |
>> /lib64/ld-linux-x86-64.so.2 (0x00007f617f210000) |
183 |
>> thank you ahead. |
184 |
>> |
185 |
>> |
186 |
>> 2011/10/29 Adam Carter <adamcarter3@×××××.com> |
187 |
>> |
188 |
>>> > And i try to re-emerge pam,but i can't |
189 |
>>> |
190 |
>>> With the old file and links there I don't understand why your system |
191 |
>>> doesn't work, but re-emerging pam it definitely worth trying. What |
192 |
>>> fails when you try to re-emerge? |
193 |
>>> |
194 |
>>> Also, what about |
195 |
>>> # ldd /sbin/rc |
196 |
>>> |
197 |
>>> |
198 |
>> |
199 |
> |