Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 281899 - dev-python/docutils-0.5 failed to emerge after upgrading python from 2.5.x to 2.6.x
Summary: dev-python/docutils-0.5 failed to emerge after upgrading python from 2.5.x to...
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Development (show other bugs)
Hardware: x86 Linux
: High normal (vote)
Assignee: Python Gentoo Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-08-18 11:56 UTC by Claer
Modified: 2009-08-18 20:38 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Claer 2009-08-18 11:56:04 UTC
After upgrading world containing a new version of python (2.6), I was unable
to emerge dev-python/docutils-0.5

Here is the paste of the error :
>>> Emerging (1 of 1) dev-python/docutils-0.5
 * docutils-0.5.tar.gz RMD160 SHA1 SHA256 size ;-) ...                                                                                                  [ ok ]
 * checking ebuild checksums ;-) ...                                                                                                                    [ ok ]
 * checking auxfile checksums ;-) ...                                                                                                                   [ ok ]
 * checking miscfile checksums ;-) ...                                                                                                                  [ ok ]
>>> Unpacking source...
>>> Unpacking docutils-0.5.tar.gz to /var/tmp/portage/dev-python/docutils-0.5/work
>>> Source unpacked in /var/tmp/portage/dev-python/docutils-0.5/work
>>> Preparing source in /var/tmp/portage/dev-python/docutils-0.5/work/docutils-0.5 ...
 * Applying docutils-0.5-test_node_class_names-python-2.6.patch ...                                                                                      [ ok ]
 * Applying docutils-0.3.7-extramodules.patch ...                                                                                                        [ ok ]
>>> Source prepared.
>>> Configuring source in /var/tmp/portage/dev-python/docutils-0.5/work/docutils-0.5 ...
>>> Source configured.
>>> Compiling source in /var/tmp/portage/dev-python/docutils-0.5/work/docutils-0.5 ...
python setup.py build
Error: The "distutils" standard module, which is required for the
installation of Docutils, could not be found.  You may need to
install a package called "python-devel" (or similar) on your
system using your package manager.
 *
 * ERROR: dev-python/docutils-0.5 failed.
 * Call stack:
 *               ebuild.sh, line   49:  Called src_compile
 *             environment, line 2880:  Called distutils_src_compile
 *             environment, line  709:  Called die
 * The specific snippet of code:
 *           ${python} setup.py build "$@" || die "Building failed";
 *  The die message:
 *   Building failed
 *
 * If you need support, post the topmost build error, and the call stack if relevant.
 * A complete build log is located at '/var/tmp/portage/dev-python/docutils-0.5/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/dev-python/docutils-0.5/temp/environment'.
 *

>>> Failed to emerge dev-python/docutils-0.5, Log file:

>>>  '/var/tmp/portage/dev-python/docutils-0.5/temp/build.log'

 * Messages for package dev-python/docutils-0.5:

 *
 * ERROR: dev-python/docutils-0.5 failed.
 * Call stack:
 *               ebuild.sh, line   49:  Called src_compile
 *             environment, line 2880:  Called distutils_src_compile
 *             environment, line  709:  Called die
 * The specific snippet of code:
 *           ${python} setup.py build "$@" || die "Building failed";
 *  The die message:
 *   Building failed
 *
 * If you need support, post the topmost build error, and the call stack if relevant.
 * A complete build log is located at '/var/tmp/portage/dev-python/docutils-0.5/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/dev-python/docutils-0.5/temp/environment'.
 *
[root@papillon 4028 ~] 1 #


If I Change back the default python interpreter to the old version (2.5.x),
the package docutils compiled fine.
[root@papillon 4030 ~]# eselect python list
Available python interpreters:
  [1]   python2.5
  [2]   python2.6 *
[root@papillon 4031 ~]# eselect python set 1
[root@papillon 4032 ~]# eselect python list
Available python interpreters:
  [1]   python2.5 *
  [2]   python2.6
[root@papillon 4033 ~]# emerge -1 dev-python/docutils
Calculating dependencies... done!                    

>>> Verifying ebuild manifests

>>> Emerging (1 of 1) dev-python/docutils-0.5
 * docutils-0.5.tar.gz RMD160 SHA1 SHA256 size ;-) ...                                                                                                  [ ok ]
[...]
>>> Completed installing docutils-0.5 into /var/tmp/portage/dev-python/docutils-0.5/image/


>>> Installing (1 of 1) dev-python/docutils-0.5
 * Byte compiling python modules for python-2.5 .. ...                                                                                                   [ ok ]
>>> Auto-cleaning packages...

>>> No outdated packages were found on your system.

 * GNU info directory index is up-to-date.
[root@papillon 4034 ~]#



Reproducible: Always

Steps to Reproduce:
1. emerge python 2.6
2. eselect python version 2.6
3. emerge -1 dev-python/docutils

Actual Results:  
ebuild dev-python/docutils failed when built with python-2.6

Expected Results:  
ebuild dev-python/docutils installs successfully when built with python-2.6
Comment 1 Rafał Mużyło 2009-08-18 12:28:00 UTC
In such cases first question is always:
did you run python-updater already ?
See also the output of (in python):
import sys
import os
import glob
from distutils.core import setup
from distutils.command.build_py import build_py
from distutils.command.install_data import install_data
Comment 2 Claer 2009-08-18 20:22:13 UTC
I didn't run python-updater, that was my mistake...
After running it, everything went fine. 

Sorry for the noise.