After emerge -u world where python was updated, I now get the following error when I try to emerge packages Traceback (most recent call last): File "/usr/bin/emerge", line 14, in ? import portage File "/usr/lib/portage/pym/portage.py", line 11, in ? import time,cPickle,atexit,grp,traceback,commands,pwd,cvstree,copy ImportError: No module named cPickle I tried python-updater which also failed with a similar message Reproducible: Always Steps to Reproduce: 1. emerge -up world 2. python upgrades 3. unable to emerge anything else Expected Results: portage should retain functionality after the python upgrade
please attach your /etc/make.conf.
Created attachment 31591 [details] /etc/make.conf file from the computer in question
I have worked around this bug as follows: deleted the /usr/lib/python2.3 directory copied the /usr/lib/python2.3 directory from another computer on the network everything appears to be working now. I don't know what went wrong, but all of the modules didn't build for me. Python itself (/usr/bin/python) appeared to be working fine.
Does the newer version of Python, 2.3.4, work correctly for you?
I am using 2.3.4 with no problems. It hasn't updated again that I have noticed.
what version of python were you updating from and to what version?
What version of gcc do you have? Also, please attach a result of 'ls -lR /usr/lib/python2.3' command and your /var/db/pkg/dev-lang/python-2.3.4/CONTENTS file.
I have make.conf set for unstable "~x86" 2.3.4 showed up when I synced on 5/15/04. I don't know which version I was running previously. I bootstrapped the system about April 20th and I have a usr/lib/python2.2 directory so it might have been a 2.2 version.
gcc is 3.3.3-r6 I have attached the other two pieces that you requested. Remember that I copied over the /usr/lib/python2.3 directory from another computer on the network.
Created attachment 33113 [details] ls -IR /usr/lib/python2.3
Created attachment 33115 [details] /var/db/pkg/dev-lang/python-2.3.4/CONTENTS I appreciate the interest in this problem. I wanted to let you know that I am taking my system down at midnight and moving across the country. I won't be back online for 2 weeks so please accept my apologies if this causes any delays for you.
i can't tell whats gone wrong .. cpickle.so seems to be installed with a non-zero size.
Remember that cpickle.so is only present and non-zero in size because I copied the directory from another computer. It was not present following the errant build.
are you sure? its in your CONTENTS file, so its must of been on your machine, unless the disk was full or something?
When things weren't working, I looked in /usr/lib/python2.3 for cpickle and it wasn't present. When I searched for cpickle I didn't find it anywhere in the directory tree. I subsequently looked for it on another computer and it was in /usr/lib/python2.3. I noticed that there were several other modules that were present on the other computer that I didn't have on the computer in question. Both computers were have amd processors and were running ~x86. I backed up my /usr/lib/python2.3 directory and copied the one from the other computer. Magic happened and everything worked fine after that. I honestly didn't think that copying the directory would fix things, but I haven't had a problem since.
well, oddly you're the only one who's reported this problem. we've heard no other reports of this, so i can't figure out why you were missing cpickle except for a local problem on your machine. seems to me that subsequently it worked fine, so unless theres more debugging detail you can provie, i'm afraid i'll have to close this bug.
I think closing this bug is reasonable. I'll mark it down as "just one of those things". Thanks for your help.