Albert Hopkins wrote:
>
> First question: what did you do?
>
> # python
> Python 2.4.4 (#1, Jan 2 2007, 19:55:21)
> [GCC 4.1.1 (Gentoo 4.1.1-r3)] on linux2
> Type "help", "copyright", "credits" or "license" for more
> information.
> >>> import time
> >>> time.__file__
> '/usr/lib/python2.4/lib-dynload/time.so'
>
> Make sure that file exists and that the files that it links to exist.
>
>
>
First of all thank you very much! :))
Actually I don't know what happened yet. I have another system with the
same hardware, the same software configuration and almost the same world
file. The first thing I checked after your message was:
"ls -la /usr/lib/python2.4/lib-dynload/"
on the broken system and it showed an empty dir. Next I made the same
check on the healthy system and it was full of files including
"time.so". So, I transfered the whole directory to the broken system and
now "emerge" works fine (at least at first glance).
Thanks again!
[OT]
Strange.
I did
"qfile time.so"
on the healthy system and it gave no results. Also I did
"qlist python | grep time.so"
and it gave no results either. I suspect something went wrong on both
systems but I'm not sure what and how to fix it.
Even more strange.
Before sending my question here I tried
"quickpkg python portage"
and extracted the contents of the archives in the root ("/") dir of the
broken system. This action didn't help. After your answer I checked the
contents of the packages made by "quickpkg":
localhost / # tar jtf python-2.4.3-r4.tbz2 | grep lib-dyn
./usr/lib/python2.4/lib-dynload/
bzip2: (stdin): trailing garbage after EOF ignored
localhost / # tar jtf portage-2.1.1-r2.tbz2 | grep lib-dyn
bzip2: (stdin): trailing garbage after EOF ignored
It appears that python only creates this directory, but I can't figure
out which packages put files in it.
Is it normal?
--
Best regards,
Daniel
--
[email protected] mailing list
