Summary: | emerge --info: No module named _md5 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | ade05fr <ade05fr> |
Component: | [OLD] Core system | Assignee: | Python Gentoo Team <python> |
Status: | RESOLVED DUPLICATE | ||
Severity: | major | CC: | jer, pchrist |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
ade05fr
2008-11-01 17:38:50 UTC
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. > 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 *** |