Important! Do not update to Python 2.6.5_p20100801

Seems like someone pulled another breakage, almost an year after the past one. Please do not upgrade to this version of Python, and if you have problems like the following:

>>> Emerging (1 of 1) dev-lang/python-2.6.5-r3
Traceback (most recent call last):
  File "/usr/bin/emerge", line 42, in 
    retval = emerge_main()
  File "/usr/lib64/portage/pym/_emerge/main.py", line 1555, in emerge_main
    myopts, myaction, myfiles, spinner)
  File "/usr/lib64/portage/pym/_emerge/actions.py", line 434, in action_build
    retval = mergetask.merge()
  File "/usr/lib64/portage/pym/_emerge/Scheduler.py", line 914, in merge
    rval = self._merge()
  File "/usr/lib64/portage/pym/_emerge/Scheduler.py", line 1222, in _merge
    self._main_loop()
  File "/usr/lib64/portage/pym/_emerge/Scheduler.py", line 1369, in _main_loop
    self._poll_loop()
  File "/usr/lib64/portage/pym/_emerge/PollScheduler.py", line 134, in
_poll_loop
    handler(f, event)
  File "/usr/lib64/portage/pym/_emerge/SpawnProcess.py", line 151, in
_output_handler
    buf.fromfile(files.process, self._bufsize)
IOError: [Errno 11] Resource temporarily unavailable

Then please see bug #330937at this point in time I have no idea how to solve if you updated already, it’s 3:50am and I’m actually here just because I made a mistake rebooting Yamato and found this out.

Update: we have a quick hotfix for you to apply if you reach this point:

wget http://dev.gentoo.org/~ferringb/fix-python-2.6.5_p20100801.patch -O - | patch /usr/lib/portage/pym/_emerge/SpawnProcess.py

it’s a one-liner, just execute it, then you can simply re-merge Python 2.6.5-r3 and Portage to have the pristine system.

13 thoughts on “Important! Do not update to Python 2.6.5_p20100801

  1. I was skeptical of your criticism of the python team in the past. Getting Python 3 in early was a good thing, especially since Gentoo is such a developer friendly system and we ought to be banging away the new bits if we’re worth our salt. But breaking the package manager.. this was a pretty grievous mistake. Hopefully they learned an important lesson.

    Like

  2. At the moment I’m on holidays since the past friday, but two days ago a colleague from my office called me because *portage stopped to worked* on the cluster and also on several different servers used for testing.I have lost *ONE* day of my holiday because @Arfrever suggested in a commet of your post[1] to use USE_PYTHON inside make.conf file to let end-users to gain a better control of the installed python interpreters. So simple, so good and my office colleagues decided to adopt it, but the disaster was just behind the corner:$ emerge –info’ascii’ codec can’t decode byte 0x9c in position 27: ordinal not in range(128) in /etc/make.confPortage was completely broken / unrecoverable and I was very lucky to found the connection between USE_PYTHON and the make.conf error in just 12 hours (I’m not exaggerating); now the real question: why are there NOT working features into the stable portage? I’m seriuos, why? I wondered how and why nobody noticed the problem before to commit into the repository.[1] http://blog.flameeyes.eu/20

    Like

  3. @ booxter, I’ve actually noticed the bug before you posted it — and I’m happy to say that the suggestion I gave there is supported by pambase, so I’m going in the right direction with that as well!@ equilibrium the answer is simply “Afrerver hasn’t tested Portage with Python 2 (which is the default for Gentoo) in a very long time”; even last night he kept trying “defending” himself that he tested it… with Py3.1 and 3.2..

    Like

  4. I was just to say that someone should explain to Afrever that he should test portage with python, seem basic

    Like

  5. What I fail to understand, is WHY we need to continue pulling snapshots from the 2.6 branch. Sticking to stable releases seems so much simpler. Let python upstream decide when something is ready to be used :>

    Like

  6. I think gentoo python guys like to run bleeding-edge code. It’s ok. It’s not ok when they push it in portage (python3 for default installations, today’s epic fail).I’m curious why changes in python don’t require any peer review and QA? It’s that simple: if we break python we break portage and the whole system -> so we *can’t afford* breaking it.

    Like

  7. Pity I and countless other users didn’t see this before having our systems hosed, again. So many careless bumps in the last year, not including the monumental f-up that was libpng…I really like Gentoo, but it’s things like this (lack of QA, careless commits to the tree, poorly planned upgrades/security bumps) that has driven me to another source-based distro.

    Like

  8. Why am I not surprised Arfever is still committing shit to the tree and acting like everyone else is wrong and he’s right. It’s been almost a year (I switched to other distros and windows) and he’s still at it. I’m going to go out on a limb and guess that debug USE-flag still exists for apr?Looked it up just now. It was fixed by someone else ofc.

    Like

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s