Bug 421631 – net-wireless/blueman-1.23: emerging fails with python syntax error

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Sebastian Pipping 2012-06-17 18:27:35 UTC]

Created attachment 315617 [details]
build.log

Relevant build log excerpt:

=======================================================================
checking for a Python interpreter with version >= 2.7... python3
checking for python3... /usr/bin/python3
checking for python3 version... 3.1
checking for python3 platform... linux2
checking for python3 script directory... ${prefix}/lib64/python3.1/site-packages
checking for python3 extension module directory... ${exec_prefix}/lib64/python3.1/site-packages
checking for headers required to compile python extensions...   File "<string>", line 1
    import sys; print sys.prefix
                        ^
SyntaxError: invalid syntax
  File "<string>", line 1
    import sys; print sys.exec_prefix
                        ^
SyntaxError: invalid syntax
not found
configure: error: Could not find Python headers
=======================================================================

Could be a Python2-Python3-mixup thing.

This is the situation python-wise:

=======================================================================
# eselect python list
Available Python interpreters:
  [1]   python2.5
  [2]   python2.6 *
  [3]   python2.7
  [4]   python3.1
  [5]   python3.2

# eselect python list --python2
Available Python 2 interpreters:
  [1]   python2.5
  [2]   python2.6 *
  [3]   python2.7

# eselect python list --python3
Available Python 3 interpreters:
  [1]   python3.1 *
  [2]   python3.2
=======================================================================

[Comment 1 Tiziano Müller (RETIRED) 2012-06-18 14:51:14 UTC]

strange, I suspect that your /usr/bin/python2 symlink or the wrapper is somehow broken because configure first checks for python, python2 and then for python3.

Can you please attach the config.log?

[Comment 2 Tiziano Müller (RETIRED) 2012-06-18 14:53:45 UTC]

this should be the output:

checking for a Python interpreter with version >= 2.7... python
checking for python... /usr/bin/python

and the wrapper should then call python-2.6 since  that's your python-2 active version and we're calling "python_set_active_version 2 ; python_pkg_setup" in the ebuild.

[Comment 3 Sebastian Pipping 2012-06-19 19:57:30 UTC]

Created attachment 315797 [details]
config.log

(In reply to comment #1)
> Can you please attach the config.log?

Here you go.

[Comment 4 Tiziano Müller (RETIRED) 2012-06-20 06:13:22 UTC]

Thanks. Seems that the package in deed requires python-2.7. Fixed in -r2 (together with some shebang conversion stuff).

[Comment 5 Alexander 2012-06-20 20:14:37 UTC]

Created attachment 315883 [details, diff]
Setting minimum version of Python to 2.6.

Dependence on Python 2.7 not entirely true. I created a patch to reduce the minimum version of Python to 2.6. Blueman emerged and running.
Please check it out.

[Comment 6 Tiziano Müller (RETIRED) 2012-06-21 06:13:51 UTC]

That patch must be against configure.ac only. If you create a bug @upstream, submit an updated patch for blueman (for configure.ac only) and a patch for the ebuild I'll submit it.