Received the following after doing an emerge -u world that upgraded Python. >>> Merging sys-devel/autoconf-2.54 to / Traceback (most recent call last): File "/usr/bin/emerge", line 1641, in ? mydepgraph.merge(mydepgraph.altlist()) File "/usr/bin/emerge", line 1037, in merge retval=portage.doebuild(y,"merge",myroot,edebug) File "/usr/lib/python2.2/site-packages/portage.py", line 1244, in doebuild return merge(settings["CATEGORY"],settings["PF"],settings["D"],settings["BUILDDIR"]+"/build-info",myroot,myebuild=settings["EBUILD"]) File "/usr/lib/python2.2/site-packages/portage.py", line 1470, in merge return mylink.merge(pkgloc,infloc,myroot,myebuild) File "/usr/lib/python2.2/site-packages/portage.py", line 3939, in merge return self.treewalk(mergeroot,myroot,inforoot,myebuild) File "/usr/lib/python2.2/site-packages/portage.py", line 3646, in treewalk mymtime=int(time.time()) OverflowError: float too large to convert
Details of exactly what I did. Base gentoo 1.4rc1 install. X KDE, evolution mozilla etc. Changed the make.conf to include ACCEPT_KEYWORDS="~x86" emerge -f -u world to grab all the new stuff. emerge mysql to get that running USE="mysql" emerge -u msyslog to get and build msyslog and then it upgraded about 8 packages, including gcc to 3.2.1 and glibc and python. try to emerge rest of the world by doing emerge -u world and then get the error reported.
one more thing... seems to be "time" dependent. Just doing a emerge -u world now, and it is putting in one package. If I wait a while then it seems to break again.
Things may have been broken because you switched gcc and glibc versions due to your sudden change of keywords. You need to either rebuild those packages in a consistant form, or get some bin packages form someone. Do not mix ~arch with arch for system packages.
*** Bug 11366 has been marked as a duplicate of this bug. ***
this happens on a fresh stage2 install too ...
Fresh stage 2 with or without ~arch ?
Someone else on the mailing list (gentoo users) had similar problem. Below is my post on what I did to work around this problem. ------------ Start Post to mailing list --------------- Hi All, I had the same problem, I did file it as a bug (ID 11333) and was told its a problem with using ~arch and gcc/glibc. What I did to fix it was hack the portage.py code a little and changed the line it complains on to read starttime=long(time.time()) that seemed to fix the problem and all worked well after that (there is another line in the code that does the same thing, but cant remember where it is now. just do a search for int(time.time()) within your editor and change the line to long(time.time()). As a by the way... I did an rsync again, re-emerge'd portage and python and even tried the rescure portage. None worked until I did the code hack. hope this helps. Jonathan -------------- End post to mailing list -----------------
It's kinda odd for that to happen... What is your date set to? Do this: python -c 'import time; print time.time()'
This is what I get from that command. jonathan@pixie jonathan $ python -c 'import time; print time.time()' 1038791097.79 jonathan@pixie jonathan $ System date is set correctly, ntpdate sync'd daily with ntp servers.
What version of python do you have? python -V
Version 2.2.2
This is _really_ silly, but I fixed it anyway.
