Hello since my "emerge -C mktemp ss com_err" i cant emerge anything. I think python is broken. How can i restore it ? Reproducible: Always Steps to Reproduce: 1.emerge -C mktemp ss com_err 2.emerge ss 3. Actual Results: # emerge --info !!! Failed to complete portage imports. There are internal modules for !!! portage and failure here indicates that you have a problem with your !!! installation of portage. Please try a rescue portage located in the !!! portage tree under '/usr/portage/sys-apps/portage/files/' (default). !!! There is a README.RESCUE file that details the steps required to perform !!! a recovery of portage. No module named _md5 !!! Failed to complete portage imports. There are internal modules for !!! portage and failure here indicates that you have a problem with your !!! installation of portage. Please try a rescue portage located in the !!! portage tree under '/usr/portage/sys-apps/portage/files/' (default). !!! There is a README.RESCUE file that details the steps required to perform !!! a recovery of portage. No module named _md5 Traceback (most recent call last): File "/usr/bin/emerge", line 31, in <module> import portage File "/usr/lib64/portage/pym/portage/__init__.py", line 79, in <module> import portage.getbinpkg File "/usr/lib64/portage/pym/portage/getbinpkg.py", line 15, in <module> import urllib2 File "/usr/lib64/python2.5/urllib2.py", line 88, in <module> import hashlib File "/usr/lib64/python2.5/hashlib.py", line 133, in <module> md5 = __get_builtin_constructor('md5') File "/usr/lib64/python2.5/hashlib.py", line 60, in __get_builtin_constructor import _md5 ImportError: No module named _md5
It seems that you broke your portage or something. Please provide more info(emerge --info output etc.) Reopen when you have submitted these info.
@pchrist: Please allow about a day to pass before closing as NEEDINFO. :)
(In reply to comment #1) > It seems that you broke your portage or something. Please provide more > info(emerge --info output etc.) Reopen when you have submitted these info. > hello as i mentionned in the bug before i cant give you emerge --info because the emerge commande line is not working anymore.
It seems like this might be triggered by openssl breakage due to being built with kerberos support, and the mit-krb5 dependence on ss and com_err. You might be able to untar some packages from our tinderbox to get it working again: http://tinderbox.dev.gentoo.org/html/ If you have a linux/amd64 system then these packages might work for you: http://tinderbox.dev.gentoo.org/html/default-linux/amd64/All/
which packages do i have to install again ? i have unmerge ss and com_err to install e2fsprogs and i havent updated openssl for a while. thanks (In reply to comment #4) > It seems like this might be triggered by openssl breakage due to being built > with kerberos support, and the mit-krb5 dependence on ss and com_err. > > You might be able to untar some packages from our tinderbox to get it working > again: > > http://tinderbox.dev.gentoo.org/html/ > > If you have a linux/amd64 system then these packages might work for you: > > http://tinderbox.dev.gentoo.org/html/default-linux/amd64/All/ >
(In reply to comment #5) > which packages do i have to install again ? > i have unmerge ss and com_err to install e2fsprogs First unpack ss and com_err and then run ldconfig. Maybe then python work again.
i have done untar of the com_err and ss packages and copy all the files to the target folder and then made a ldconfig. problem is still here. (In reply to comment #6) > (In reply to comment #5) > > which packages do i have to install again ? > > i have unmerge ss and com_err to install e2fsprogs > > First unpack ss and com_err and then run ldconfig. Maybe then python work > again. >
Does /usr/lib64/python2.5/lib-dynload/_md5.so exist? If it does exist, it seems to be broken in some way. That file belongs to python so you'll probably want to download a python tarball from the tinderbox and unpack it on your system.
The "No module named _md5" error is the same as bug 198447 and bug 191577.
*** This bug has been marked as a duplicate of bug 198447 ***