emerge --info
Traceback (most recent call last):
File "/usr/bin/emerge", line 43, in <module>
retval = emerge_main()
File "/usr/lib64/portage/pym/_emerge/main.py", line 1879, in emerge_main
return action_info(settings, trees, myopts, valid_atoms)
File "/usr/lib64/portage/pym/_emerge/actions.py", line 1407, in
action_info
repo = vardb.aux_get(cpv, ["repository"])[0]
File "/usr/lib64/portage/pym/portage/dbapi/vartree.py", line 659, in
aux_get
self._aux_get(mycpv, aux_keys, st=mydir_stat)):
File "/usr/lib64/portage/pym/portage/dbapi/vartree.py", line 690, in
_aux_get
raise KeyError(mycpv)
KeyError: u'dev-lang/python-3.1.4-r3'
2011/10/29 co <[email protected]>
>
>
> These are the packages that would be merged, in order:
>
> Calculating dependencies .... done!
> [ebuild R ] sys-libs/pam-1.1.5 USE="berkdb cracklib nls vim-syntax
> -audit -debug -nis (-selinux) -test" 0 kB
>
> Total: 1 package (1 reinstall), Size of downloads: 0 kB
>
>
> >>> Verifying ebuild manifests
>
> >>> Emerging (1 of 1) sys-libs/pam-1.1.5
> * Linux-PAM-1.1.5.tar.bz2 RMD160 SHA1 SHA256 size ;-) ... [
> ok ]
> * Linux-PAM-1.1.5-docs.tar.bz2 RMD160 SHA1 SHA256 size ;-) ... [
> ok ]
> >>> Unpacking source...
> >>> Unpacking Linux-PAM-1.1.5.tar.bz2 to
> /var/tmp/portage/sys-libs/pam-1.1.5/work
> tar: Linux-PAM-1.1.5/INSTALL: Cannot open: Invalid argument
> tar: Linux-PAM-1.1.5/ABOUT-NLS: Cannot open: Invalid argument
> tar: Linux-PAM-1.1.5/ChangeLog: Cannot open: Invalid argument
> tar: Linux-PAM-1.1.5/COPYING: Cannot open: Invalid argument
> tar: Linux-PAM-1.1.5/Make.xml.rules: Cannot open: Invalid argument
> tar: Exiting with failure status due to previous errors
> /usr/lib64/portage/bin/isolated-functions.sh: line 264:
> /var/tmp/portage/sys-libs/pam-1.1.5/temp/logging/unpack: Invalid argument
> * ERROR: sys-libs/pam-1.1.5 failed (unpack phase):
> /usr/lib64/portage/bin/isolated-functions.sh: line 264:
> /var/tmp/portage/sys-libs/pam-1.1.5/temp/logging/unpack: Invalid argument
> * failure unpacking Linux-PAM-1.1.5.tar.bz2
> /usr/lib64/portage/bin/isolated-functions.sh: line 264:
> /var/tmp/portage/sys-libs/pam-1.1.5/temp/logging/unpack: Invalid argument
> *
> /usr/lib64/portage/bin/isolated-functions.sh: line 264:
> /var/tmp/portage/sys-libs/pam-1.1.5/temp/logging/unpack: Invalid argument
> * Call stack:
> /usr/lib64/portage/bin/isolated-functions.sh: line 264:
> /var/tmp/portage/sys-libs/pam-1.1.5/temp/logging/unpack: Invalid argument
> * ebuild.sh, line 56: Called src_unpack
> /usr/lib64/portage/bin/isolated-functions.sh: line 264:
> /var/tmp/portage/sys-libs/pam-1.1.5/temp/logging/unpack: Invalid argument
> * environment, line 3487: Called _eapi0_src_unpack
> /usr/lib64/portage/bin/isolated-functions.sh: line 264:
> /var/tmp/portage/sys-libs/pam-1.1.5/temp/logging/unpack: Invalid argument
> * ebuild.sh, line 622: Called unpack
> 'Linux-PAM-1.1.5.tar.bz2' 'Linux-PAM-1.1.5-docs.tar.bz2'
> /usr/lib64/portage/bin/isolated-functions.sh: line 264:
> /var/tmp/portage/sys-libs/pam-1.1.5/temp/logging/unpack: Invalid argument
> * ebuild.sh, line 401: Called _unpack_tar 'bzip2 -d'
> /usr/lib64/portage/bin/isolated-functions.sh: line 264:
> /var/tmp/portage/sys-libs/pam-1.1.5/temp/logging/unpack: Invalid argument
> * ebuild.sh, line 371: Called assert_sigpipe_ok 'failure
> unpacking Linux-PAM-1.1.5.tar.bz2'
> /usr/lib64/portage/bin/isolated-functions.sh: line 264:
> /var/tmp/portage/sys-libs/pam-1.1.5/temp/logging/unpack: Invalid argument
> * isolated-functions.sh, line 37: Called die
> /usr/lib64/portage/bin/isolated-functions.sh: line 264:
> /var/tmp/portage/sys-libs/pam-1.1.5/temp/logging/unpack: Invalid argument
> * The specific snippet of code:
> /usr/lib64/portage/bin/isolated-functions.sh: line 264:
> /var/tmp/portage/sys-libs/pam-1.1.5/temp/logging/unpack: Invalid argument
> * [[ $x -ne 0 && $x -ne ${PORTAGE_SIGPIPE_STATUS:-141} ]] && die "$@"
> /usr/lib64/portage/bin/isolated-functions.sh: line 264:
> /var/tmp/portage/sys-libs/pam-1.1.5/temp/logging/unpack: Invalid argument
> *
> /usr/lib64/portage/bin/isolated-functions.sh: line 264:
> /var/tmp/portage/sys-libs/pam-1.1.5/temp/logging/unpack: Invalid argument
> * If you need support, post the output of 'emerge --info
> =sys-libs/pam-1.1.5',
> /usr/lib64/portage/bin/isolated-functions.sh: line 264:
> /var/tmp/portage/sys-libs/pam-1.1.5/temp/logging/unpack: Invalid argument
> * the complete build log and the output of 'emerge -pqv
> =sys-libs/pam-1.1.5'.
> /usr/lib64/portage/bin/isolated-functions.sh: line 211:
> /var/tmp/portage/sys-libs/pam-1.1.5/.die_hooks: Invalid argument
> /usr/lib64/portage/bin/isolated-functions.sh: line 264:
> /var/tmp/portage/sys-libs/pam-1.1.5/temp/logging/unpack: Invalid argument
> * The complete build log is located at
> '/var/tmp/portage/sys-libs/pam-1.1.5/temp/build.log'.
> /usr/lib64/portage/bin/isolated-functions.sh: line 264:
> /var/tmp/portage/sys-libs/pam-1.1.5/temp/logging/unpack: Invalid argument
> * The ebuild environment file is located at
> '/var/tmp/portage/sys-libs/pam-1.1.5/temp/environment'.
> /usr/lib64/portage/bin/isolated-functions.sh: line 264:
> /var/tmp/portage/sys-libs/pam-1.1.5/temp/logging/unpack: Invalid argument
> * S: '/var/tmp/portage/sys-libs/pam-1.1.5/work/Linux-PAM-1.1.5'
> Traceback (most recent call last):
> File "/usr/lib64/portage/bin/ebuild-ipc.py", line 276, in <module>
> sys.exit(ebuild_ipc_main(sys.argv[1:]))
> File "/usr/lib64/portage/bin/ebuild-ipc.py", line 273, in ebuild_ipc_main
> return ebuild_ipc.communicate(args)
> File "/usr/lib64/portage/bin/ebuild-ipc.py", line 63, in communicate
> lock_obj = portage.locks.lockfile(self.ipc_lock_file, unlinkfile=True)
> File "/usr/lib64/portage/pym/portage/locks.py", line 73, in lockfile
> myfd = os.open(lockfilename, os.O_CREAT|os.O_RDWR, 0o660)
> File "/usr/lib64/portage/pym/portage/__init__.py", line 215, in __call__
> rval = self._func(*wrapped_args, **wrapped_kwargs)
> OSError: [Errno 22] Invalid argument:
> '/var/tmp/portage/sys-libs/pam-1.1.5/.ipc_lock'
> * The ebuild phase 'unpack' has exited unexpectedly. This type of behavior
> * is known to be triggered by things such as failed variable assignments
> * (bug #190128) or bad substitution errors (bug #200313). Normally, before
> * exiting, bash should have displayed an error message above. If bash did
> * not produce an error message above, it's possible that the ebuild has
> * called `exit` when it should have called `die` instead. This behavior
> * may also be triggered by a corrupt bash binary or a hardware problem
> * such as memory or cpu malfunction. If the problem is not reproducible or
> * it appears to occur randomly, then it is likely to be triggered by a
> * hardware problem. If you suspect a hardware problem then you should try
> * some basic hardware diagnostics such as memtest. Please do not report
> * this as a bug unless it is consistently reproducible and you are sure
> * that your bash binary and hardware are functioning properly.
> /usr/lib64/portage/bin/misc-functions.sh: line 978:
> /var/tmp/portage/sys-libs/pam-1.1.5/.die_hooks: Invalid argument
> Traceback (most recent call last):
> File "/usr/lib64/portage/bin/ebuild-ipc.py", line 276, in <module>
> sys.exit(ebuild_ipc_main(sys.argv[1:]))
> File "/usr/lib64/portage/bin/ebuild-ipc.py", line 273, in ebuild_ipc_main
> return ebuild_ipc.communicate(args)
> File "/usr/lib64/portage/bin/ebuild-ipc.py", line 63, in communicate
> lock_obj = portage.locks.lockfile(self.ipc_lock_file, unlinkfile=True)
> File "/usr/lib64/portage/pym/portage/locks.py", line 73, in lockfile
> myfd = os.open(lockfilename, os.O_CREAT|os.O_RDWR, 0o660)
> File "/usr/lib64/portage/pym/portage/__init__.py", line 215, in __call__
> rval = self._func(*wrapped_args, **wrapped_kwargs)
> OSError: [Errno 22] Invalid argument:
> '/var/tmp/portage/sys-libs/pam-1.1.5/.ipc_lock'
> * The ebuild phase 'die_hooks' has exited unexpectedly. This type of
> * behavior is known to be triggered by things such as failed variable
> * assignments (bug #190128) or bad substitution errors (bug #200313).
> * Normally, before exiting, bash should have displayed an error message
> * above. If bash did not produce an error message above, it's possible
> * that the ebuild has called `exit` when it should have called `die`
> * instead. This behavior may also be triggered by a corrupt bash binary or
> * a hardware problem such as memory or cpu malfunction. If the problem is
> * not reproducible or it appears to occur randomly, then it is likely to
> * be triggered by a hardware problem. If you suspect a hardware problem
> * then you should try some basic hardware diagnostics such as memtest.
> * Please do not report this as a bug unless it is consistently
> * reproducible and you are sure that your bash binary and hardware are
> * functioning properly.
>
> >>> Failed to emerge sys-libs/pam-1.1.5, Log file:
>
> >>> '/var/tmp/portage/sys-libs/pam-1.1.5/temp/build.log'
>
> * Messages for package sys-libs/pam-1.1.5:
>
> 2011/10/29 co <[email protected]>
>
>> #ldd /sbin/rc
>> linux-vdso.so.1 => (0x00007fff69fff000)
>> libutil.so.1 => /lib64/libutil.so.1 (0x00007f617f00d000)
>> librc.so.1 => /lib64/librc.so.1 (0x00007f617ee01000)
>> libeinfo.so.1 => /lib64/libeinfo.so.1 (0x00007f617ebfb000)
>> libdl.so.2 => /lib64/libdl.so.2 (0x00007f617e9f7000)
>> libpam.so.0 => not found
>> libc.so.6 => /lib64/libc.so.6 (0x00007f617e691000)
>> libncurses.so.5 => /lib64/libncurses.so.5 (0x00007f617e440000)
>> /lib64/ld-linux-x86-64.so.2 (0x00007f617f210000)
>> thank you ahead.
>>
>>
>> 2011/10/29 Adam Carter <[email protected]>
>>
>>> > And i try to re-emerge pam,but i can't
>>>
>>> With the old file and links there I don't understand why your system
>>> doesn't work, but re-emerging pam it definitely worth trying. What
>>> fails when you try to re-emerge?
>>>
>>> Also, what about
>>> # ldd /sbin/rc
>>>
>>>
>>
>
